Skip to content

Commit

Permalink
feat(efs): One-Zone filesystem (#28501)
Browse files Browse the repository at this point in the history
In this PR, I have added support for creating one zone filesystems. 

[As discussed in the issue](#15864 (comment)), I considered including `availabilityZoneName` in the props, but for now, I have added only the `oneZone` argument.

The `efs.FileSystem` construct also generates a mount target simultaneously. However, when creating a one zone file system, both the mount target and the file system should be located in the same Availability Zone. The issue arises because the name of the Availability Zone where the mount target will be placed (obtained from `props.vpc.selectSubnets()`) remains token, making it impossible to compare it with the given `availabilityZoneName`.

Please let me know if there is a smart way to resolve this.

Closes #15864

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
  • Loading branch information
badmintoncryer committed Jan 16, 2024
1 parent 06acf4f commit c0085d5
Show file tree
Hide file tree
Showing 14 changed files with 2,196 additions and 1 deletion.

Large diffs are not rendered by default.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit c0085d5

Please sign in to comment.