General

  1. Support loading CloudFormation templates from an S3 Bucket

    Due to the API limits limiting in-call CloudFormation template length to 51200 bytes, consider enabling the option to load a CF template from an S3 bucket. This functionality already exists in the CLI, and can be done via a script step, but having it be baked in would be an enhancement.

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Use AWS IAM Roles as Octopus AWS Accounts

    When creating an Octopus AWS Account (https://octopus.com/docs/infrastructure/deployment-targets/aws) you currently need to enter an AWS Access Key and Secret Key. This means the corresponding AWS Access Key needs to be periodically rotated, creating some management overhead and potential security vulnerabilities. Rather than an AWS Access Key and Secret Key, if we were able to enter an AWS IAM Role that is assumed whenever that Octopus AWS Account is used, then we would no longer need to manage AWS Access Keys.

    In the background, Octopus Deploy would need to set it up so that the AWS IAM Role is assumed…

    67 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  3. Kubernetes Cluster Worker Pools

    I am on a cloud account using shared worker pools. This is great, but using shared pools means Octopus Infrastructure is running my deployments and I need to wait for a worker to free up.
    Also shared workers do not have a fixed IP so I cannot limit the IP addresses that can communicate with my Kubernetes Master, an attack vector I would like to close.

    It would be great if when setting up a Kubernetes cluster, my Octopus cloud account asks if it can run workers inside my cluster.

    An issue with this is that the worker will run…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    With the Tentacle container image available from index.docker.io/octopusdeploy/tentacle it is possible to run workers inside a Kubernetes cluster. The workers can be polling tentacles, and so do not need static IPs.

    The free ebook “The ten pillars of pragmatic Kubernetes deployments” available at https://github.com/OctopusDeploy/TenPillarsK8s/releases/latest/download/tenpillarsk8s.pdf describes how to create workers in a Kubernetes cluster in Chapter 3 “Verifiable deployments”.

  4. Runbook need support for prompted variables

    Runbook need support for prompted variables

    We need support for prompted variables when using runbooks hope this is added in a future version

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Additional features for AWS templates

    Currently there are several AWS deployment templates like one for uploading file to S3 bucket and few for deploying CloudFormation stacks.
    The problem with them is that they have a short support of different features we have for traditional IIS or Azure templates. So the suggestion is to add some of these features to AWS templates too e.g

    • JSON Configuration Variables,
    • Custom Deployment Scripts,
    • Configuration Variables,
    • Configuration Transforms
    75 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    Octopus 2021.2 enables structured configuration variables in the CloudFormation step. This is the next version of JSON Configuration variables, and allows variables to be injected into YAML and JSON files. See https://octopus.com/docs/projects/steps/configuration-features/structured-configuration-variables-feature for more details on this feature.

    Older features like configuration transforms and configuration variables won’t be enabled in CloudFormation steps, as these are XML and .NET specific, and so don’t provide much value for YAML or JSON templates.

    Custom deployments scripts are being implemented today by adding “Run a script” steps before and after a given step, and so this is also not something that will be added to the CloudFormation step.

  6. Kubernetes Ingress doesn't allow to configure TLS

    Allow kubernetes ingress to specify TLS configuration.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. 13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add variables substitution capabilities

    We keep our deployment configurations in octopus variables and use json substitution the replace them on deploy time

    This could be improved in a few ways:

    • Use the json variables substitution feature on other step templates than deploy a package (for example: run a script)
    • have to ability to substitute also yml files
    • give a variable a null value, the only option now is tho give him empty string, which influence the code.
    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. terraform

    Terraform step templates for Azure deploys. Currently only AWS is supported in Octopus included step templates. It seems like an easy addition to the existing functionality

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow cloning of tenants

    It should be possible to clone a tenant including it's current configuration in a similar way to that you can clone whole projects.
    Tenants tend to be similarly configured with only minor changes to each one so it would save time rather than having to configure each one from scratch.

    144 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow project dependencies - so deploying one project would automatically deploy all dependent projects

    We have many dependencies between our projects. So for example we have cross database dependencies which mean that a particular version of the database must be installed prior to another version. Similarly we have base services that are required by all others that must be installed first. There is currently no way of telling Octopus that one project depends upon another.

    We could create one great big Octopus deployment with all the steps in it to deploy the TFS projects/libraries in the correct order. But this would be very complicated because of the large number of dependencies.

    It would be…

    317 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. C# Script in script modules

    We need to use C# code as script in the script modules

    229 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add notes or description to deployment process step

    When working with the deployment process I sometimes find that I have to do something in a step that might not be standard, for example setting a temporary user on the "create app pool" step. It would then be great to be able to ad a note to the step describing what is done and why.

    43 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Find variable usage across all projects and variable sets

    When working with library variable sets used in many projects with many steps it is cumbersome to figure out where a given variable is used.

    When updating a deployment process, certain tasks become very difficult, such as:
    -Renaming or deleting a variable
    -Checking validity of a newly-updated variable value across all usages

    With a "find all" feature these tasks would be much simpler (plus I'm sure there would be wider-reaching benefits).

    343 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    Happy to announce we’ve added a usage tab to the variable set page in 2019.5.4, where you can view which projects and releases are using a variable set. While this does not cover all suggestions below, we are confident that this goes a long way to solving the problem.

    Finding the usages of individual variables is something that is a lot more complex than it sounds, and we are unlikely to implement. Many variables usages are embedded in strings, or even in files sourced from packages, meaning any results we displayed would be incomplete.

    If you think we’ve misinterpreted this suggestion, please raise a new suggestion with a bit more detail about the use case, and let us know in the comments below.

  15. Major and Minor version numbers as individual variables available for use

    We deploy to a sub app on the site for our Web services with the major/minor version number in the URL to allow for easy side by side deployments. We don't deploy every version to a new URL because of the volume of builds we get for dev/testing etc. and we like to give a friend URL out to 3rd parties that use them.

    e.g. https://MyWebService.com/v1.2/MyService.svc

    currently we have custom powershell to update the IIS location in predeploy, we hard set it to something like "MyIIS.Site/v1.2", would be good if we could get the specific number using variables and use…

    32 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add support for Python scripting.

    It would be great to see Python listed as a script step. Python is heavily utilized in the infrastructure space, AWS, F5, Citrix, VMware and will help to drive full automation further up the stack.

    119 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  17. Lock "production" releases from retention policy

    Via @DotNetWise (https://github.com/OctopusDeploy/Issues/issues/1157)

    Retention policy helps you to cleanup the mess, but it could possible destroy your live releases.

    You DO want to apply retention policy on live servers, but not for those releases you know there are being used / live etc.

    Hence, add the ability to lock a release, so it won't be deleted by the retention policies.
    Later on, I could unlock it and it will go away on when the next retention policy is being applied.

    29 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow me to choose which environments a project uses / per project environments

    We have multiple projects being deployed to different servers in heterogeneous environments. Some are just test-production, others are dev-test-staging-production. The projects often have completely separate environments.

    It would be beneficial to be able to either choose which environments a project can deploy to, or to be able to set up per-project environments to be able to keep the same names for config transforms. (ex. "Web.Test.cfg" instead of "Web.Test-Product1.cfg")

    Currently the Dashboard is also very "cluttered" with empty boxes due to those environments not being in use for certain projects.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add "Substitute variables in files" feature in "Run a Helm update" step

    In "Run a Helm update" step we need: Enabled Features -> Substitute variables in files

    Why?
    For example we need to create configMap for our helm-chart. App config locate in this chart, so we need replase all #{values} by values from project scope

    Step helm_install:
    1. download chart
    2. Substitute variables in files (choose location)
    3. in custom script (deployment step) create configMap for our pods

    If this feature doesn't exist: we need another step where we download app config and substitute variables and use this file to create configMap

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. promote a whole environment

    We have "major deployments". At this time we have to deploy all our applications (~ 70) at once. So it would be nice to have a possibility to deploy all projects from environment-1 to environment-2

    30 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base