-
Create a step template that applies config transformations
Have an entry field that accepts the same sort of content as is seen in the transform window here: https://webconfigtransformationtester.apphb.com
as well as maybe a file pattern/name to match the transformation to.This way one can avoid building multiple instances of an application, one for each build configuration (environment), transforms don't happen at build time and can take place as part of a deployment.
2 votes -
Enable one to be able to iterate a list of last installed directory paths for steps in project
Create an Octopus variable that contains the last installed directory paths for the steps in the project. This becomes useful if you have one step that deploys and another that works on the previously deployed step, but for some reason you deployed one set of steps first and later the remaining steps.
1 vote -
Display just the variables applied to a release on the release's page
The Variables section a Release page appears to show all variable that apply to the release, would it be possible for any variables which are obviously being overwritten to be omitted from this list?
As an example, if I have a variable in a Library which is being overwritten by this particular project, at the moment both will appear in this list.
2 votes -
Configure Default Deploy Options
It would be nice if you were able to configure defaults for deploy options. Currently they are all false by default. I never really had a need to check any on a regular basis until Guided Deployments are introduced but now I find myself checking this option with every deployment, which isn't optimal. I'm not sure if it would be best to be able to configure these on a per project level or perhaps project group level but it would be nice to configure their defaults somehow.
1 vote -
Allow override of appVersion during Helm upgrade step
appVersion for Helm charts cannot be overridden with command-line arguments, which means the new version must be overridden before packaging the chart, which causes a new chart version per application version.
There are workarounds for this, but those cannot be done with the current Helm upgrade step.1 vote -
Add channel to the deploy release page
On the deploy release page (the one that shows just before actually deploying a release) the channel (if any) is not shown anywhere on the page. Would be very useful to avoid mistakes when deploying.
0 votes -
Deploy in "Debug Mode", pause after each step
It would be useful to be able to run a deployment in "Debug Mode", where it would execute one step at a time, pausing after each step, so a developer can verify that it is operating correctly.
0 votes -
If a step failed on a specific Target / Tentacle remove it from the list of targets for future steps
It would be configurable and we could leverage the existing functionality of how the Health Check steps take targets out of the list for future steps.
0 votes -
Provide access to account credentials during deployments
When a deployment is being executed, there may be some value in providing access to account credentials that have already been stored and managed in Octopus Deploy.
While the primary motivating factor for creating the accounts section has been to provide access to deployment targets, some users may get value from using them to access or control other parts of their deployment process that sit behind some authentication mechanism. This would allow OD to better manage all the resources needed to fully complete a deployment with authentication details being securely managed in one place.
The biggest concern with this approach…
0 votes -
Multi-select tentacles for changing environment/roles
Enable a way to make a changes (add/remove environment, add/remove role) to multiple tentacles at once.
0 votes -
Hide Release
Over time, older releases that are no longer in use just crowd up the release screen. I want to retain their history, so do not want to delete them.
It would be nice to be able to hide releases.
0 votes
- Don't see your idea?