This repository was archived by the owner on Sep 14, 2020. It is now read-only.
Provoke handling cycles even with no arbitrary field preservation #343
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.
What do these changes do?
Trigger the after-sleep handling cycles via the progress storage, the same way as it is triggered for the no-sleep handlers.
Description
This aspect was unintentionally forgotten in #331, where the handlers' persistence was made configurable.
If the resource would have no arbitrary field preservation (e.g. for built-in resources), the dummy patching would be silently ignored by K8s API.
With this PR, the dummy patches are made the same way as the regular handlers are patched, so the handling cycles are always provoked after the sleeps.
Issues/PRs
Type of changes
Checklist
CONTRIBUTORS.txt