Add an event filter with the resource.DesiredStateChanged predicate to filter status updates out #498
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
ulucinar
force-pushed
the
filter-status-updates
branch
2 times, most recently
from
b6516eb
to
10ce2ba
Compare
|
/test-examples="examples/azure/resourcegroup.yaml" |
…o filter status updates out - Generate the spec.initProvider API for the MRs. Signed-off-by: Alper Rifat Ulucinar <ulucinar@users.noreply.github.com>
ulucinar
force-pushed
the
filter-status-updates
branch
from
10ce2ba
to
e425f97
Compare
|
/test-examples="examples/azure/resourcegroup.yaml" |
1 similar comment
|
/test-examples="examples/azure/resourcegroup.yaml" |
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.
Description of your changes
This PR adds an event filter using the resource.DesiredStateChanged to the generated resource controllers so that updates to only labels, annotations (Crossplane's create pending/failed annotations will be ignored) and to the
specwill result in reconcile requests.The PR also generates the
spec.initProviderAPI because it bumps the upjet version.The PR also fixes a couple of linter issues.
I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
Please see crossplane-contrib/provider-upjet-aws#789. We will also need to perform some further tests with #495.