-
Organize Runbooks in a folder structure
In our more complex deployment project, we heavily depend on runbooks to update configuration, check parameters, run clean-ups, change certificate, and and and.
It is very hard to keep an overview in a long and unstructured list and it would be immensely helpful if we could organize runbooks a folder structure.e.g.
|- Certificate
| |- verify chain
| |- change cert
|- Database
| | - create backup
| | - run maintenance
|- Configuration
| | -rewrite config
| | -verify config... and so on
1 vote -
Allow custom deployment scripts for Terraform steps
Currently it it not possible to script additional actions when planning to apply or applying a Terraform template. This means that additional steps are required to carry out simple takes like importing an exiting resource before planning, or uploading a saved plan to S3 so that it can be pulled and applied.
Many other steps have this configurable feature, and I believe it would be highly effective here.
Suggestion -
- Pre-deployment script runs before 'terraform init' (allowing download of plan from S3, for example).
- Deployment script runs after 'terraform init' (allowing 'terraform import' after the template has been…1 vote -
Reorder Tenants
Make it so we can reorder tenants. We have 200 of them and having to scroll down to find our "Internal" tenant is silly. Renaming it to "0 Internal" to make it appear at the top looks hacky.
2 votes -
ip restriction
Customer has requested we add some basic IP level restrictions to the Cloud instances when accessing via VPNs or other restricted networks
2 votes -
Control when Tentacle retention policy step will be executed during deployment
Tentacle retention policy is executed once all deployments steps are completed. When the retention policy step starts running, it blocks any other step.
This behavior is by design and can't be configured.This design can cause issues if for some reason the retention policy step encounters issues and takes a long time to complete.
As a workaround we can add a deployment step of a dummy package at the end of the deployment process. As result the tentacle retention is executed at the last step of the deployment.
I would like to have an option to control when the retention…
5 votes -
Cloud region health checks
It would be nice to define health checks for a cloud region, ideally a script that is run for each deployment in the region.
It's easy to deploy websites to a cloud region, but hard to see if they're up and available.
1 vote -
Dashboard should be better at visualizing multiple tenants
Currently the home dashboard displays tenants as a small grey-on-grey count of up-to-date tenants vs total tenants. It would be nice to see a coloured pie chart or similar visualization instead, to make it more obvious when one tenant in an environment is still running an old version or has had a failed deployment.
It can be easy to miss failed deployments from the dashboard screen.1 vote -
Allow setting Build Information WorkItems
Currently Push Build Information API and command line ignores values set on WorkItems field, only to auto populate with values once one of the Integration extension is enabled.
Please allow Push Build Information API and Command line to
- Set WorkItems with values set on request
- Do not override values even if Issue Tracker extension is enabled5 votes -
Add parameters to Runbooks
This would be like runbook specific variables, but they are defined on the runbook and don't make sense to be in the published snapshot. They would generally be prompted values, but that shouldn't be required. They would be "snapshotted" when you run the runbook. When you are scheduling runbooks with a trigger, you should be able to provide values to use when the runbook is triggered.
For an example use of these, we have a Runbook that exports data from a database to a CSV and emails it. We have variables for the from and to dates and the email…
7 votes -
Operations Dashboard
I use Runbooks to check things in my Kubernetes cluster. I can run these on a trigger, but I have no way to surface them if there is a problem.
It would be really useful if Octopus Deploy had a dashboard that had configurable "Widgets" (or some such thing). You could have several different kinds of "Widgets", but the simplest would be one that has two states, "Needs Attention" or "Fine" (along with some text for context).
So I could define one of these Widgets, lets call it Container Base Image Status (a real example for me). In that widget…
2 votes -
Support Terraform Registries as an External Feed
I would like to use a Terraform Registry as an external feed. This would allow me to focus on certain versions of my terraform code fordeployment.
1 vote -
ID and Name in the html code for SIGN IN button?
We are trying to add our internal Octopus url access through CyberArk privileged access security, but CyberArk is not able to detect the "SIGN IN" button in the login page. Cyberark support said this is due to inspection of the "Sign In" button do not have ID and Name in the html code so Cyberark can't find the element.
Please can you help us add the ID and Name in the html code for SIGN IN button?1 vote -
Tenants
Display Tenant Name and Description when making selection of the tenant when deploying a release. An environment made by a previous team used the "Name" field to enter some sort of "Id" and on the "Description" field they captured the tenant's name, now is somehow hard to know which tenant to select by means of the Id.
1 vote -
Apply the retention policy out of hours (or on a schedule)
Applying the retention policy at the end of a deployment isn’t the best use of deployment time especially in a tenanted environment with many packages to deploy for many tenants on a single vm.
I would love to see an option to apply the retention policy out of hours, when the environment is at a low usage.
It would certainly speed up our deployments.
Similar to, but using a schdule.
https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/42726191-control-when-tentacle-retention-policy-step-will-b3 votes -
OctopusBypassDeploymentMutex for Script console
Parallel execution should be enabled or can be switch on the fly in script console. Via a variable, similar to OctopusBypassDeploymentMutex
With the scenario that there is a process running (read: stuck/looping) in the target and executing a kill command via the script console will get you “waiting for script to finish in task…” so it is currently not the workaround.
Ref case:
https://help.octopus.com/t/force-stop-a-step-execution/26682/32 votes -
Dashboard icon page target
I manage a multi tenant system and the dashboard is always a pain to use.
First the icon cant be trusted as it dose not accurately show things like a single tenant deploying (The animated icon).
But the real pain is that if I click that icon it takes me to the deployment page of one of the tenants. What I want it to do is take me to a screen for all of the tenants. Something like the tasks screen filtered by environment would be very nice.
Then I would be able to see the true state of all…
1 vote -
Add timeout to guided failures
Add an option to have guided failures timeout out and fail after a specified period of time. I.E it no manual intervention is taking in 1 hour have the deploy fail completely.
2 votes -
Allow variables to be set as Environment Variables
It would be extremely useful to allow variables to be set as an environment variable before the process starts (and even allow outputs to be made environment variables). At the moment it is extremely hard to write generic scripts for both development and for use in octopus.
Allowing variables to be set as environment variables eliminates this issue as well as allows more providers etc.
If I take a terraform run where the provider (say digital ocean and terraform cloud) can be initialized via environment variables I do not need to litter my scripts with octopus only if conditionals. They…
2 votes -
Ability to limit updates to specific variable sets to specific groups
We'd like the ability to lock down a specific variable set so that only specific teams can update the values in that variable set. We want to be able to have variables that multiple teams consume but only admins can set the values.
1 vote -
Octopus Server on Linux directly
As a Octopus Administrator I should be able to install Octopus Server directly on Machine with Linux operating system.
Now, there is only version with Linux container and in some cases docker can be unnecessary abstraction layer, that need to be maintained with OS machine.
1 vote
- Don't see your idea?