General
-
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…
78 votes -
Obfuscate sensitive variables in deployment log in variable substitution
We're using various steps for deployment ('Deploy a package', 'Deploy to IIS') which both have variable substitution options to substitute variables in Web.config/App.config.
During deployment, i've noticed that these substitutions are logged. However, sometimes i see that our sensitive variables are being logged here at 'verbose' level. Other sensitive (and also non-sensitive) variables are obfuscated.
It seems that the deployment process decides by itself based on the name of the variable. In my opinion, the sensitive option of the variabel should be considered here as well.
An example of what we've got currently:
We've got an appsetting in our app.config,…3 votes -
Filter Environments shown in each Project Group on the Dashboard
Filter the environments show in each project group on the dashboard. Only environments included in the lifecycles/channels for each project in the project group should be shown.
We have many environments but most are only used by a few project groups. Some project groups only deploy to a single environment. This requires us to horizontally scroll far to the right past environments which aren't capable of being deployed to in order to see what is deployed.
4 votes -
Terraform support for SSH Workers
Currently the built in terraform steps only support Windows workers. It would be good if the steps were platform agnostic and able to run on any worker.
9 votes -
Cleanup Application folder for versions that have no corresponding release any more
We noticed that the automatic cleanup of C:\Octopus\Applications apparently does not cleanup versions where no corresponding release exists any more (e.g. because we only played around and afterwards deleted the release without manually cleanup up the C:\Octopus\Applications folder).
It would be really cool if the cleanup would also cleanup versions for which there is no corresponding release.
3 votes -
Allow machine policies to be set for Azure WebApps
I would like to be able to customize the Health Check of Azure WebApps deployment targets. For example I would expose an endpoint
/health
that must be queried on an ~hourly basis. In the case of a Tentacle this is possible using Machine Policies, but I can't assign one to a Azure WebApp deployment target.3 votes -
Production Deployment Notification
I would like to receive an email notification when a PRODUCTION deployment is taking place.
1 vote -
Tag AWS ECR (Elastic Container Registry) images from a feed with a deployment tag
Amazon's ECR (Elastic Container Registry) is a docker-compatible registry that you can configure as a first-class package feed in Octopus. Part of the ECR product (in AWS) is to set up lifecycle policies so it can automatically delete old images (since it takes up space for each image). This is a similar feature that Octopus offers on its own built-in package registry, but the ECR is obviously an external registry so the purging has to managed by AWS (and no Octopus). But ECR has no way of knowing which images are used (so they won't get deleted), except if you…
2 votes -
Approval Role
I'm not seeing things specifically, but it would be nice if there was a role which was Release Approval Only Role. To allow a certain set of users to just approval releases to go to the next environment in the life cycle.
1 vote -
Re-label or remove the "Automatically run configuration transformation files" checkbox
The label of this checkbox is slightly confusing - it led me to believe there was a manual process for applying transforms too. Given that when this box is ticked, a default set of transforms are applied, and when it is not ticked, those default transforms don't run (but transforms listed in the additional box DO run) and the process is always automatic, a label like "Apply the default set of transforms built into octopus" might be better. Alternatively, consider removing the checkbox entirely and just putting the pre-programmed defaults (Web.Release.config => Web.Config, Web.#{Octopus.Environment.Name}.config =>Web.Config) into the box as a…
3 votes -
Octopus Server API versions & related components - Compatibility Table
Firstly, thanks for working on and improving upon an already great product. Now to the feedback at hand, I am currently investigating making use of the .NET Octopus.Client within a project to manage the octopus deploy server. As part of that investigation I was trying to gain a better grasp of the compatibility of the various Octopus Deploy (OD) server versions and the related components. That led me to the current page, https://octopus.com/docs/api-and-integration/compatibility which though useful at first glance, it was not clearly defined upon further investigation. Since I'm looking to use the Octopus.Client component let's example some questions for…
3 votes -
Deploying files
The only thing Octopus should do is deploy files, correct?
Can we just deploy files with a polling tentacle without an issue?
Fair enough I am deploying to sites with low connection speeds, but even windows remote desktop connect can copy the files without an issue but Octopus can't!!!!!?
Can we just do that?But thank you, even dow it sucks at polling it still remains the BEST, great program awesome way for deployments.
1 vote -
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.
35 votes -
Allow Scheduled Deployment Triggers to not re-deploy if targets are up to date
Currently, the Scheduled Triggers option allows setting a time to deploy, and even includes examples in the documentation for "nightly deployments." The downside currently is that it will re-deploy every single night, even if the environment was already successfully deployed to.
It would be nice to add an option to only deploy if the environment / targets need it done. This would allow for a real nightly promotion without excess deployments and logs.
17 votes -
terraform
Terraform step templates for Azure deploys. Currently only AWS is supported in Octopus included step templates. It seems like an easy addition to the existing functionality
12 votes -
Rolling deployment parallelism per role
We have an service environment right now that consists of two data centers that each contains 3 servers that host the services. These services hosts host 100+ services each and each server is hosting exactly one instance of each service; so they are in effect mirrored.
When we deploy to these servers, we do it one data center at a time. Since there are so many services per server, we can’t just remove the server from the load balancer. Also since we do round robin load balancing and want to have zero downtime and keep consistency in our responses during…
3 votes -
Display channel description when creating a new release
The selected channel's description should be displayed when creating a new release, otherwise a user may miss important information that is not fully conveyed by the channel's name. Currently a user would have to navigate to the separate channels tab to see this, which breaks the UI flow and which they may not necessarily do.
5 votes -
Add variables substitution capabilities
We keep our deployment configurations in octopus variables and use json substitution the replace them on deploy time
This could be improved in a few ways:
- Use the json variables substitution feature on other step templates than deploy a package (for example: run a script)
- have to ability to substitute also yml files
- give a variable a null value, the only option now is tho give him empty string, which influence the code.
25 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.
35 votes -
Dark theme
It would be great to have the option to switch to a dark theme
148 votes
- Don't see your idea?