Open jessesuen opened 1 week ago
I am unsure if this should be declared in-spec, or be more like the current abort annotation we have for the verification process of a Stage.
Verifications aren't themselves a CR, so an annotation on a Stage to kill a verification feels like it makes sense.
If we did go an annotation-based route here, couldn't we apply that annotation directly to the Promotion instead of on the Stage?
If we did go an annotation-based route here, couldn't we apply that annotation directly to the Promotion instead of on the Stage?
Yes, that's actually what I was suggesting.
Proposed Feature
When hitting https://github.com/akuity/kargo/issues/2661, it became apparent that we need the ability to terminate promotions since they might be long-lived, or bugs might cause them to get stuck running.
Motivation
I no longer want a Promotion to run.
Suggested Implementation
Introduce a
terminate
field in a Promotion, that would be set by API server by a user interaction:Note that terminate is a struct instead of a boolean, because we might want different termination options, e.g. gracefully close PRs that were opened (SIGTERM), or do nothing like a
kill -9
(SIGKILL).