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.

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?

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.

Add a filter search to this dialog, and order the dropdown contents alphabetically.

Version: https://octopus.com/downloads/2020.6.4855

Also put a copy icon next to your version number.

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.

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.

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.

Customer has requested we add some basic IP level restrictions to the Cloud instances when accessing via VPNs or other restricted networks

We would like to get notices when any deployment process either skips a step (for instance because there are no available targets) or when a step fails.

As per the guideline on the user roles page, it is recommended to have the Octopus Deploy team create built-in roles where they are lacking. We have several users who would like the ability to view/create/modify subscriptions to get notifications about steps in deployment processes. At present we would need to either create a custom role or give them administrator rights for this. Please create a built-in role so we do not have the risk of managing this ourselves.

appVersion for Helm charts cannot be overridden with command-line arguments, which means the new version must be overridden before packaging the chart, which causes a new chart version per application version.
There are workarounds for this, but those cannot be done with the current Helm upgrade step.

The only Runbook trigger right now is a scheduled trigger.

I would like to suggest two more trigger types:

Helm Chart Package Trigger:

When a new Helm Chart version of a package is published, then the trigger would fire. (Allowing the calling of a Runbook.)

Version Control Trigger:

If Octopus Deploy added a VCS trigger, then it would allow us to use GitOps.

Both of these allow Operations to enable control from check in / merge point in source control.

Right now supported is Powershell, Bash, C#, F# and Python

Would be nice to be able to write nodejs scripts as well

We want to be able to add custom values like commit id for example on packages

This would help knowing which commit id the package comes from, at the moment we are adding commit id in our release notes, but that ties to the release and not necessarily to the package

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/3

We are currently using React, Gatsby and Parcel which all use .env files for their environment variables

https://www.npmjs.com/package/dotenv

Currently .env files are not being recognized, they are assuming they are yaml files, which they are not, they are read similar to java properties as key values

Right now we have to use variable substitution, but would like to use structured so we don't need to add #{} tags in our code