Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: SG already exists error when recreating with create_before_destroy by introducing a security_group_name_prefix variable #64

Merged
merged 3 commits into from
Oct 25, 2023

Conversation

stefanwb
Copy link
Contributor

@stefanwb stefanwb commented Oct 24, 2023

Fixes the SG already exists error when recreating with create_before_destroy by introducing a sg_name_prefix variable that can be used to override the default behaviour where the Lambda's name is used.

@github-actions github-actions bot added the bug Something isn't working label Oct 24, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 24, 2023

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Lint 📖success

Terraform Validation 🤖success

Validation Output

Success! The configuration is valid.


@marwinbaumannsbp marwinbaumannsbp added the enhancement New feature or request label Oct 24, 2023
@stefanwb stefanwb force-pushed the fix-sg-name branch 2 times, most recently from d5ac309 to 4ddf29f Compare October 24, 2023 14:59
@stefanwb stefanwb added the breaking This change is not backwards compatible label Oct 24, 2023
@stefanwb stefanwb changed the title fix: SG already exists error when recreating with create_before_destroy fix: SG already exists error when recreating with create_before_destroy by introducing a sg_name_prefix variable that can be used to override the default behaviour where the Lambda's name is used. Oct 24, 2023
@stefanwb stefanwb changed the title fix: SG already exists error when recreating with create_before_destroy by introducing a sg_name_prefix variable that can be used to override the default behaviour where the Lambda's name is used. fix: SG already exists error when recreating with create_before_destroy by introducing a sg_name_prefix variable Oct 24, 2023
variables.tf Outdated Show resolved Hide resolved
main.tf Outdated Show resolved Hide resolved
main.tf Outdated Show resolved Hide resolved
@stefanwb
Copy link
Contributor Author

@marwinbaumannsbp see updated PR with resolved comments after our conversation

…destroy by introducing a sg_name_prefix variable that can be used to override the default behaviour where the Lambda's name is used.

Signed-off-by: Stefan Wessels Beljaars <[email protected]>
@stefanwb stefanwb removed the breaking This change is not backwards compatible label Oct 24, 2023
@marwinbaumannsbp marwinbaumannsbp changed the title fix: SG already exists error when recreating with create_before_destroy by introducing a sg_name_prefix variable fix: SG already exists error when recreating with create_before_destroy by introducing a security_group_name_prefix variable Oct 24, 2023
@marwinbaumannsbp marwinbaumannsbp removed the enhancement New feature or request label Oct 24, 2023
@stefanwb stefanwb merged commit 5334750 into master Oct 25, 2023
@stefanwb stefanwb deleted the fix-sg-name branch October 25, 2023 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants