-
Store SubscriptionId in tandem with WebGroupName for Azure Resources
The reason beeing that Azure CLI and Azure RM commands are context sensitive in regards to subscriptions. If for some reason you have Azure Accounts with access to more than one subscription you might be unable to use scripting to manage those resources, since the Azure Acccount's default subscriptionId might not match the resource's subscriptionId.
My suggestion would be to just add a new field/setting/variable for all Azure resources that Octopus stores information about, where you already take care of the ResourceGroupName and treat it exactly the same.
Azure provides the information in the same context at the same level,…1 vote -
Order JSON before serializing
The audit log is made significantly more difficult to use as edits to a value (in my case, a variable in a variable set, but this likely applies to any array of objects) moves the updated value to the end of the array (deleting and recreating, I would guess).
Ordering the JSON by id before serialising it would make the audit log significantly easier to read, and thus more useful.
1 vote -
API to determine if worker is busy or idle
in order to determine if a worker can safely be terminated it would be good to have a rest api for this. The closest thing we get today is this script https://github.com/OctopusDeploy/OctopusDeploy-Api/blob/master/REST/PowerShell/Workers/GetWorkersUsedInTasks.ps1 which uses string matching in task log output - very rudimentary, and with tons of failure modes.
I know there's a "worker lease" table, a rest api endpoint covering that table would be great.
1 vote -
Dynamic environments
I need the ability to add dynamic environments to Octopus Deploy. My use case is Dev Test Lab environments that are spun up and down to run a test suite.
3 votes
- Don't see your idea?