-
Notifications
You must be signed in to change notification settings - Fork 22
Fix: Add a check for tektonconfig status #256
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
base: main
Are you sure you want to change the base?
Conversation
Test still needs fixing |
297e2ee
to
8b4504c
Compare
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.
/approve
Code changes generally look good. Asking for a few changes before we call this good to merge:
- Add the check for not found errors
- Update the commit message so it is more complete. Tekton has an excellent guide on writing good commit messages.
6cc8882
to
e206635
Compare
Thanks for the review @adambkaplan . Did the changes. |
Cleaning up tests |
9a78c7c
to
d317fa7
Compare
I have updated some tests to create the tektonconfig since its status being ready is now required after the fix |
2a03ffd
to
a724136
Compare
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.
Looks good to me.
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.
Looks good
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.
/approve
Marking this as a fix worth adding.
/hold
There is a bit of risk with this change, I'd rather not merge it as we are getting ready for the v0.16.0 release. After we release v0.16.0 I think it's fine to merge.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adambkaplan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
39901c5
to
446c6a5
Compare
Thanks for the points @adambkaplan ! |
The e2e appeared to have flaked - timed out waiting for the operator pod to become ready. We may consider increasing the timeout from 5m to 10 or 15 minutes (in a separate pull request). |
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.
Code wise this looks good. However, I do ask that you fix the typos and formatting of the commit message. These serve as excellent reference for future maintainers (maybe even your future self!).
Tekton has excellent guidelines on how to write a well formed commit message.
Add a TektonConfig readiness check to the ShipwrightBuild reconcile loop to ensure that the operator proceeds only when the TektonConfig is available and ready. This prevents reconciliation of the Build resource which depends on Tekton components. The new function `fetchAndCheckTektonConfig`: - Retrieves the TektonConfig resource from the cluster - Checks its status conditions for readiness - Logs messages for both success and failure cases - Sets an appropriate Ready condition on the ShipwrightBuild resource - Signals the controller to requeue if Tekton is missing or not ready Resolves: shipwright-io#167 Signed-off-by: Hasan Awad <[email protected]>
446c6a5
to
d58b19f
Compare
/hold cancel We can merge this now that Shipwright v0.16.0 has been released. |
/retest |
Changes
Added a check for tektonconfig before progressing in the reconciliation process.
Fixes #167
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes