Hi,
We would like to select certain release versions in the scheduled deployment triggers similar to how we create a new release and can select a release version
Currently it doesn't seem to be possible and it uses only the latest release
Hope this can added in the next Octopus release
Thanks,
KK

Looking at the documentation for “octo.exe push” (https://octopus.com/docs/api-and-integration/octo.exe-command-line/push), but I cannot see any option to perform a dry run. The ‘create-release’ command has a ‘whatif’ param, and it would be really handy to have this on the ‘push’ command as well.

It would be helpful if you could have the Tenant name display on the Infrastructure page under Deployment Targets instead of hovering.

I think it would be nice to have this feature on Octopus.
So I was given a deployment task and I had multiple environment variables to upload.
I am the lazy type so instead, I wrote a python script to enable me to upload all at once in just a sec.

I hope this saves someone too

https://github.com/opemipoVRB/Python-Octopus-Client

Azure allows for the deployment of Subscription level resources via a template, but currently there is no out of the box step to do this in Octopus.

https://docs.microsoft.com/en-us/azure/azure-resource-manager/deploy-to-subscription

It would be great if we could have a built in step, along the same lines as the 'Deploy an Azure Resource Manager' template step.

If you deploy to specific targets in an environment but one the steps triggers a chained deployment, the chained deployment will target all hosts in the environment. It would be better if the chained deployment continued to target only the specific hosts that were originally chosen.

Sometimes we just want to write out a simple file to disk. For example writing out a basic text file to a location. While you could have a basic template in an repo sometimes you want to write out a straight file to disk with the normal support for variable substitution. Example, write a file to a queue or change a basic configuration file.

We need to put multiple certificates into the trusted people-store, and number of certificates must be configurable in one step.

Tried putting multiple certificates into the same scope for a variable, that only published the first one.

The Service Fabric Mesh deployment model is in public preview since a couple of months back and GA is expected this spring. Being mainly ARM template and container based, the SF Mesh deployment is probably possible to accompish by custom scripts today, but good out of the box support in OD would be very valuable.

It would be nice if a deploy could be requested when you don't have permissions. For example our Acceptance and Production environments can only be deployed to by the Release Management team, so it would be nice to be able to Request a deploy from within Octopus for a certain release version.

We have around 50 Tenant project variables that differ per each linked environment (Dev, Test, Uat, Stage, Prod)
So imagine the current UI, we have to scroll down the list endlessly until we find the variable.
Tenant variables UI improvement suggestion:
1. Toggle linked environments project variables- meaning use accordion or panel widget for each linked environment, so when I click on one linked environment I would expect to see the Tenant Variables only for that linked environment. Currently all linked environments variables are displayed.
app#/tenants/Tenants-61/variables?activeTab=projectVariables

1. Add filtering / searching for project variables on the same page app#/tenants/Tenants-61/variables?activeTab=projectVariables

Currently in powershell scripts, the only list of variables is $OctopusParameters, but this list includes all the built-in Octopus parameters as well.

It would be really nice to be able to reference only the variables defined in the current project during a deployment.

Something like $OctopusProjectVariables

Here's the scenario:

I have a web application that is being used across 12 countries.

Every country has its own environment, databases.

While the current Octopus allow us to create tenant variable like Alias, it is useful but when it comes to scope variable this feature is not there.

Example: Tenant A has a different Database credential for UAT and PROD. Currently the workaround is to create 2 tenant variable, like UAT Database, PROD Database.

It would be useful to have this scoped as well.

It would be nice if the Channel Version Rules had support for Octopus variables. From a management standpoint, when you have dozens and dozens of deployment steps bound to specific Version Rules, it would make sense to be able to make centralized updates rather than going through all of the various projects, channels, and associated rules in order to make the same update.

I would like it if there would be an option to compress the Package Drop folder on a target location.

I see it is now possible to deploy it as an artifact in .Zip format.
But i would like it if we could deploy it to a file share in .Zip format without requiring somebody to manually copy it there.
Each Offline Package Drop folder contains a Calamari folder that is 45MB unzipped and only 10MB zipped.

Support an indent filter in variable substitution extended syntax so that multi-line variables can be outputted with an indent of a specified number of spaces.