Skip to content

feat: force ready status for desired objects#153

Open
eegseth wants to merge 2 commits intocrossplane-contrib:mainfrom
eegseth:main
Open

feat: force ready status for desired objects#153
eegseth wants to merge 2 commits intocrossplane-contrib:mainfrom
eegseth:main

Conversation

@eegseth
Copy link

@eegseth eegseth commented Sep 24, 2025

Description of your changes

Adds possibility to force readiness for desired objects from the composition. Useful for objects that does not have a status field etc.

This PR just picks up the ball from PR #33 (thanks to @tomaszkiewicz).

Fixes #29

I have:

[x] Read and followed Crossplane's [contribution process].
[ ] Added or updated unit tests for my change.

Signed-off-by: Endre Egseth <endre.egseth@lanekassen.no>
@salbracco24
Copy link

Any update on this? It would be a nice feature.

@bobh66
Copy link
Contributor

bobh66 commented Dec 15, 2025

This is probably superseded by #160. Also there are ways to specify individual resource readiness in the composing functions - like the annotation used by function-go-templating

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Never Ready When Creating Env Config

3 participants