fix(regular_service_perimeter): remove create before destroy lifecycle rule from service perimeter policy resources #227
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e rule from service perimeter policy resources The ingress and egress policy resources managed here force replacement on any changes to their rules but it is not permitted to have multiple policies with the same title attached to a service perimeter. Therefore it is not possible to create replacement policies before destroying existing policies.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The ingress and egress policy resources managed here force replacement on any changes to their rules but it is not permitted to have multiple policies with the same title attached to a service perimeter.
Therefore it is not possible to create replacement policies before destroying existing policies.
Fixes #225