Skip to content
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

[Backport stable/1.0] Hard reject resolving incident with missing failed command #7344

Merged
1 commit merged into from
Jun 22, 2021

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jun 22, 2021

Description

Backport of #7293 to stable/1.0.

relates to #7127

In case the failed command can no longer be found for the incident to
resolve, we should not be able to resolve the incident. Instead, the
resolve command should be rejected. This already happened, but it would
simultaneously also write incident resolved (which seems conflicting).

To match behavior of other unrecoverable parts in the engine, we just
throw an exception during the processing, which stops any follow-up
events from being written and rejects the command.

(cherry picked from commit 2658a5f)
Copy link
Member

@korthout korthout left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍 (successfully backported by action)

bors merge

@ghost
Copy link

ghost commented Jun 22, 2021

Build succeeded:

@ghost ghost merged commit 156fe04 into stable/1.0 Jun 22, 2021
@ghost ghost deleted the backport-7293-to-stable/1.0 branch June 22, 2021 14:35
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants