-
Notifications
You must be signed in to change notification settings - Fork 113
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
feat: block isbsvc deleting when there is linked pipeline #2202
Conversation
Signed-off-by: Derek Wang <[email protected]>
Signed-off-by: Derek Wang <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2202 +/- ##
=======================================
Coverage ? 63.93%
=======================================
Files ? 334
Lines ? 40676
Branches ? 0
=======================================
Hits ? 26006
Misses ? 13611
Partials ? 1059 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Derek Wang <[email protected]>
return fmt.Errorf("failed to check if there is any pipeline using this InterStepBufferService, %w", err) | ||
} | ||
if pls > 0 { | ||
return fmt.Errorf("can not delete InterStepBufferService %q which has %d pipelines connected", isbSvc.Name, pls) |
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.
will printing the pipeline names help the end user?
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.
This will show up in ISBService status, which means it displays in kubectl get isbsvc
This should sort of fix the problem in #1956.