Ensure that stack operation lock is always unlocked #892
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
| @@ -131,6 +131,10 @@ type Scheduler struct { | |||
| // Any additional tags to add to stacks. | |||
| Tags []*cloudformation.Tag | |||
|
|
|||
| // When true, alls to Submit won't return until the stack has | |||
|
👍 looks great |
This was referenced Jun 24, 2016
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.
I discovered that there are certain cases where the stack operation lock would not get unlocked. If, for example, an error was returned from calling UpdateStack, we'd never reach the call to l.Unlock().
This change makes it so that
performStackOperationis synchronous throughout the stack operation, which means we can justdefer l.Unlock()immediately after locking.