-
Pause for manual intervention after every step for testing deployments/runbooks
A thought just occurred to me. Being able to pause for manual intervention after every step could be an option in the advanced settings of a deployment or runbook execution. This would assist in testing runbooks/deployment processes meaning you can check state at each stage. Maybe not a manual intervention, perhaps just a "next step" or "proceed" button or similar.
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 -
Integrate PWA features and Desktop Notifications
It would be nice if we could install our octopus instances as a PWA and integrate desktop notifications for things like deployment events, failures, and possibly manual steps needing approval
1 vote -
Reorder Lifecycle Environments
Provide ability to reorder target environments in a lifecycle, just like you can reorder steps in a process. Currently, we have to delete all subsequent environments when adding a new environment, then re-add all those deleted environments. Being able to simply reorder these in the UI seems a quick win.
2 votes -
Permission Audit view
We were recently audited, and asked to provide screenshots showing which users had "DeploymentCreate" permissions.
please add a new Permissions Audit screen that allows selecting one or more permissions and spaces, and then showing all users who have that permission.
1 vote -
Octo CLI Support on ARM
I would assume* it's mostly a case of adding
linux-arm64
as a runtime argument.Octopus is the /only/ thing that's preventing me from moving my TeamCity agents to Amazon t4g instances. I can accept that the plugin for TC maybe more involved but can we atleast get a build of the cli supporting ARM so that I can manually post manually to Octopus.
4 votes -
Show ProjectId or SlugId in Project settings
Octopus-API/Octopus-Client works on Project Id or SlugId, However, there is no way to see these values in the web app. It would be intuitive if they are included in the project settings (albeit read-only) for usage across Octopus tools.
Usage:
https://help.octopus.com/t/can-we-see-the-project-id-in-octopus-web-app1 vote -
Schedule Runbook Trigger with set prompted parameters
We have a case where we want to have a runbook to handle restoring Databases from different sources to different targets.
To handle this we have a form sheet with prompted variables.
But we also have the case where we want to do a restore daily to one of our databases. To do this we would need to be able set a trigger and also to set the prompted variables within that trigger.
I understand this can be done through the API currently but would rather see this in the UI.
My workaround for now is to duplicate the runbook…
1 vote -
Allow running Execution Containers directly on a Kubernetes cluster
Allow running Execution Containers directly on a Kubernetes cluster without a configured worker.
The blog post here describes how to run workers on a Kubernetes cluster: https://octopus.com/blog/kubernetes-workers However, this approach has some challenges because it uses a long-lived container on the cluster to do the work.
It would be great if we could get an option to run ephemeral Execution Containers directly on a Kubernetes cluster without the need of a worker. Or, if instead of having long-lived worker containers on the cluster that directly run tasks, the workers only acted as a "broker", and tasks using that worker launched…
3 votes -
when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run
when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run.
idk what you call this icon with the orange square and white lightning bolt
but when the lifecycle is in this state, the save button really means, “go ahead and run”.
1 vote -
TeamCity plugin agentless deployment
When running a deployment and showing its status, specially on longer deployments, the TeamCity agents will be on hold for the duration of the task. On deployments where guided interruption is enabled this is specially taxing on agent licenses.
Since 2020.2.4 TeamCity has introduced agentless builds, where an agent can be detached during the execution of a build, and requires the running process to call TC back via api and inform the build has finished.
This is currently not possible on the plugin and, using powershell, I've found hard to establish the whole deployment status at X point in time.
2 votes -
Allow structured variabel replacement in the Upgrade a Helm-Chart step
This would be useful for replacing values especially in the values-file from Chart Package or Additional Package. With this feature we don't need to have variable replacement syntax in our source-files.
5 votes -
Improve child steps to allow arbitrary steps to be organised/grouped together
Customers would like to be able to create a group of child steps from any step (currently some don't allow grouping for example deploy a release steps)
Take a look at the following example:
- Create an EKS cluster.
- Create an Octopus deployment target.
- Add a config map to the EKS cluster.
Customers would like to be able to group all three steps together but currently, while step three requires a Kubernetes deployment target, step 2 cannot have the target because it fails if the target doesn't already exist.
It would be great to be able to specify everything in the…
0 votes -
Allow variable set assignment through variable set
Currently when a new variable set is created, it has to be included in projects individually. When there are many projects that should include the variable set, it would be much more convenient if the set could be included in projects via the 'usage' tab.
1 vote -
Calculate estimated completion time on the server
Currently the estimated completion time is displayed in the Octopus UI. If I'm understanding the response I got on the support forms correctly that value is calculated in the client and not pulled from the server. It would be really useful that that value was calculated on the server and the estimated completion time was exposed as an Octopus variable.
https://help.octopus.com/t/get-estimated-completion-time-programmatically/273752 votes -
I need to Set a Project variable from a PowerShell step so that i can use the variable in an arm template parameter file as a substitution
I need a step A that set a project level variable #{COLOUR} from powershell and/or bash such that when I run an arm template step within the same deployment the parameter file correctly substitutes the value of #(colour} during the arm template deploy.
1 vote -
Add Deployments link to Worker View
Add Deployments link to Worker View like what exists for deployment targets
Deployment target link path example: /app#/Spaces-1/infrastructure/machines/Machines-xxxx/deployments
2 votes -
Add support for Keyfactor (Security and SSL) Certificate management
We use keyfactor (https://www.keyfactor.com/platform/certificate-lifecycle-automation/) for Certificate lifecycle Automation. It would be great if Octopus could integrate with this keyfactor to allow for issuance, renewal, inventory, import and storage of new certificates.
1 vote -
Add Migrate options to API Import
First I want to say that the new API functionality added in latest versions is very appreciated especially the possibility to export/import project out of spaces. However we really miss the merge functionality when importing project from Non-prod octopus to Prod Octopus
Our current automated procedure includes : Delete project-> Re-import Project-> Update prod variables
Problems: It removes history and require a new release number in prod due to updated of variables.
Addition to this feature requests includes: Exclusion of environment variables in export
1 vote -
Grouping variables in Octopus UI
As a project leader I should be able to group variables on Octopus UI. This can be just logical separation.
This solve the problem with linked variables and help mange them.
For example It could collapse elements that are in structure - for example: db.username and db.password can be collapse as elements of root db or by labeling variables and then can be filtered by using specific label, for example - db.
2 votes
- Don't see your idea?