Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. When you configure a "Run a Script" deployment step, you can reference a package, and add the "Substitute Variables in Files" feature. Within the help text it says "A newline-separated list of file names to transform, relative to the package contents." which is inaccurate:

    For me, using a simple, relative path here e.g. "index.html" didn't work. I needed to use the full extracted path of the package e.g:

    {Octopus.Action.Package[EdibleCode.Something].ExtractedPath}\index.html

    Also, you can reference multiple packages for a a run a script template, in which case "relative to the package contents" doesn't make sense and needs clarifying.

    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)
  2. When I use the Export function in Audit, the Details column is a mix of HTML and JSON.
    For example:

    <span>{<br> "Id": "variableset-LibraryVariableSets-76",<br> "OwnerId": "LibraryVariableSets-76",<br> "Version": 11</span><del style="background:#ffe6e6;">5</del><ins style="background:#e6ffe6;">6</ins><span><br>}</span>

    I understand that this is a way to show what the changes were, but this format is only usable for display in HTML, not for parsing the exported audit via any tools.
    Would it be possible to export this as JSON and indicate the change in some other, structural way?
    E.g.

    { "Id": "variableset-LibraryVariableSets-76", "OwnerId": "LibraryVariableSets-76", "Version": { "OldValue": 115, "NewValue": 116 } }

    Or in any other way which would…

    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

    1 comment  ·  Installation  ·  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. Packer is a versatile tool, especially when working in a multi-cloud environment. It can be used for both creating both base gold images that can then be fully built on later or fully built imputable images.

    I see an octopus step being able to be used to:
    1) create or pull (from a repository) & update a json template with variables & transformation.
    2) next packer validate
    3) packer builds the image.

    ideally, there would also be an "Octopus" provisioner for packer that would allow the download of repos, call templates, transforms, variables install tenticle via cli

    but even it…

    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

    2 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)
  4. Native integration with ServiceNow so teams can link releases to change requests and pause deployments to production until approvals are met.

    20 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

    5 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)
  5. When iterating through a collection variable using #{each var in array}, it would be helpful to have a sort by pipe
    Eg: #{each var in array | orderby var.property}

    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)
  6. We've been trying to ensure that any 'Step Templates' created in Octopus contain scripts/code (PowerShell) that exists within a package. That package is then referenced as part of the 'Step Template'.

    The problem we have with this is that as soon as the package is pushed, it then gets used in any new releases. This means that we have no opportunity to test this in Octopus prior to new releases in pipelines using it.

    It would be useful if within the 'Step Template' we could specify/fix the package version (or specify a range) used so that all other pipeline releases…

    6 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

    1 comment  ·  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)
  7. Deployment trigger options are currently limited. It would be nice to trigger a deployment by executing Azure Function which would queue the request using Azure Service Bus. In this case Octopus Deploy would listen for a queue message to start a deployment.

    This solution would allow for various creative integrations within Azure.

    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  ·  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)
  8. When steps are executed, right now it will show a green check if success or a red x when a step fails. It would find it helpful to know which steps actually deployed a new package to a deployment target vs. those that didn't do anything because the package was already deployed to the target. This could just be another type of indicator. Right now it just shows success whether it deployed a package or if it already existed. You have to drill and review the logs to determine which path happened.

    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)
  9. It would be nice to visually see the Steps that will be deploying a different package than the last one that was in a release. This could be done by just highlighting the row in a different color.

    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)
  10. Imagine you have a connection string variable and you want to update it. You would update the variable and redeploy, however if you made a mistake (edited the wrong variable or the new connection string was not live yet) then you cannot roll back. This is even more of a problem if the variable is sensitive as you can't copy it beforehand.

    I would like to be able to version octopus variables, this would include:
    - Who
    - When
    - When deployed
    - The ability to roll back/forward.

    At the moment we have to source control much of this type…

    67 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

    Planned  ·  7 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. Currently you can set a condition to a step so that it is only run on tenants with certain tenant tags.

    If I know want to run one step on tenants with a tag but not run a second step with a the same tenant tag (different configuration for these tenants) I have to use conditions field instead. This gives a very unclear overview of the process as it appears to that both step run on tenants with the tag.

    Ideal would be
    * Step A run on tenants with Tag A.
    * Step B run on all tenants except…

    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

    1 comment  ·  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)
  12. On the face of it, a simple request... add am optional commit comment when saving an edited project. When going through the audit looking at project changes, it would be nice to simply read a project change commit message, when deciphering bit of JSON. It would be optional, so the JSON change is still available.

    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  ·  Installation  ·  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 deploying application containers, there can be times when you want a password that no human needs to know and survives only for the lifetime of the container.

    Our primary use case is generating secure keystores for certificates, etc. At container start-up, it will generate a new local keystore and we then have the ability to dynamically sign CSRs generated within the container via an external signing service.

    We do not want to leave the keystore nor the certificate objects without any password, but also do not want to store the values anywhere external to the container.

    Granted, we certainly…

    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)
  14. It would be nice to support Azure DevOps Artifacts Universal Packages feeds. We are slowly moving to Azure DevOps Artifacts (for artifact management only), and would like to use Universal Packages.

    https://docs.microsoft.com/en-us/azure/devops/artifacts/quickstarts/universal-packages?view=azure-devops&tabs=azuredevops

    14 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)
  15. Can we please have support for the DNS-01 challenge type for LetsEncrypt. We don’t want to have to expose a server to the open internet just to validate a certificate domain. DNS-01 solves this by querying the DNS provider directly for the challeng token to ensure you own the domain in question.

    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  ·  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)
  16. Add a PROCESS SNAPSHOT option for releases with an UPDATE PROCESSES button. This is the same thing that Octopus already has for variables. Just do it for Processes!

    Nothing worse than having to make a small powershell script change then create a new release and run it back up the runway or having to temporarily manipulate the lifecycle to get it re-deployed to where you want it to go with the updated process.

    I want to be able to go to the release. Hit update processes for that release to what I just changed on any process then be able…

    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. Given the Octopus Projects are not source controlled, comparing projects is quite difficult, so I resort to Export process and export variables to json and then do a file compare.

    This is made difficult when comparing variables, as the json file is in no particular order. It seems the most recently edited variable is at the bottom.

    Can we please arrange the variable in a set order, perhaps the same as the UI.

    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  ·  Installation  ·  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. Currently, Variable Conditionals as documented here:
    https://octopus.com/docs/deployment-process/variables/variable-substitutions#VariableSubstitutionSyntax-Conditionalsconditionals

    Does not allow for evaluation of more than one condition, which makes the syntax really ugly and dificult to read when workaround/hacks are implemented to evaluate more than one condition...

    For example, currently only this is allowed:

    {if Octopus.Deployment.Tenant.Name == "PreProd"}prod#{else}uat#{/if}

    Make is easy to do OR/AND and evaluate more than one condition, like this for example:

    {if Octopus.Deployment.Tenant.Name == "PreProd" || Octopus.Deployment.Tenant.Name == "Production"}prod#{else}uat#{/if}

    To get an idea of the issues review this post (describes workaround for AND but OR is not possible so far!):

    https://help.octopus.com/t/run-condition-variables-two-conditions/1585

    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

    1 comment  ·  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)
  19. "Use the version number from an included package" isn't as useful as it could be because whenever I modify a deployment process and go to create a new release, Octopus complains the release version already exists. So I either have to delete the old release or append ".i" to the version number. I would estimate I've appended ".i" about ten thousand times over the years. Would be nice to not have to do this.

    Basically this:
    https://help.octopus.com/t/how-to-create-a-release-version-with-package-number-and-an-incremental-number-with-it/23869

    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)
  20. The Dashboard somehow manages to show only 8 of my projects on a full-screen 1920x1080 browser. There is really no reason it shouldn't be able to show more than twice as many. There is just so much whitespace. This app should be about utility, and scrolling/searching really reduces the utility here.

    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  ·  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)
1 2 8 10 12 71 72
  • Don't see your idea?