General

  1. chained deployment to specific targets

    If you deploy to specific targets in an environment but one the steps triggers a chained deployment, the chained deployment will target all hosts in the environment. It would be better if the chained deployment continued to target only the specific hosts that were originally chosen.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Create/write a file to a location

    Sometimes we just want to write out a simple file to disk. For example writing out a basic text file to a location. While you could have a basic template in an repo sometimes you want to write out a straight file to disk with the normal support for variable substitution. Example, write a file to a queue or change a basic configuration file.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. have a better way of handling parameters in arm templates

    When setting up a new ARM template for use in octopus we set the default value of all parameters to #{something} so that the 'parameter' page in octopus is auto populated.This works great for most values but if we have a secure string octopus will update the 'default value' in the arm which will show up in the deploy history in Azure. We would like to see some way to handle this so we can ignore updating the default value or auto-populate the parameters page without needing the default value or some other way to handle this a bit cleaner.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support Azure Service Fabric Mesh

    The Service Fabric Mesh deployment model is in public preview since a couple of months back and GA is expected this spring. Being mainly ARM template and container based, the SF Mesh deployment is probably possible to accompish by custom scripts today, but good out of the box support in OD would be very valuable.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Json Configuration - Scope Target File

    Been setting up multiple pipelines for Azure Data Factory (ADF) resources, defined by a series of Json files and would like to to use the Json Configuration Variables for configuring these. In ADF you typically have a series of linked services json files, specifying e.g. connection strings, credentials, input type etc - all with the same hierarchy - E.g. the connection string would be specified as 'properties:typeProperties:connectionString' in all the linked service files - hence the problem, since all json files are applied with the same OD variables.

    I proprose an extension to the existing Json Configuration Variables feature, where…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Integrate Octopus deploy project variables with Azure Key Vault

    So sensitive project variables will be referenced from Azure Key Vault instead of being stored in octopus.

    https://azure.microsoft.com/en-us/services/key-vault

    3357461 - 'Azure Resource Manager Key Vault support' was only about ARM template Key Vault support.
    17973586 - 'Integrate Octopus deploy with secrets managment system Vault' is similar to this issue only for https://www.vaultproject.io

    This idea is similar to
    https://docs.microsoft.com/en-us/vsts/build-release/concepts/library/variable-groups?view=vsts#link-secrets-from-an-azure-key-vault-as-variables

    115 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. Set Rolling Deployment Window Size with a variable

    Should we implement the ability to configure a Rolling Deployment's Window Size via variable? Adding this feature would allow the window size to be controlled dynamically after release creation.

    Feel free to add any comments or thoughts below.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. Azure Extension "Learn more about Octopus Deploy" link broken

    When installing the OctopusDeploy Tentacle Agent Extension in Azure the "Learn more about Octopus Deploy" leads to https://octopus.com/tour?utmsource=azure-portal&utmmedium=in-product&utmcontent=about&utmcampaign=OD
    The only thing at that address is a "Page not found.
    We can't seem to find the page you are looking for. The page may have been removed, or moved somewhere else" message.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow adding tags for AWS CloudFormation Stacks

    Currently if I were to deploy a CloudFormation template using the AWS CLI I would have the option to specify tags for the stack.

    The tags defined at the stack level propagate to all AWS resources in the stack that support tagging.

    Since our stacks generally correlate to an environment such as 'staging' or 'production' it would be useful to supply an Environment tag to the stack and have this applied to all resources.

    Octopus currently does not allow us to specify the tags for the stack in the 'Deploy an AWS CloudFormation template' step.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Give us control over log output wrapping of octo.exe

    We integrate Octopus into our Azure DevOps pipeline through octo.exe. The problem is that octo.exe wraps the output it receives from the server unconditionally to 80 characters. This does not make any sense.
    The net result - it is completely unreadable.
    Please, remove the wrapping or give us a flag to remove it.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  11. Provide an option for step-templates to not require new release

    It would be good for step-templates to have a boolean (tick/slider) option for step-templates to not require a new release for updated versions.

    This would allow basic step templates to be updated without having to create new releases for multiple projects.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow a Project to randomly choose / cycle through deployment hosts rather than deploy to all instances.

    Allow a Project to randomly choose / cycle through deployment hosts rather than deploy to all instances.

    This should be a configuration option for the default deployment setting and separate from the manual deploy to specific instances that currently exists.

    Potentially with the option to select the number of instances to choose to deploy to

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow specifying Tentacle name in Azure Resource Manager Template extension

    When using the Azure ARM template Octopus Tentacle extension, it would be nice to be able to override the tentacle name. It currently uses the computer name, which sometimes is not the best name for the tentacle

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Make target roles variable

    Let target roles be bindable like most other fields.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Supply a list of project variables for powershell

    Currently in powershell scripts, the only list of variables is $OctopusParameters, but this list includes all the built-in Octopus parameters as well.

    It would be really nice to be able to reference only the variables defined in the current project during a deployment.

    Something like $OctopusProjectVariables

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  17. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  18. octo.exe pack should support a --exclude= flag (at least when --format=zip)

    The nuspec approach may indeed support excluding files. However the zip approach (--format=zip) doesn't. Per octopus documentation the .zip approach is the recommended way forward. In this light a --exclude option is in order to compensate feature-wise vS the nupkg approach.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow variables to be used for Channel Version Rules

    It would be nice if the Channel Version Rules had support for Octopus variables. From a management standpoint, when you have dozens and dozens of deployment steps bound to specific Version Rules, it would make sense to be able to make centralized updates rather than going through all of the various projects, channels, and associated rules in order to make the same update.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base