General
-
Use AWS IAM Roles as Octopus AWS Accounts
When creating an Octopus AWS Account (https://octopus.com/docs/infrastructure/deployment-targets/aws) you currently need to enter an AWS Access Key and Secret Key. This means the corresponding AWS Access Key needs to be periodically rotated, creating some management overhead and potential security vulnerabilities. Rather than an AWS Access Key and Secret Key, if we were able to enter an AWS IAM Role that is assumed whenever that Octopus AWS Account is used, then we would no longer need to manage AWS Access Keys.
In the background, Octopus Deploy would need to set it up so that the AWS IAM Role is assumed…
67 votesEC2 instance roles and secondary IAM roles can be assumed in AWS steps and for EKS clusters (new in 2020.4). The blog post at https://octopus.com/blog/aws-iam-roles has more details.
-
Support older versions of SQL Server
Please reintroduce support for SQL Server 2016 Enterprise.
Recent versions of Octopus only support SQL Server 2017+. SQL Server 2016 (SP2) still has mainstream Microsoft support until July 2021 and extended support until July 2026. It is very expensive for organisations to run and support multiple editions of Highly Available Enterprise SQL clusters and is consequently a barrier for upgrading to the latest Octopus version for my organisation. My organisation is a large enterprise in a heavily regulated industry so our software must be supported platforms, I am sure many of your enterprise customers would benefit from this.
9 votesWe have relaxed the restrictions on SQL Server from SQL Server 2017+ to SQL Server 2016+ in the latest patch release of Octopus Server 2020.2 and 2020.3.
This has taken affect from the following versions
2020.1.x (SQL Version change was not enforced in 2020.1.x)
2020.2.18 ➜ 2020.2.latest
2020.3.6 ➜ 2020.3.latest
2020.4.0 ➜ latest -
Runbook need support for prompted variables
Runbook need support for prompted variables
We need support for prompted variables when using runbooks hope this is added in a future version
2 votesThis was implemented in Octopus 2019.11
https://octopus.com/docs/runbooks/runbook-variables#prompted-variables -
Support Terraform 0.12
Octopus supports Terraform-Steps. It uses Terraform 0.11. Terraform 0.12 has been released and has a few breaking changes. Update the Terraform-Integration to be compatible with Terraform 0.11 and 0.12.
48 votesWe are happy to inform you that this UserVoice suggestion has been addressed as part of https://github.com/OctopusDeploy/Issues/issues/6562, and will be released with Octopus 2020.5.0.
-
Support linux-arm in Linux Tentacle
A dotnet core version has been build. I would be great if this was compiled to a linux-arm runtime.
https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle
15 votesSupport for ARM tentacles has been included in 2020.2.
See the blog post at https://octopus.com/blog/deploying-an-octopus-pi for an example of how these can be used with a Raspberry Pi.
-
Disable Chrome AutoFill on inputs
The chrome autofill gets in the way of dropdowns/multi-selects. There is not the ability for a user to disable autofill for specific websites, but this is supposed to work on the developer side:
47 votesThis should be resolved as of Octopus 2020.4
https://github.com/OctopusDeploy/Issues/issues/6481 -
Helm 3 support
Helm 3 is around the corner. Right now rc2 is available. Would be nice to Octopus could integrate with 3rd version of helm. Eg. Repositories will be available as container registries also. Are you guys plan to integrate with third version ?
1 vote -
Fix a typo in the docs
The header here
https://octopus.com/docs/administration/data/octopus-database#Octopusdatabase-highavailability
is missing an "i" between "bil" and "ty". Says Availabilty and not Availability1 voteThis has been resolved.
-
Kubernetes Ingress doesn't allow to configure TLS
Allow kubernetes ingress to specify TLS configuration.
15 votesThis was implemented in 2018.11.2
https://github.com/OctopusDeploy/Issues/issues/4929 -
Allow multiple version of 'kubectl'
Currently Ocotpus only allows for one version of 'kubectl' to be added to the Octopus server. This means that all clusters targeted by Octopus must be running the same version of Kubernetes.
It would add greater flexibility if we could add multiple versions of 'kubectl' and then choose which version to use within the Kubernetes deployment target.
3 votesThe ability to run a target in an environment with custom executables has been enabled with execution containers. The documentation at https://octopus.com/docs/deployment-process/execution-containers-for-workers has more information.
-
13 votes
This is now available. See the docs at https://octopus.com/docs/deployment-process/configuration-features/structured-configuration-variables-feature for more details.
-
Dark theme
It would be great to have the option to switch to a dark theme
166 votesDark mode was added in Octopus 2020.1 https://octopus.com/blog/octopus-dark-mode
:) -
terraform
Terraform step templates for Azure deploys. Currently only AWS is supported in Octopus included step templates. It seems like an easy addition to the existing functionality
12 votesAzure accounts can now be selected when deploying Terraform templates. See the issue at https://github.com/OctopusDeploy/Issues/issues/5518 for more details.
-
Allow defining an explicit order for prompted variables
At the moment (at least to my knowledge) the order in which prompted variables are shown is dependent on the variable name (ordered alphabetically).
It would be really cool if there was a possibility to give prompted variables an explicit order so that we can control in which order they appear in a simpler manner. For example it would be cool if one could just set a "priority" value for a prompted variable. This "priority" could be an integer and the prompts could then be ordered by this priority in descending order.
Unfortunately giving them names to achieve the correct…
13 votesPrompted variables are now shown in alphabetical order, as of 2019.7.2.
-
Allow kubernetes & helm steps to override the target provided namespace
Although the kubernetes target type defines its namespace, there may be some situations where a different namespace should be used for a given step
1 voteOverriding the namespace on the Helm step was implemented in 2019.1.1: https://github.com/OctopusDeploy/Issues/issues/5141
We can create a new suggestion for the other kubernetes steps if desired.
-
Add ability to use run conditions for child steps
The only way to specify a rolling deployment is by grouping several steps into one parent step.
Child steps cannot specify any run condition (success, fail, variable) but some child steps run condition can be based on several factors controlled by run conditions.
I already opened a discussion here: http://help.octopusdeploy.com/discussions/problems/55380-add-ability-to-use-run-conditions-for-child-steps
192 votesRun conditions were made available for child steps in Octopus 2020.2: https://octopus.com/blog/octopus-release-2020-2#better-run-conditions
-
Support Powershell scripts on Linux
Now that Powershell is cross-platform, please support running Powershell scripts on Linux
33 votes -
Show variable snapshot differences in release screen
Sometimes when deploying, the user receives this message:
"For consistency, this deployment will use a snapshot of the variables and deployment process that was taken when the release was created, which does not include the latest changes that have been made to the project. A changed process can only be incorporated by creating a new release (this one may be renamed if desired). Variables can be updated via the release page, clicking Show to show the variables from the snapshot, and clicking the Update variables button."
It would be great to be able to tell the user exactly what changed,…
217 votesIntegrated in https://github.com/OctopusDeploy/Issues/issues/4700
-
Allow cloning of tenants
It should be possible to clone a tenant including it's current configuration in a similar way to that you can clone whole projects.
Tenants tend to be similarly configured with only minor changes to each one so it would save time rather than having to configure each one from scratch.144 votesThe ability to clone tenants was delivered in Octopus 2019.8
-
Add Let's Encrypt automation to OD server
Ensuring certificates for the OD server are up to date are a little annoying. It would be awesome if the OD server could support renewing it's own hosting certificate with Let's Encrypt.
I've had a stab at creating custom steps to do this. The main issue is domain validation (DV). DNS validation often requires manual intervention and OD server controls http (see discussion at https://community.letsencrypt.org/t/domain-validation/26512 ).
The only way I see this really progressing forward is if OD server supports Let's Encrypt in the server as a maintanence task as it would be able to respond to http DV requests.…
16 votesThis has been released with Octopus 3.15. See our blog post for more information – https://octopus.com/blog/octopus-release-3-15.
- Don't see your idea?