This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Configuration for whether resources should be always updated #70
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.
How to categorize this PR?
/area usability
/kind enhancement
/priority normal
What this PR does / why we need it:
This PR introduces a new command line parameter
--always-update
which defaults tofalse
. If set totrue
it will always send aPUT
request for managed resources even if it detects that their desired state does not differ from their actual state in the system. This isWhich issue(s) this PR fixes:
Ref gardener/gardener-extension-provider-aws#134
Special notes for your reviewer:
/invite @tim-ebert
Release note: