General
-
When deploying project containing Deploy Release step, allow previewing steps and excluding machines from child deployments
Currently when deploying a project containing one or more Deploy Release steps (https://octopus.com/docs/deployment-process/coordinating-multiple-projects/deploy-release-step), there is no ability to preview the deployment steps that will be executed in the child deployment, nor the ability to exclude machines from the child deployment.
It would be nice to surface this information on the create-deployment page of the parent project.
23 votes -
Make variable list usable for configuring IIS bindings.
When adding a binding to IIS in Octopus, you can only use seperate variable. Every binding needs a new variable. Some of our deployments have over 50 bindings. We create each binding separate. If we use a variable list only the last item of the list end up in de IIS binding. It would help us a lot if we could ad three generic bindings (Test, Acceptation, Production), en in the bindings use a variable list, containing all the IIS bindings.
43 votes -
Highlight the variable Snapshot difference while updating the release snapshot
Whenever there is a change in the variable after the creation of the release, we used to get warning saying "Release Snapshot has been changed". But we do have only one option to update the entire release without knowing what has been changed. It would be great if you have any way to find/highlight the variables and their values that will be updated when I click "Update Variables" in the release Snapshot section. It will minimize the risk when it's comes to updating the snapshots for production deployment and it will give a transparent view of what changes are done…
35 votes -
Integrate Octopus deploy project variables with Azure Key Vault
So sensitive project variables will be referenced from Azure Key Vault instead of being stored in octopus.
https://azure.microsoft.com/en-us/services/key-vault
3357461 - 'Azure Resource Manager Key Vault support' was only about ARM template Key Vault support.
17973586 - 'Integrate Octopus deploy with secrets managment system Vault' is similar to this issue only for https://www.vaultproject.ioThis idea is similar to
https://docs.microsoft.com/en-us/vsts/build-release/concepts/library/variable-groups?view=vsts#link-secrets-from-an-azure-key-vault-as-variables22 votes -
Configure path package is deployed to
Hi,
I have set up Deployment process and everything works fine except one thing.
I cannot find a way to edit step "zero" - downloading and unpacking of deployment package (nuget package).
In our deployment we process multiple tenants on single environment.What Octopus currently does (this process seems automatic to me):
- Downloads correct package version if its not already downloaded (this is ok)
- Unpacks it into C:\Octopus\Applications\tenantName\Production\projectName\projectVersion (want to change this)
- Then uses this folder as source of data (ok).I have TWO problems with this approach:
1)
while deploying on multiple tenants after ONE deploy…95 votes -
Deployment Pipeline as Code
I would like to see the "pipeline as code approach" applied to projects. The main idea is to be possible to define the process of a project using a yml file in a source code repository or package.
33 votesWe like this idea too.
-
Deploy to Service Fabric
The 'Deploy to Service Fabric' process does not provide all the available security mode options available in Service Fabric, we are doing a POC around an on-premise SF cluster using a gMSA which the Fabric will run under the context of and Windows Identities to allow client-to-node communication. the option for using Windows Credentials (in this case it would be the Windows Service Account which Octopus is running under the context of) to connect to the cluster is not available! i.e.
Connect-ServiceFabricCluster -ConnectionEndpoint <cluster-domain-name | server hostname>:19000 -WindowsCredential
9 votes -
Your latest version is disaster!
Your latest version is disaster! Total disaster!
7 votes -
Support multi-package deploy steps
Allow package deploy steps to select multiple packages that are deployed in the selected order (with the ability to change the order). We have a website where we deploy a clean copy of a vendors files (makes upgrades easier), then we overlay different 3rd party modules and our solution into the same folder. These packages together create a whole website.
9 votes -
Dark theme
It would be great to have the option to switch to a dark theme
65 votes -
Add repository retention feature for external feeds
Add repository retention feature for external feeds. I'd like to be able to manage package retention on external feeds in the same way that they are managed for the internal feed automatically deleting unreleased packages after a number of days
7 votes -
On Dashbaord always show Environments & Projects
When working with a large number of projects & environments, it easy to get lost if you are scrolling horizontally and verticle, If you were looking for a specific project in a particular environment.
3 votes -
Clone channel
It would be very useful to be able to Clone a Channel.
18 votes -
Allow customisation of the CSP Security Header
Or let images come from any source.
6 votes -
Make "Include a Script Module" search dialog case insensitive
The search is case sensitive when searching for a script module in the "Include a Script Module" dialog from the Process page.
I think this should be case insensitive.
2 votes -
Display Deployments Requiring Manual Intervention for a Release
When viewing details for a particular release, we used to be able to see any active deployments that are currently awaiting manual intervention. It seems this is no longer visible in Octopus 4.0. In order to view this, we need to go back to a project's "Overview" to see any deployments that have pending intervention steps to approve. This complicates the workflow.
17 votesNithin are you talking about in the release page? If so then the deployment status should already be visible, including if it's paused for manual intervention (icon looks like an eye). Could you log a ticket through supportoctopus.com along with screenshots so that we can investigate? -
In a master project that includes Deploy Release steps, allow variables to override values in child deployment
In a master project that includes Deploy Release steps, we can define per deploy release step variables that will be available to steps within the child deployment's process.
We'd like to have variables on the master project level that will override the same variables child deployment's process so we won't have to do it for every step.
For example - if I have a master project with 10 deploy release steps, and each step has a db connection string variable, currently i have to go into each deploy release step and update the connection string. We'd like to see it…1 vote -
Allow tenants associated with only disabled deployment targets to be disabled
We would like to be able to pick a tenant tag and deploy to tenants on enabled targets without error. As it is, we receive "<tenant> has no deployment targets in <environment>" errors for those tenants associated with disabled targets.
1 vote -
Scope private key access of the certificate step
Private Key Access which define who has access to the private-key on the target machine on the import certificate step could have a scope option.
So each environment different certificate with different user and permission3 votes -
Make display customizable
The view of the latest version is awful. Please make it customizable either at a site level or based on the logged in user.
1 vote
- Don't see your idea?