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.

Allow each individual determine what deployment emails they want to receive. Users on multiple teams, or large deployment teams, are bombarded with hundreds emails a day. Giving the user the ability to tell the system they only want to receive failures, or no emails at all, would provide a better user experience. Alternatively, if this is not possible, allowing the system to have a single designated email for deployment notifications. This would allow the users to designate something like a Teams Channel to receive the notifications, and cut down on the amount of emails being sent in general.

Please add support for uploading artifacts also via the user interface.

Uploading reports/approval documents or other files to a release is currently not possible via an upload button. We have to do a workaround using a script that uploads files from a specific folder or using the API to attach files to a release.

Especially during Octopus approval steps people need to upload documents.

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”.

When we're doing mass maintenance to an entire environment, it would be useful to be able to disable non-admins from doing things to that environment, and display a banner (e.g."Deployments to production are disabled while servers are being re-racked") without stopping activity in other environments.

Looking for something much like the system-wide maintenance mode, except environment specific.

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?

Microsoft opened up a preview for ARM base Azure Cloud Service, which is probably hinting on them moving away from a Classic cloud service deployment model:
https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/overview
Please add support for this type of targets.

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.

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

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.