This repository has been archived by the owner on Jun 14, 2021. It is now read-only.
Document the need for lifecycle argument #327
Merged
Conversation
This file contains 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
… and `app_user` When managing application group assignments via `app_group_assignment` resource the application resource's group management must be disabled using `lifecycle.ignore_changes` attribute to avoid removal of externally added assignments. Same applies to `app_user` resource. While this behaviour is shown in examples, it is best to warn users by adding this to docs too. See #322
quantumew
approved these changes
Nov 12, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When managing application group assignments via
app_group_assignmentresourcethe application resource's group management must be disabled using
lifecycle.ignore_changesattribute to avoid removal of externally added assignments. Same applies
to
app_userresource.While this behaviour is shown in examples, it is best to warn users by
adding this to docs too.
See #322