You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! We are having an issue updating the severity annotation. We have essentially the following pipeline, configured to start an event when the job starts running and end it after an upgrade with Helm:
We want to modify the severity after the Helm process is finished (to set it to SUCCESS or WARN depending on the on_success or on_failure, for example). But when it runs it returns
2022/02/07 11:57:43 could not complete API call: error merging new annotations with existing annotations: could not retrieve required annotations field: /response/annotations at part 0: couldn't find key "response"
Could someone take a look at this? It seems that removing the additional /response could be enough to solve it, but I'm not sure if this could break something else, and I don't know enough Go to redo the tests that could break. Thanks!
The text was updated successfully, but these errors were encountered:
Hello! We are having an issue updating the severity annotation. We have essentially the following pipeline, configured to start an event when the job starts running and end it after an upgrade with Helm:
We want to modify the severity after the Helm process is finished (to set it to SUCCESS or WARN depending on the
on_success
oron_failure
, for example). But when it runs it returnsLooking at the code, it seems it is reading the
/response/annotations
path of the event, which makes sense for an http response of this type, but in this case the event.json is being read directly from the file saved by thein
step, which already saves only the response from the body. Therefore it looks like there is an extra/response
that is causing the error to appear.Could someone take a look at this? It seems that removing the additional
/response
could be enough to solve it, but I'm not sure if this could break something else, and I don't know enough Go to redo the tests that could break. Thanks!The text was updated successfully, but these errors were encountered: