resource/aws_m2_environment: Should support setting both `efs` and `fsx` storage

[gdavison]

Terraform Core Version

All

AWS Provider Version

5.55.0

Affected Resource(s)

aws_m2_environment

Expected Behavior

Both efs and fsx storage should be settable at the same time

Actual Behavior

The provider returns an error

2 attributes specified when one (and only one) of [storage_configuration[0].efs.<.efs,storage_configuration[0].efs.<.fsx] is required

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "aws_m2_environment" "example" {
  name               = "example"
  engine_type        = "bluage"
  engine_version     = "3.7.0"
  instance_type      = "M2.m5.large"
  security_group_ids = [aws_security_group.example.id]
  subnet_ids         = aws_subnet. example[*].id

  storage_configuration {
    efs {
      file_system_id = aws_efs_file_system.example.id
      mount_point    = "/m2/mount/efsexample"
    }
    fsx {
      file_system_id = aws_fsx_lustre_file_system.example.id
      mount_point    = "/m2/mount/fsxexample"
    }
  }
}

Steps to Reproduce

Apply the configuration

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[gdavison]

Already done

[github-actions[bot]]

[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.