Skip to content

Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

1452 results found

  1. Variable sets should have Tenant support. Such variables to have a Tenant scope.

    This would allow common vars to be reused via variable sets. This should be a common requirement for multi-tenanted microservice setups. Without that you either have to have variable copied or have them all defined at the Tenant level. Both bad options.

    A work around is to have variables as #{if TenantName =="A"}TenantAValue{#/if}#{if TenantName =="B"}TenantBValue{#/if}
    this is pretty ugly and it doesnt work for snesative variables as far as I know.

    I know this tricky to implement but really important IMHO

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tenants  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. It would be very helpful if you provided an octopus github app in the github marketplace as a way to auth when using github feed/github credentials.

    Azure Devops and Terraform cloud currently provide this functionality and it is very helpful as it acts as an organisation service account rather than any 1 individuals account.

    Currently if I create a PAT token for octo to use and then I leave the company that puts the other development teams in a bit of trouble, not to mention the security implication of any other user in octo being able to act as me.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. We want to be able to use a trigger to create and deploy a release of a project (using a specific channel).

    At the moment the project relies on a prompted variable so we are unable to do this.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Currently it’s possible to limit rights of a Team to specific tenants but not to a tenant tag. With ~20 tenants and more it's really hard to maintain this. Also the list would become so long. It would really help to specify just the tenant tag.

    In our case we have only one risky tenant which should be assigned to a small Team. But we have to add all 19 less risky tenants to the bigger Team.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Tenants  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. When running a Runbook and only one tenant is available the tenant is automatically selected and a checkbox is shown saying "Skip tenants where Snapshot Y7484HM is the current version deployed to ExampleEnvironment". It's checked by default.

    However when deselecting the tenant and selecting it again this checkbox doesn't appear. It seems like it's connected to the automatic selection of the tenant which is strange.

    Additionally it would make sense to have this checkbox disabled by default (or configurable) because Runbooks are for routine tasks (as the website says) where we WANT to run the Runbook multiple times (although there…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Runbooks  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. We need to forward Octopus Deploy Audit Logs to a Syslog Server. It will be grate if there will be an option to configure log forwarding to a syslog server in Octopus Deploy administration page.

    We need this feature because we are a payment facilititator and we need to store all of our logs in a centralized log server like syslog servers. This feature will help us to comply with PCI-DSS standards and our local legal authorities.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. We have custom urls that are generated in some of our deploy scripts - unfortunately the user has to copy and paste the url from the log into the browser currently.

    I would be nice of the logging functions supported markdown so we could just click a link to go to the url, or we could format our logs more effectively.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. When a release's snapshot gets stale, Octo will provide a warning when deploying the release to alert the user that the snapshot is out of date. I currently click the linked release, update the variables, and then go back to the deployment page. However, it'd be very nice to have some way to update the snapshot for the release from the deployment page itself and save a couple clicks. Could be something like a button in the warning modal that would do this.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. We'd like to implement Canary Deploy in some of our projects.

    We have seen and tried different methods but for our needs the best solution would be this one:
    go, during deployment, to select the canary target and start the deployment only on that target(s).

    It works fine, however the problem is that at the end of the process we see the outcome in green and this is very misleading because in reality the deployment was successful but only on the selected target(s).

    We tried to manually edit the status but it seems it is only possible to put in…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Hi,

    I have been looking at getting out deployment process under version control for our main project.

    I have successfully integrated Octopus with Azure Devops Repo and created a test project under version control etc.

    From what I can see, the entire deployment process is written to a /.octopus/deployment_process.ocl file, including any inline PowerShell scripts.

    For example:

    step "Swap Staging and Production Slots" {

    action {
        action_type = "Octopus.AzurePowerShell"
        properties = {
            Octopus.Action.Azure.AccountId = "#{AzureAccount}"
            Octopus.Action.Script.ScriptBody = <<-EOT
           ….
            ….
            …. 
            Lots of powershell coding
            ….
            ….
            ….
            EOT
            Octopus.Action.Script.ScriptSource = "Inline"
            Octopus.Action.Script.Syntax = "PowerShell"
            OctopusUseBundledTooling = "False"
        }
        worker_pool
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. A concept of a commit generally includes author information, however this information does not seem to be currently available in Octopus.

    Having commit author in Octopus would be useful for notifications during deployment process, and for attribution in release notes.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add support to enable multi factor support to users.
    Now more than ever we need to protect our Octopus Deploy instances as it is more and more becoming the keys to the kingdom.
    Support for Authy/Google auth plus DuoSecurity would be a good start

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. When the user has an ongoing deployment visible in his/her browser, it would be great if we could add the possibility to play a customisable sound at the end of the deployment: deployments can take a very long time to finish and who runs the deployment interactively is definitely interested in being notified right after the deployment completes for various reasons. Please add this functionality to the product.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Today, there are several levels to manage variables in Octopus, and it's a good thing:
    - Library variable sets
    - Project variables
    - Tenant variables (thanks to variable templates)

    I think you should really simplify this process to manage all of them from Library variable sets only. Indeed, when you create a variable from this section, you can link it to some environments, some targets, and some target roles. If you add the possibility to link it to tenants and projects, it's win :)

    Doing that would also allowing to set tenant/project variables only to some environments, that is not…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Add additional Authentication Providers for Octopus Cloud such as AWS Identity Center or LDAP for Users hosting there infrastructure on AWS

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Administration  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. On the release Overview page, it would be nice if the DEPLOY... button was enhanced with a context menu that as an option that behaves as it does now (navigates to release page).
    Having the "DEPLOY [↓]" deploy instantly without navigating would save some clicks when there are many channels.
    Perhaps there already exists a feature to deploy all channels to "next stage".

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. I’m actually working on a project where I need to deploy an ECS Service that uses a different FireLens configuration but the current ECS deployment step by Octopus Deploy does not support that configuration.

    AWS Docs: https://docs.aws.amazon.com/AmazonECS/latest/userguide/firelens-taskdef.html

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. I could not find any way to get the branch name for a release in the given environment for a Project.

    My requirement: There are around 40-50 projects in my organization, there are different-2 environments like Beta, UAT and Production. and source control branches are also different-2 for each environment and there is no naming convention followed by people. So It's very hard to know for a given project and environment what is the repository and what is the branch name.

    I tried with Octopus. Client library, But could not get this information. So it would be great to have…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Prompted variables are defined manually, the idea is to add the option of filling the values with information of an external source.
    For example, fill a Drop Down prompted variable with the values from a column of a MSSQL table.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. So in our scenario we have multiple tenants and each one has 6 or more environments which are attached to the tenant. In the overview screen we see the list of tenants on the right hand column and the environments as the column header and their current version along the row. What we really need so that we don't get confused to which site we are deploying is some additional metadata on the overview screen so we can at a glance see something like what ownership of that deployment or what that deployment is for.

    So to explain I have…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Projects  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 72 73
  • Don't see your idea?