Bugfix: Allow retries on existing resources #32
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
This PR fixes a bug where Ansible was retrying resources with a cached resourceVersion, so if the resourceVersion changed it would fall into a failure loop of not applying against the latest resourceVersion. Now, Ansible will be using the latest resourceVersion when applying a resource.
Tunguska55
force-pushed
the
provision-retry-bugfix
branch
from
1484444 to
cf30d71
Compare
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.
This PR fixes a bug where Ansible was retrying resources with a cached resourceVersion, so if the resourceVersion changed it would fall into a failure loop of not applying against the latest resourceVersion.
Now, Ansible will be using the latest resourceVersion when applying a resource.
Fixes: #33