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

The replace environment goal copies over non-custom (elastic beanstalk created) security groups to the new environment if the old environment contains custom security groups #128

Open
edwinquaihoi opened this issue Sep 29, 2019 · 0 comments

Comments

@edwinquaihoi
Copy link
Contributor

During a "replace environment" operation the security groups of the source environment are copied over to the target environment. However if the the source environment contains both custom and non-custom security groups, the code incorrectly copies all security groups. This creates a referential integrity exception later on when the source environment is being terminated because one of its non-custom security groups is now being referenced in the target environment.

Note: As a workaround you need to manually deference the non-custom security group in the target environment and then manually terminate the source environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant