315 results found
-
Scope variables by Date
Add the ability in the variable editor to set a variable value to only be used during a specific date range. Dates should be able to exclude year. "Every Oct, Nov, Dec" for example.
1 vote -
Move the Load More/Load all buttons to be closer to tenants
In multi-tenant implementations, the Tenants screen only shows 30 tenants. When the left side list of Tenant types, upgrade rings, hostings, etc, exceeds the height of the list of tenants, the "Load More and Load All" button/link is pushed to the bottom of the page and requires a user to scroll to see there are more tenants to choose from. This has caused us to miss several tenants when making configuration changes because it looks like we are seeing all tenants on the screen.
I have a screen shot but I don't know how to submit it.
2 votes -
Add security secret cleansing to Artifacts
When Octopus attaches Artifacts it does not screen the for any secrets or credentials as such these can often compromise accounts etc that are used to create that Artifact, depending on what it is and how its made.
It would be great if before Octopus attached the Artifact it looked to screen and cleanse the Artifact of potential Secrets there fore reducing the risk of it been used for security exploits etc.
5 votes -
Clarify boolean logic of tenants & tenant tags on deployment targets
Multiple users at my company have encountered a fairly dangerous deployment target configuration behavior that isn't very clear in the UI. When you configure tenants and tenant tags on a deployment target, the logic is:
Specific tenants OR (tenants tagged <abc> AND <xyz> AND <etc.>).
The dangerous part is the OR. At first glance, beginners at my company have assumed that the tenant and tenant tag fields all have an AND relationship, so they select a specific tenant and various tenant tags that apply to that tenant. They assume this is straightforward, so they don't click the preview button that…
2 votes -
Add Export/Import buttons in project UI
We have dev and prod instances of Octopus Deploy. I’ve created a deployment project on the dev and then we needed to copy it to prod. We didn’t find Export/Import buttons in project UI. My colleague opened https://octopus.com/docs/api-and-integration/octo.exe-command-line/export page and told, that it’s too complicated and it will be easier to manually duplicate all steps on the prod Octopus Deploy.
Could you please add to project Octopus UI Export/Import buttons , that will provide same behaviour as octo.exe CLI. It’s ok to implement just the simplest scenario with default parameters and have a note “if you need more control, use…
4 votes -
Define permissions on the project level to enable multi-tenancy to where a customer can access the Octopus server for their UAT environment
Define permissions on the project level to enable multi-tenancy to where a customer can access the Octopus server for their UAT environment and not see other projects and not able to make global config changes.
1 vote -
Octopus Cloud - Packages - shift click support with packages
It would be nice if you could shift + click to select a range of packages to delete in the Library > Packages for a given package.
0 votes -
Octopus Cloud - Packages - show total amount of space used
It would be nice to be able to see how much space packages are taking up for an Octopus Cloud instance and whether you are reaching the max amount allowed. The maximum space allowed in Octopus Cloud is not documented I believe.
It might be helpful to have this knowledge so we know when to use Octopus Cloud's built-in repository to host packages versus utilizing an external package feed from elsewhere.
3 votes -
Display operating system version information on the Deployment Targets page
It would be useful to see what operating system and potentially which .net framework versions are installed on a deployment target. I've got a variety of different server versions and in order to pick a baseline .net framework version I need to work out the oldest OS.
10 votes -
Allow retention policies for packages only
Retention policies are great because our storage usage is getting insane with our hundreds of projects. Retention policies aren't being used because the release history/audit trail of previous releases is considered too valuable to remove.
Implement a package-only retention policy where old packages can be automatically removed, but without the need to delete associated releases first.
2 votes -
It would be convenient if the Tenant had a Description field for explanatory text.
It would be convenient if the Tenant had a Description field for additional text describing the purpose of the Tenant. (Much like the Projects that have a Description field to provide extra info.)
1 vote -
Default channel should be configurable
when we have channels, you can select to group by channels or no grouping. We want it possible to per project or per user to be configurable what grouping to use.
1 vote -
Certificates are too restrictive for Tenants
Currently if you choose "Include only in tenanted deployments" when adding a new Certificate to your library you are required to:
A) Select all of the tenants to be associated with that Certificate
B) Select a Tenant Tag to associate with the certThis is restrictive. Why can't all Tenants just have access to the Certificate? When you only do Tenanted deployments you have to remember to tag the newly created tenant or go back to the cert and add them to the list. Its cumbersome to maintain.
There should be a toggle for ALL tenants on the cert.
1 vote -
export custom role permissions
We have a use-case whereby we need the same permission sets for a custom role across multiple instances of Octopus. So when setting up a new Octopus instance it would be great to be able to export that custom role from one instance and apply it to the other.
1 vote -
Synchronize external security groups task should ignore users that are disabled in check,
Currently task "Synchronize external security groups" flags all non-existant users with a warning/error. This is the case even if the user has been disabled. the check should do either: Ignore user if disabled and not in "AD" or report error if user exists in "AD" but is disabled in octopus.
1 vote -
icon
Change the icon on the dashboard for deployments stuck on actual Manual Intervention steps and ones stuck on Guidance Failure steps
1 vote -
White background behind logos
I added over 60 logos in an earlier version of octopus, many had white backgrounds rather than transparent, now they all look a bit off against the pale grey background.
Ok ... this is a tiny thing but thought I'd mention it.
0 votes -
Package Library Wildcard Search
When searching for a Package in the Library permit the use of wildcards to optimise the searches.
We have prefixed our packages with the names of our clients and it would be great to view all packages where acme* would return all acme packages
1 vote -
Add the ability to group tenants
I think it would be a good idea to have the option of grouping tenants for the purpose of organisation and not deployment:
- A group does not have the functionality other than to group items
- Grouping is optional and you would always be able to interact with tenants in the same way you do now
- Groups have a name, description and maybe an image
- A group can contain tenants and/or other groups
- Tenants do not need to be in a group
- Being in a group does not functionally affect the tenant
The scenario:
- I run a business that puts up…
1 vote -
Tenanted Variables
After upgrading to this new version of Octopus, with the new UI, the configuration of tenanted variables became very counter-intuitive, it's very heavy while loading multiple projects and the color pallet makes it even harder to understand which environment is which, but the color pallet it's an issue in general with all of the UI of this new version, it's very confusing as you cannot distinguish easily between projects, tenants, variables, environments, etc.
1 vote