Fix: Add a check for tektonconfig status#256
Fix: Add a check for tektonconfig status#256openshift-merge-bot[bot] merged 1 commit intoshipwright-io:mainfrom
Conversation
|
Test still needs fixing |
297e2ee to
8b4504c
Compare
adambkaplan
left a comment
There was a problem hiding this comment.
/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 |
adambkaplan
left a comment
There was a problem hiding this comment.
/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 DetailsNeeds 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). |
adambkaplan
left a comment
There was a problem hiding this comment.
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 <hasan.m.awad94@gmail.com>
446c6a5 to
d58b19f
Compare
|
/hold cancel We can merge this now that Shipwright v0.16.0 has been released. |
|
/retest |
|
For some reason GH actions isn't working. Going to close + reopen the PR to see if it fixes the issue. |
|
@adambkaplan I reran the failed actions |
adambkaplan
left a comment
There was a problem hiding this comment.
/lgtm
Looks like it is working now, all tests pass!
e5fde90
into
shipwright-io:main
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