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
One of the most confusing parts of Octopus is managing the variable sets. I have lots of variables and lots of scopes and it's hard to juggle in the web app. Adding this feature would really help me out almost every release.
I'm looking at using the raw HTTP API, but it's complicated. Most confusing to me
The scoped and non-scoped versions show up as separate entries in the list of variables.
Switching between /api/Spaces-1/libraryvariablesets/ and /api/Spaces-1/variables/ doesn't make much sense.
It would help a lot if there was support for this in the CLI, maybe by grouping the instances with the same names.
One of the most confusing parts of Octopus is managing the variable sets. I have lots of variables and lots of scopes and it's hard to juggle in the web app. Adding this feature would really help me out almost every release.
I'm looking at using the raw HTTP API, but it's complicated. Most confusing to me
/api/Spaces-1/libraryvariablesets/
and/api/Spaces-1/variables/
doesn't make much sense.It would help a lot if there was support for this in the CLI, maybe by grouping the instances with the same names.
According to the API documentation, this is what updating a variable looks like: https://octopus.com/docs/octopus-rest-api/examples/variables/update-variable-set-variable-value
The text was updated successfully, but these errors were encountered: