Runbook process editor commit failed silently due to sensitive variable declaration not support in version control #9233
Labels
kind/bug
This issue represents a verified problem we are committed to solving
Severity
Low
Version
2025.1.7634
Latest Version
I could reproduce the problem in the latest build
What happened?
If a Runbook contains a sensitive value parameter, the Git commit will fail without displaying an error. In the browser developer tools, we see a 500 error with a
"ErrorMessage": "The property 'Octolint.Octopus.ApiKey' is sensitive and not a variable declaration, which is not currently supported"
message.Ideally, the user would see the same error message we display when they try to save a sensitive parameter value in a project deployment process step.
Example:
Reproduction
Sensitive/password box
parameter.Commit
button stays green, and no errors are displayed in the UI.Error and Stacktrace
More Information
No response
Workaround
Move the sensitive value to a variable and reference the variable in the step parameter before committing changes.
The text was updated successfully, but these errors were encountered: