522 results found
-
Add "Substitute Variables in Templates" feature to "Upgrade Helm Chart" step
Using values file to handle simple variable replacement is cool. It's painful to do that for multiline texts defined as Octopus Variable. It's very hard to get the indentation right. A somehow easier way will be using ".Files.Get" and then pipe to "nindent". This means we have a text file in which the variables are to be substituted during the same step like "Upgrade Helm Chart" and that file is not a helm values file at all.
"Upgrade Helm Chart" already has a feature "Custom Deployment Scripts", which can be used to do this. But a much more easier way…
2 votes -
Supply prompted variable to trigger
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.
4 votes -
Write-Output and other logging functions should be able to use markdown
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.
3 votes -
Update variable snapshot in deployment window
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.
2 votes -
Warning state
We'd like to implement Canary Deploy in some of our projects.
We have seen and tried different methods but for our needs the best solution would be this one:
go, during deployment, to select the canary target and start the deployment only on that target(s).It works fine, however the problem is that at the end of the process we see the outcome in green and this is very misleading because in reality the deployment was successful but only on the selected target(s).
We tried to manually edit the status but it seems it is only possible to put in…
1 vote -
Ability to call a script rather than code it inline
Hi,
I have been looking at getting out deployment process under version control for our main project.
I have successfully integrated Octopus with Azure Devops Repo and created a test project under version control etc.
From what I can see, the entire deployment process is written to a /.octopus/deployment_process.ocl file, including any inline PowerShell scripts.
For example:
step "Swap Staging and Production Slots" {
…action { action_type = "Octopus.AzurePowerShell" properties = { Octopus.Action.Azure.AccountId = "#{AzureAccount}" Octopus.Action.Script.ScriptBody = <<-EOT …. …. …. Lots of powershell coding …. …. …. EOT Octopus.Action.Script.ScriptSource = "Inline" Octopus.Action.Script.Syntax = "PowerShell" OctopusUseBundledTooling = "False" } worker_pool1 vote -
Play a configurable audible bell at the end of a deployment
When the user has an ongoing deployment visible in his/her browser, it would be great if we could add the possibility to play a customisable sound at the end of the deployment: deployments can take a very long time to finish and who runs the deployment interactively is definitely interested in being notified right after the deployment completes for various reasons. Please add this functionality to the product.
1 vote -
Add context menu to deploy button on Overview page
On the release Overview page, it would be nice if the DEPLOY... button was enhanced with a context menu that as an option that behaves as it does now (navigates to release page).
Having the "DEPLOY [↓]" deploy instantly without navigating would save some clicks when there are many channels.
Perhaps there already exists a feature to deploy all channels to "next stage".1 vote -
Add FireLens configuration to the existing ECS deployment step
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
2 votes -
rollback
I need to add automatic rollback process in my deployment pipeline.
For example - If X release version deployment failed, then it will rollback to previous last successful release version Y in the same environment.
Trigger must be automatically happen.Please guide if someone has any better solution here.
1 vote -
Octopus Kubernetes Operator for GitOps Pull Workflow
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.3 votes -
Inline Bicep
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?
1 vote -
Support setting pod priorityClassName when deploying to Kubernetes
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
1 vote -
Basic ANSI escape code support
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
4 votes -
Add restrictions to prompted variables.
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.
2 votes -
Allow structured variabel replacement in the Upgrade a Helm-Chart step
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.
6 votes -
Container image name variables
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.
2 votes -
Advanced Release Filters
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)2 votes -
Support for AWS ECR as package feed for "Upgrade a Helm Chart" step
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.
1 vote -
Schedule Runbook Trigger with set prompted parameters
We have a case where we want to have a runbook to handle restoring Databases from different sources to different targets.
To handle this we have a form sheet with prompted variables.
But we also have the case where we want to do a restore daily to one of our databases. To do this we would need to be able set a trigger and also to set the prompted variables within that trigger.
I understand this can be done through the API currently but would rather see this in the UI.
My workaround for now is to duplicate the runbook…
4 votes