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
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.
Prerequisites
I have verified the problem exists in the latest version
I have searched open and closed issues to make sure it isn't already reported
I have written a descriptive issue title
I have linked the original source of this report
I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)
The bug
It's possible to use the API to submit a deployment process that is invalid, causing unexpected behaviour. The UI stops this deployment process being created.
Process is invalid because:
It's got child steps and the parent step does not have a target role assigned.
The parent step is a manual intervention step that cannot have a target role associated as it runs on the Octopus server, therefore it can't be a parent step.
We have flagged this as an issue with product, but at this point we do not have capacity to assign an engineer to resolve the issue. We'll keep the issue open, but unfortunately we can not provide any guidance as to when it will be resolved.
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your issue, making sure it's handled appropriately.
Prerequisites
The bug
It's possible to use the API to submit a deployment process that is invalid, causing unexpected behaviour. The UI stops this deployment process being created.
Process is invalid because:
What I expected to happen
The validation should match that in the UI.
Steps to reproduce
This API request reproduces the issue:
curl_manualintervention.txt
The invalid deployment process looks like:
Log excerpt
Affected versions
Tested on 2020.5.2
Octopus Server:
Workarounds
This does not prevent the customer working.
Links
https://octopus.zendesk.com/agent/tickets/62229
The text was updated successfully, but these errors were encountered: