346 results found

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.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →
   Released  ·  Matthew Casperson responded

   This is available in 2021.3: https://github.com/OctopusDeploy/Issues/issues/6993

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 ]]

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Released  ·  1 comment  ·  Installation  ·  Delete…  ·  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 and temporary credentials (https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html) are created whenever the corresponding Octopus AWS Account is used by a deploy process.

   As for the credentials that are used to assume the AWS IAM Role, I would expect that the AWS service role for EC2 instances running the Octopus Deploy server / workers is used by default to assume the AWS IAM Role. And if Octopus is not running on EC2 instances, maybe as part of the creation of the Octopus AWS Account, when specifying the AWS IAM Role to assume, you could specify another Octopus AWS Account to use to assume that role. That way you could maintain a single AWS IAM User and Access Key, and then that user would be used to assume the AWS IAM Roles.

   As an example, you could setup the Octopus Deploy server / workers EC2 role (or an IAM user) policy as follows:
   Name: octopus-deploy-server
   https://gist.github.com/burck1/5469acbff31b71fa69ef8d91c4426e50

   Then when creating the AWS IAM Role that will be assumed as part of the deployment you would:
   1. Setup the Trust Relationship as:
   Name: octopus-deploy-my-project-deployer
   https://gist.github.com/burck1/5469acbff31b71fa69ef8d91c4426e50
   2. Setup the AWS IAM Role policy to have access to whatever AWS resources needed.

   Note: This feature would also allow cross-account access as AWS IAM Roles can be assumed within other 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… more

   27 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Deployments  ·  Delete…  ·  Admin →
   Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

   EC2 instance roles and secondary IAM roles can be assumed in AWS steps and for EKS clusters (new in 2020.4). The blog post at https://octopus.com/blog/aws-iam-roles has more details.

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 on a node who's IP is generally ephemeral, so this will only really work if the cluster has a network configured with a static IP.

   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… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →
   Released  ·  Matthew Casperson responded

   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.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Installation  ·  Delete…  ·  Admin →
   Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

   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 Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Deployments  ·  Delete…  ·  Admin →
   Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

   This was implemented in Octopus 2019.11
   https://octopus.com/docs/runbooks/runbook-variables#prompted-variables

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.

   20 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Integration  ·  Delete…  ·  Admin →
   Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

   We are happy to inform you that this UserVoice suggestion has been addressed as part of https://github.com/OctopusDeploy/Issues/issues/6562, and will be released with Octopus 2020.5.0.

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

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Delete…  ·  Admin →
   Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

   Support for ARM tentacles has been included in 2020.2.

   See the blog post at https://octopus.com/blog/deploying-an-octopus-pi for an example of how these can be used with a Raspberry Pi.

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

   27 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   4 comments  ·  Delete…  ·  Admin →
   Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

   This should be resolved as of Octopus 2020.4
   https://github.com/OctopusDeploy/Issues/issues/6481

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.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Released  ·  Matthew Casperson responded

    This is now available with the
    “Deploy an Azure App Service” step.

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 Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integration  ·  Delete…  ·  Admin →
    Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

    https://github.com/OctopusDeploy/Issues/issues/6048

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
    27 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Delete…  ·  Admin →
    Released  ·  Matthew Casperson responded

    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 Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

    This has been resolved.

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.

    10 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Released  ·  Matthew Casperson responded

    Tags will be able to defined on the CloudFormation stack in Octopus 2021.2.

15. Kubernetes Ingress doesn't allow to configure TLS

    Allow kubernetes ingress to specify TLS configuration.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Delete…  ·  Admin →
    Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

    This was implemented in 2018.11.2
    https://github.com/OctopusDeploy/Issues/issues/4929

16. 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

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    5 comments  ·  Deployments  ·  Delete…  ·  Admin →
    Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

    This has been fixed as part of the issue documented at https://github.com/OctopusDeploy/Issues/issues/6476.

17. 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.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

    The ability to run a target in an environment with custom executables has been enabled with execution containers. The documentation at https://octopus.com/docs/deployment-process/execution-containers-for-workers has more information.

18. Support YAML parsing like you do JSON parsing in variable substitution extended syntax
    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Delete…  ·  Admin →
    Released  ·  AdminProduct Team (Admin, Octopus Deploy) responded

    This is now available. See the docs at https://octopus.com/docs/deployment-process/configuration-features/structured-configuration-variables-feature for more details.

19. 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.
    16 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Deployments  ·  Delete…  ·  Admin →
    Released  ·  Matthew Casperson responded

    The new “Structured configuration variables” feature extends the JSON substitution to YAML, XML, and Java properties files. It is also available on a “Run a script” step for use with additional package references.

    You can find more information on this feature at https://octopus.com/docs/projects/steps/configuration-features/structured-configuration-variables-feature.

20. Create an Octopus Terraform Provider

    Like many others, we use Terraform to manage our cloud infrastructure and it would be great if we could create and manage our octopus setup in it too.

    This is a follow up to the question posted on the Octopus Help section: https://help.octopus.com/t/any-plans-for-an-octopus-terraform-provider/20853

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integration  ·  Delete…  ·  Admin →
    Released  ·  Matthew Casperson responded

    A Terraform provider is available at https://registry.terraform.io/providers/OctopusDeployLabs/octopusdeploy/latest.