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. Update documentation for "Updating Linux" runbook example to include additional successful exit codes

    A code sample at the following URL is incorrect:

    https://octopus.com/docs/runbooks/runbook-examples/routine/updating-linux#:~:text=To%20create%20a%20runbook%20to,and%20then%20click%20ADD%20STEP.

    The script under step 7 of "Create the Runbook" section (CentOS/RHEL) should be updated to reflect the existence of additional yum exit codes which indicate successful execution. Currently, this script does not account for exit code 100. From 'man yum':

    "DNF exit code will be 100 when there are updates available and a list of the updates will be printed, 0 if not and 1 if an error occurs."

    This can be corrected by introducing a compound conditional as follows:

    if [[ $? -ne 0 && $? -ne 100…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 →
  4. 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”.

  5. Support older versions of SQL Server

    Please reintroduce support for SQL Server 2016 Enterprise.

    Recent versions of Octopus only support SQL Server 2017+. SQL Server 2016 (SP2) still has mainstream Microsoft support until July 2021 and extended support until July 2026. It is very expensive for organisations to run and support multiple editions of Highly Available Enterprise SQL clusters and is consequently a barrier for upgrading to the latest Octopus version for my organisation. My organisation is a large enterprise in a heavily regulated industry so our software must be supported platforms, I am sure many of your enterprise customers would benefit from this.

    9 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  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    We have relaxed the restrictions on SQL Server from SQL Server 2017+ to SQL Server 2016+ in the latest patch release of Octopus Server 2020.2 and 2020.3.

    This has taken affect from the following versions
    2020.1.x (SQL Version change was not enforced in 2020.1.x)
    2020.2.18 ➜ 2020.2.latest
    2020.3.6 ➜ 2020.3.latest
    2020.4.0 ➜ latest

  6. 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 →
  7. Support Terraform 0.12

    Octopus supports Terraform-Steps. It uses Terraform 0.11. Terraform 0.12 has been released and has a few breaking changes. Update the Terraform-Integration to be compatible with Terraform 0.11 and 0.12.

    48 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  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support linux-arm in Linux Tentacle

    A dotnet core version has been build. I would be great if this was compiled to a linux-arm runtime.

    https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle

    15 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  ·  Flag idea as inappropriate…  ·  Admin →
  9. Disable Chrome AutoFill on inputs

    The chrome autofill gets in the way of dropdowns/multi-selects. There is not the ability for a user to disable autofill for specific websites, but this is supposed to work on the developer side:

    https://stackoverflow.com/questions/40200130/how-to-disable-chrome-to-autofill-username-email-password/40200269#40200269

    47 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  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow .war files to be deployed to Azure Web Apps

    Currently .war files are not supported by the Azure Web App deployment, it would be ideal that we can deploy this type of file directly to Azure Web Apps without having to take additional steps.

    6 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  ·  Flag idea as inappropriate…  ·  Admin →
  11. Helm 3 support

    Helm 3 is around the corner. Right now rc2 is available. Would be nice to Octopus could integrate with 3rd version of helm. Eg. Repositories will be available as container registries also. Are you guys plan to integrate with third version ?

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

  13. Fix a typo in the docs

    The header here
    https://octopus.com/docs/administration/data/octopus-database#Octopusdatabase-highavailability
    is missing an "i" between "bil" and "ty". Says Availabilty and not Availability

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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.

    28 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  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 →
  16. Allow multiple version of 'kubectl'

    Currently Ocotpus only allows for one version of 'kubectl' to be added to the Octopus server. This means that all clusters targeted by Octopus must be running the same version of Kubernetes.

    It would add greater flexibility if we could add multiple versions of 'kubectl' and then choose which version to use within the Kubernetes deployment target.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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 →
  18. 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 →
  19. Dark theme

    It would be great to have the option to switch to a dark theme

    166 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 →
← Previous 1 3 4 5 16 17
  • Don't see your idea?

Feedback and Knowledge Base