-
Notifications
You must be signed in to change notification settings - Fork 551
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 race condition on duplicate entity alias creation #1429
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
The creation of entity aliases should be serialized, since we want to handle the case when the user is attempting to create duplicate entity aliases during the same Teraform execution. A duplicate entity alias shares the same mount accessor and name with another entity alias. The fix is to lock the /identity/entity-alias/id path on all create, update, and delete operations. This allows the provider to reliably detect the duplicate entity alias condition, and prevent duplicate alias creation. Other fixes: - all CRUD functions are of the *Context type, and can return meaning diag.Diagnostics - created a new entity package under internal/identity/entity with some helper functions
- factor out common lock/unlock functions
vinay-gopalan
approved these changes
May 2, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Great work 😄
marcboudreau
pushed a commit
to marcboudreau/terraform-provider-vault
that referenced
this pull request
Nov 6, 2022
The creation of entity aliases should be serialized, since we want to handle the case when the user is attempting to create duplicate entity aliases during the same Terraform execution. A duplicate entity alias shares the same mount accessor and name with another entity alias. The fix is to lock the /identity/entity-alias/id path on all create, update, and delete operations. This allows the provider to reliably detect the duplicate entity alias condition, and prevent duplicate alias creation. Other fixes: - all CRUD functions are of the *Context type, and can return meaning diag.Diagnostics - created a new entity package under internal/identity/entity with some helper functions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix race condition on duplicate entity alias creation
The creation of entity aliases should be serialized, since we want to
handle the case when the user is attempting to create duplicate entity
aliases during the same Teraform execution. A duplicate entity alias
shares the same mount accessor and name with another entity alias.
The fix is to lock the /identity/entity-alias/id path on all create,
update, and delete operations. This allows the provider to reliably
detect the duplicate entity alias condition, and prevent duplicate
alias creation.
Other fixes:
diag.Diagnostics
helper functions
Community Note
Closes #669
Release note for CHANGELOG:
Output from acceptance testing: