search

OctopusDeploy / Issues

| Public | Bug reports and known issues for Octopus Deploy and all related tools
https://octopus.com
161 stars 20 forks source link

Config As Code Projects have 'Commit' option rather than 'Save' when editing sensitive variables #8999

Open LewisJohnsonOctopus opened 2 weeks ago

LewisJohnsonOctopus commented 2 weeks ago

Severity

Low - No blocking but causes confusion.

Version

Earliest tried was 2024.1.12775 - Exists in all versions currently.

Latest Version

I could reproduce the problem in the latest build

What happened?

When editing sensitive variables within a Config as Code project, we currently present a 'Commit' button. This is due to us currently not differentiating between the types of variables that have been changed. This is not accurate, as no commit is generated in version control. A 'Save' button when only sensitive variables have been edited would be more appropriate.

Reproduction

  1. Create a Config as Code project within Octopus.
  2. Navigate to the Variables page of the project.
  3. Edit a sensitive variable.

image

image

Error and Stacktrace

No response

More Information

No response

Workaround

No response

LewisJohnsonOctopus commented 2 weeks ago

[Internal] R&D slack discussion link

[Internal] ZenDesk Ticket Link