We have custom urls that are generated in some of our deploy scripts - unfortunately the user has to copy and paste the url from the log into the browser currently.

I would be nice of the logging functions supported markdown so we could just click a link to go to the url, or we could format our logs more effectively.

When a release's snapshot gets stale, Octo will provide a warning when deploying the release to alert the user that the snapshot is out of date. I currently click the linked release, update the variables, and then go back to the deployment page. However, it'd be very nice to have some way to update the snapshot for the release from the deployment page itself and save a couple clicks. Could be something like a button in the warning modal that would do this.

We want to be able to use a trigger to create and deploy a release of a project (using a specific channel).

At the moment the project relies on a prompted variable so we are unable to do this.

I’m actually working on a project where I need to deploy an ECS Service that uses a different FireLens configuration but the current ECS deployment step by Octopus Deploy does not support that configuration.

AWS Docs: https://docs.aws.amazon.com/AmazonECS/latest/userguide/firelens-taskdef.html

We're currently using Octopus to manage our Kubernetes clusters, but we're interested in transitioning to a GitOps Pull Model (rather than the current Push based approach where the Octopus Server is executing kubectl commands against our clusters) in which (in a similar fashion to the polling tentacles Octopus already offers), a service would run within our clusters and periodically
poll both git repositiories and docker registries/helm feeds for changes and sync the cluster state accordingly.

Bicep is the new ARM in Azure. With the new Version Control feature in Octopus we've moved to putting our ARM templates inline in our deployment processes - which gives a great user experience - they can be edited either view the UI or via the repo. However if we want to use Bicep we have to go back to bundling files in NuGet packages. Can I suggest that Bicep be added as a first-class experience in Octopus similar to ARM?

In my cluster we use Pod Priority classes to choose which pods to evict if a new pod cannot be scheduled. In the pod spec I need to specify priorityClassName (string, one of more pre-defined values in the cluster).

It would be very useful for me to have this option when defining deployment in the "Deploy Kubernetes containers" step template. More info here: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/

https://help.octopus.com/t/option-to-set-pod-priorityclassname-in-kubernetes-step-template/28332

I have a prompted variable to ask the deployer to enter a ticket number. If they enter anything other than a number my automation breaks. So I would like to restrict the user input to being only a number.

Octopus is getting used more and more with Linux and CLI tools in the Linux ecosystem. Those tools often output ANSI codes, particularly for color.

Most of the time it's possible to turn the color output/ANSI codes off but the lack of color can make deployment logs much less readable.

Other tools in the CI/CD process do support basic ANSI codes (color), eg. Github Actions, Gitlab CI, Jenkins etc.

As an example of log output that is much more difficult to read without color: terraform plan

This would be useful for replacing values especially in the values-file from Chart Package or Additional Package. With this feature we don't need to have variable replacement syntax in our source-files.

On the Deployments -> Overview page, instead of just an = operator when filtering by release, it would be very helpful to allow filtering by >= and <= operators. It would also by very helpful to filter just on major and minor release numbers as well or both independently.

Ex 1: filter by all tenants on major version X or greater
Ex 2: filter by all tenants on major version X and minor version Y or less (to find everyone impacted by a specific bug)

When a deployment has failed, it shows on a tenanted dashboard as the latest release, when I'm wanting to know which version was last deployed/currently active (our deployments rollback if unsuccessful), but right now there's no way on showing only success deployments.

It would be a great feature for this to be one of the Advanced Filters options.

Also, maybe as a side and could be a bug, that latest release number, even if failed, actually shows up as the current released version when doing a multi deployment i.e. using the Deploy To window

I have successfully set up an AWS ECR package feed and can find the Helm charts I have pushed there when I test the feed. However, ECR feeds do not show in the dropdown for package source in the Helm step.

I also tried using the oci:// address of the ECR as a Helm Feed, but receive the message "Only 'http' and 'https' schemes are allowed. (Parameter 'requestUri’).”

It would be great to be able to use at least one of these as a source for the chart.

The ability to use variables exists in so many different places when setting up Kubernetes deployments, but one place I would think would make the most sense is the container image name.

When creating step templates, I found this one field a barrier from allowing me to use the templates because we use that image name for checking logs for various debugging.

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 Deployments link to Worker View like what exists for deployment targets

Deployment target link path example: /app#/Spaces-1/infrastructure/machines/Machines-xxxx/deployments

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.

when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run.

idk what you call this icon with the orange square and white lightning bolt

but when the lifecycle is in this state, the save button really means, “go ahead and run”.