feat: Use base security-group module to remove duplicate EFS security group #325
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Attempt to resolve #324. I believe this is due to the fact that the nfs submodule is trying to create a duplicate NFS ingress that conflicts with the one defined here. This PR used the base
security-group
module and relies onto configure the efs ingress rules.
Motivation and Context
Resolves #324
Breaking Changes
This will cause a brief breakage for atlantis as it will replace security groups due to the need to switch modules. A sample plan looks like the following
Terraform plan
I wasn't able to find a way to fix this without this breaking change, but let me know if there's another avenue to go down.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request