General
-
Deployment promotion with excluded steps is not persisting chosen steps
Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.
We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.
It would be great if you can persist the state of excluded steps to the next environments as part of same release?
15 votes -
Allow the visibility of what teams have access to a project/group
Right now you can view a Team and see what project or project group that team has access to. We'd like to see the reverse as well. When we go to a project or project group we'd like to see the teams that have access along with their permissions.
10 votes -
Support Terraform 0.12
Octopus supports Terraform-Steps. It uses Terraform 0.11. Terraform 0.12 has been released and has a few breaking changes. Update the Terraform-Integration to be compatible with Terraform 0.11 and 0.12.
35 votes -
Use IAM roles instead of AWS access secrets for all external resources, e.g. feeds, targets, community library tasks
Currently, the only way to set up AWS authentication for an ECR external feed, AWS deployment target, community library task, etc, is with an IAM user secret such as API access keypair. Our product secrutiy team has exlicitly forbidden use of secrets such as keypairs like this and requires everything to use IAM role authentication via role assumption.
It would be lovely to replace the access key and secret key inputs with a single input for an IAM role name to assume into in order to get the needed credentials. The authentication and login could then execute on workers with…
29 votes -
Support inserting into an array in JSON Configuration
Given an JSON settings file which has an array element
e.g. { "Users": [] }
Use Octopus variables to insert into the array rather than just replace values.
e.g.
define Users:0:Username = user
define Users:0:Password = passwordWould result in the object getting inserted
{ "Users": [ { "Username: "user", "Password": "password" } ] }
https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7
7 votes -
Support linux-arm in Linux Tentacle
A dotnet core version has been build. I would be great if this was compiled to a linux-arm runtime.
https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle
12 votes -
Retention policies on offline targets (artifacts)
Delete previous install files when new install (with an artifact) occurs (offline targets). These deletion should keep in mind the configured retention policy in the corresponding lifecycle
15 votes -
Encrypt variables using Certificate
Add the ability to encrypt variable strings using something similar to the variable filters.
Something like: #{VariableToEncrypt | Encrypt(#{CertificateVariable})}
6 votes -
Support for High Priority Deployments/Tasks
Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
This is not possible now, the only solution now is to cancel all the existing tasks.28 votes -
Document Octopus Package metadata Json file format
The octo.exe push-metadata allows to provide package build information, but its format is not documented.
The documentation available at https://octopus.com/docs/octopus-rest-api/octo.exe-command-line/push-metadata states that the "metadata-file" parameter should be a "Octopus Package metadata Json file".
What is the format expected for that "Octopus Package metadata Json file" ?
7 votes -
Disable Chrome AutoFill on inputs
The chrome autofill gets in the way of dropdowns/multi-selects. There is not the ability for a user to disable autofill for specific websites, but this is supposed to work on the developer side:
38 votes -
Allow Variables to be Version Controlled
Imagine you have a connection string variable and you want to update it. You would update the variable and redeploy, however if you made a mistake (edited the wrong variable or the new connection string was not live yet) then you cannot roll back. This is even more of a problem if the variable is sensitive as you can't copy it beforehand.
I would like to be able to version octopus variables, this would include:
- Who
- When
- When deployed
- The ability to roll back/forward.At the moment we have to source control much of this type…
141 votes -
Separate permissions in the User Role "Project Contributor"
Currently, in order to allow developers to access and edit variables, they are also able to edit process steps including disabling them. This means that they are able to disable audit steps before deploying.
If process edit was a separate permission we could split out the ability to edit variables and the ability to edit/change process steps
7 votes -
"Use the version number from an included package" plus incremental number
"Use the version number from an included package" isn't as useful as it could be because whenever I modify a deployment process and go to create a new release, Octopus complains the release version already exists. So I either have to delete the old release or append ".i" to the version number. I would estimate I've appended ".i" about ten thousand times over the years. Would be nice to not have to do this.
Basically this:
https://help.octopus.com/t/how-to-create-a-release-version-with-package-number-and-an-incremental-number-with-it/238691 vote -
Support the creation of images as a task using packer
Packer is a versatile tool, especially when working in a multi-cloud environment. It can be used for both creating both base gold images that can then be fully built on later or fully built imputable images.
I see an octopus step being able to be used to:
1) create or pull (from a repository) & update a json template with variables & transformation.
2) next packer validate
3) packer builds the image.ideally, there would also be an "Octopus" provisioner for packer that would allow the download of repos, call templates, transforms, variables install tenticle via cli
but even it…
6 votes -
Export Audit as JSON
When I use the Export function in Audit, the Details column is a mix of HTML and JSON.
For example:<span>{<br> "Id": "variableset-LibraryVariableSets-76",<br> "OwnerId": "LibraryVariableSets-76",<br> "Version": 11</span><del style="background:#ffe6e6;">5</del><ins style="background:#e6ffe6;">6</ins><span><br>}</span>
I understand that this is a way to show what the changes were, but this format is only usable for display in HTML, not for parsing the exported audit via any tools.
Would it be possible to export this as JSON and indicate the change in some other, structural way?
E.g.{ "Id": "variableset-LibraryVariableSets-76", "OwnerId": "LibraryVariableSets-76", "Version": { "OldValue": 115, "NewValue": 116 } }
Or in any other way which would…
1 vote -
Add support for Venafi (Security and SSL) Certificate management
We use Venafi (https://www.venafi.com/platform/trust-authority) to issue and manager certificates. It would be great if Octopus could integrate with this system to allow for issuance, import and storage of new certificates for the sites we deploy.
1 vote -
Do not warn about changes to the audit trail when running a Runbook Snapshot
The Run page when Running a Runbook Snapshot always has a "Something has changed since this runbook-snapshot was taken" warning. However, the warning might only be about the audit trail of the Runbook Process. Won't the audit trail change with every run? If so, I think this warning is a false positive.
1 vote -
Trigger Deployment Through Azure Function
Deployment trigger options are currently limited. It would be nice to trigger a deployment by executing Azure Function which would queue the request using Azure Service Bus. In this case Octopus Deploy would listen for a queue message to start a deployment.
This solution would allow for various creative integrations within Azure.
3 votes -
Option to hide Spaces in navigation
Just upgraded to 2019.1 - the Spaces navigation item bothers me a lot. We only have one space, and don’t want more spaces (and won’t upgrade our license), yet I can’t seem to find an option to remove this. Something to add under Configuration > Features?
28 votes
- Don't see your idea?