This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
Exclude events from sequence migration that usually don't have a stage #5096
Comments
bacherfl
added a commit
that referenced
this issue
Sep 1, 2021
Signed-off-by: Florian Bacher <florian.bacher@dynatrace.com>
bacherfl
added a commit
that referenced
this issue
Sep 1, 2021
Signed-off-by: Florian Bacher <florian.bacher@dynatrace.com>
bacherfl
added a commit
that referenced
this issue
Sep 1, 2021
Signed-off-by: Florian Bacher <florian.bacher@dynatrace.com>
laneli
pushed a commit
that referenced
this issue
Sep 1, 2021
thisthat
pushed a commit
that referenced
this issue
Sep 20, 2021
RealAnna
pushed a commit
to RealAnna/keptn
that referenced
this issue
Oct 4, 2021
bhamail
pushed a commit
to bhamail/keptn
that referenced
this issue
Oct 6, 2021
…n#5096) Signed-off-by: Dan Rollo <danrollo@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At the moment the shipyard-controller throws some errors at startup during the sequence migration if an event does not contain a stage.
msg="could not migrate sequence with shkeptncontext 6173b673-c701-4c21-bfa9-ee1a9f3702c0" error="could not determine scope of task sequence: event does not contain a stage"
There are some events like
sh.keptn.event.service.delete.finished
orsh.keptn.event.service.delete.started
that don't have a stage and therefore they should be excluded and they should not raise any errors.Definition of Done
service.deleted
don't have a stageThe text was updated successfully, but these errors were encountered: