Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Library Variable Sets #346

Open
Jeff-Walker opened this issue Apr 25, 2024 · 0 comments
Open

Feature: Library Variable Sets #346

Jeff-Walker opened this issue Apr 25, 2024 · 0 comments

Comments

@Jeff-Walker
Copy link

Jeff-Walker commented Apr 25, 2024

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.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant