no-jira: no ttl long lived clusters#987
Conversation
|
@kryanbeane: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #987 +/- ##
=======================================
Coverage 95.87% 95.87%
=======================================
Files 22 22
Lines 2132 2134 +2
=======================================
+ Hits 2044 2046 +2
Misses 88 88 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Changes look good. I haven't done the verification. Will leave that for someone else. |
710acaa to
90ea08b
Compare
|
Confirmed expected behaviour: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pawelpaszki 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 |
035e935
into
project-codeflare:main
Issue link
N/A
What changes have been made
No jira for this, came up from Cathal encountering this in a cluster. With long lived clusters, we shouldn't allow TTL field to be set as this is only for lifecycled clusters.
Verification steps
poetry buildChecks