1457 results found
-
when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run
when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run.
idk what you call this icon with the orange square and white lightning bolt
but when the lifecycle is in this state, the save button really means, “go ahead and run”.
1 vote -
Deployment Email Preferences by User
Allow each individual determine what deployment emails they want to receive. Users on multiple teams, or large deployment teams, are bombarded with hundreds emails a day. Giving the user the ability to tell the system they only want to receive failures, or no emails at all, would provide a better user experience. Alternatively, if this is not possible, allowing the system to have a single designated email for deployment notifications. This would allow the users to designate something like a Teams Channel to receive the notifications, and cut down on the amount of emails being sent in general.
12 votes -
Allow variable set assignment through variable set
Currently when a new variable set is created, it has to be included in projects individually. When there are many projects that should include the variable set, it would be much more convenient if the set could be included in projects via the 'usage' tab.
1 vote -
I need to Set a Project variable from a PowerShell step so that i can use the variable in an arm template parameter file as a substitution
I need a step A that set a project level variable #{COLOUR} from powershell and/or bash such that when I run an arm template step within the same deployment the parameter file correctly substitutes the value of #(colour} during the arm template deploy.
1 vote -
Organize Runbooks in a folder structure
In our more complex deployment project, we heavily depend on runbooks to update configuration, check parameters, run clean-ups, change certificate, and and and.
It is very hard to keep an overview in a long and unstructured list and it would be immensely helpful if we could organize runbooks a folder structure.e.g.
|- Certificate
| |- verify chain
| |- change cert
|- Database
| | - create backup
| | - run maintenance
|- Configuration
| | -rewrite config
| | -verify config... and so on
1 vote -
Add tenant tag support to runbook scheduling
Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.
11 votes -
Add support for Keyfactor (Security and SSL) Certificate management
We use keyfactor (https://www.keyfactor.com/platform/certificate-lifecycle-automation/) for Certificate lifecycle Automation. It would be great if Octopus could integrate with this keyfactor to allow for issuance, renewal, inventory, import and storage of new certificates.
1 vote -
Dashboard should be better at visualizing multiple tenants
Currently the home dashboard displays tenants as a small grey-on-grey count of up-to-date tenants vs total tenants. It would be nice to see a coloured pie chart or similar visualization instead, to make it more obvious when one tenant in an environment is still running an old version or has had a failed deployment.
It can be easy to miss failed deployments from the dashboard screen.2 votes -
Add the ability to disable specific environments to all but system administrators
When we're doing mass maintenance to an entire environment, it would be useful to be able to disable non-admins from doing things to that environment, and display a banner (e.g."Deployments to production are disabled while servers are being re-racked") without stopping activity in other environments.
Looking for something much like the system-wide maintenance mode, except environment specific.
6 votes -
Add Migrate options to API Import
First I want to say that the new API functionality added in latest versions is very appreciated especially the possibility to export/import project out of spaces. However we really miss the merge functionality when importing project from Non-prod octopus to Prod Octopus
Our current automated procedure includes : Delete project-> Re-import Project-> Update prod variables
Problems: It removes history and require a new release number in prod due to updated of variables.
Addition to this feature requests includes: Exclusion of environment variables in export
1 vote -
Custom advanced variable substitution filters
Add ability to define custom substitution filters that can run scripts defined by the end user.
1 vote -
Install Example using CloudFormation and ECS
In the installation documentation there exists a helm chart example:
https://octopus.com/docs/installation/octopus-in-container/octopus-server-container-linuxAre there any existing examples of doing something similar, but using CloudFormation/Fargate/ECS to run the server + tentacles?
1 vote -
When cloning a process step to another project the list in not ordered or searchable.
Add a filter search to this dialog, and order the dropdown contents alphabetically.
Version: https://octopus.com/downloads/2020.6.4855
Also put a copy icon next to your version number.
2 votes -
Support environment variables for all `octo` CLI commands / flags
I posted about this as a GitHub issue as well (https://github.com/OctopusDeploy/OctopusCLI/issues/142). Basically, it would be nice if the
octoCLI could read environment variables for all of its commands and flags. This would make CI easier since values could be easily changed and tested without having to make code changes.Thank you!
1 vote -
Enable process scoping within library variable sets
Project variables may be scoped to a process to differentiate between variables used for deployment and variables used for runbooks.
I would like to be able to define process scope for variables within library variable sets so that library variables intended for use in deployments do not pollute my runbook process.
1 vote -
Add a data field of Team Owner or Manager (of type User) into the Octopus Teams settings tab.
Due to SOX Auditing, we have a bi-yearly user access review of everyone who has deployment permissions. We have automated this with Powershell and the Octopus API so that we can generate an excel spreadsheet to upload to Sharepoint for Managers to approve individual user access.
However, this has created a problem, there is no easy way to mark Team Ownership or a Team Manager as a simple user data field in the Teams' settings so that we could populate Sharepoint with the name of the person responsible for approving each users access.
Having a Team Owner or Team Manager…
1 vote -
Allow custom deployment scripts for Terraform steps
Currently it it not possible to script additional actions when planning to apply or applying a Terraform template. This means that additional steps are required to carry out simple takes like importing an exiting resource before planning, or uploading a saved plan to S3 so that it can be pulled and applied.
Many other steps have this configurable feature, and I believe it would be highly effective here.
Suggestion -
- Pre-deployment script runs before 'terraform init' (allowing download of plan from S3, for example).
- Deployment script runs after 'terraform init' (allowing 'terraform import' after the template has been…1 vote -
Download package option to only keep latest in cache
There are currently 2 package download options when deploying a release: using the package from the cache and always re-downloading. Both of these are useful, but each has one big downside that I think this feature would correct.
When using the package cache, Octopus will never pick up changes that were made to the same version of the package. If forcing a re-download, the package cache can quickly fill up, especially with multiple development teams (and yes, we have retention policies configured -- our packages are unfortunately quite large).
A new option that will just always re-download and keep a…
2 votes -
Add parameters to Runbooks
This would be like runbook specific variables, but they are defined on the runbook and don't make sense to be in the published snapshot. They would generally be prompted values, but that shouldn't be required. They would be "snapshotted" when you run the runbook. When you are scheduling runbooks with a trigger, you should be able to provide values to use when the runbook is triggered.
For an example use of these, we have a Runbook that exports data from a database to a CSV and emails it. We have variables for the from and to dates and the email…
8 votes -
Reorder Tenants
Make it so we can reorder tenants. We have 200 of them and having to scroll down to find our "Internal" tenant is silly. Renaming it to "0 Internal" to make it appear at the top looks hacky.
2 votes