-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat(xfn): Consider composite ready state in function response #6021
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(xfn): Consider composite ready state in function response #6021
Conversation
| // ConditionsOverride allows the composition process to force | ||
| // a specific condition status, unlike Conditions which does not allow | ||
| // setting system conditions. | ||
| ConditionsOverride []xpv1.Condition |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could use a special TargetdCondition variant. i.e. Add a System field and just use that internally to surface these conditions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried this but it does work as intended since the custom conditions update (which uses the Conditions array) is performed in handleCommonCompositionResult() but the system conditions are set in updateXRConditions().
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed to a new type CompositeResource that is analog to ComposedResource and contains a Ready *bool property.
abcea6b to
3273978
Compare
Signed-off-by: Maximilian Blatt <[email protected]>
3273978 to
eea8f82
Compare
phisco
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Successfully created backport PR for |
Description of your changes
Marks the composite as ready or unready if the if
.Desired.Composite.Readyfield is set explicitly.Fixes #6020
I have:
earthly +reviewableto ensure this PR is ready for review.[ ] Added or updated unit tests.[ ] Added or updated e2e tests.[ ] Linked a PR or a docs tracking issue to document this change.backport release-x.ylabels to auto-backport this PR.Need help with this checklist? See the cheat sheet.