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

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.

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

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.

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

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.

Add ability to define custom substitution filters that can run scripts defined by the end user.

In the installation documentation there exists a helm chart example:
https://octopus.com/docs/installation/octopus-in-container/octopus-server-container-linux

Are there any existing examples of doing something similar, but using CloudFormation/Fargate/ECS to run the server + tentacles?

I posted about this as a GitHub issue as well (https://github.com/OctopusDeploy/OctopusCLI/issues/142). Basically, it would be nice if the octo CLI could read environment variables for all of its commands and flags. This would make CI easier since values could be easily changed and tested without having to make code changes.

Thank you!

Project variables may be scoped to a process to differentiate between variables used for deployment and variables used for runbooks.

I would like to be able to define process scope for variables within library variable sets so that library variables intended for use in deployments do not pollute my runbook process.

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

Hi team,

Our deployment usually happen in a short off business hour window. However, the Calamari update by default will happen on deployment time and it can sometimes take half hour to finish. Admittedly, we can workaround this by manual update or wrote and schedule our mock deployment. They all are not elegant enough. Please consider adding this feature in.

Amazon ECR supports pushing Open Container Initiative (OCI) artefacts to repositories. This includes Helm charts.

However, Octopus does not support pulling Helm charts from OCI sources.

I'd like to see this support added.

I find that deployments to Azure Functions and standard app services will occasionally fail due to files being locked. This usually requires stopping the app service, re-running the deployment, and then restarting the function or app.

This can be scripted with Powershell, but since this is such a common scenario, I’d love a checkbox built into the Azure App Service step that provides this ability. Something like “Stop App Service prior to deployment and restart after deployment”.

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.

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.