Skip to content
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

fix: set true always #4

Merged
merged 2 commits into from
Oct 15, 2024
Merged

fix: set true always #4

merged 2 commits into from
Oct 15, 2024

Conversation

niklastreml
Copy link
Contributor

@niklastreml niklastreml commented Oct 15, 2024

Description of your changes

Fixes #3

This essentially forces the readiness to be true

Signed-off-by: Niklas Treml <[email protected]>
Signed-off-by: Niklas Treml <[email protected]>
Copy link
Member

@puffitos puffitos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was just missing, right? I was wondering why the loggings were never ready 😉

LGTM

@niklastreml
Copy link
Contributor Author

Crossplane expects the function pipeline to set it afaik. There is an "auto-ready" function, which tries to find the composed resources' readiness automatically. Tried it, doesn't work for us, since it looks for a status: ready object on the composed resource, which the logging does not have

@niklastreml niklastreml merged commit 050efc7 into main Oct 15, 2024
5 checks passed
@lvlcn-t lvlcn-t deleted the fix/readiness branch October 15, 2024 10:42
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.

3 participants