General

I suggest you...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Allow Variables to be Version Controlled

    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…

    49 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    • 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

      30 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
      • Ability to diff variables against previous release when deploying to an environment

        Scenario: I am about to promote my new release to production. My release is clean (i.e. I'm not getting the "something has changed warning"). However, a week ago, someone made an errant change to the production transform for a shared library set variable. If I deploy, it will break due to that variable change that I don't know about. I don't have a good way to detect this before I hit deploy.

        Request: On the deployment screen for a release, provide the ability to diff that release's variable snapshot against the variable snapshot from a previous release that was deployed…

        31 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
        • 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
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
          • Rolling deployment parallelism per role

            We have an service environment right now that consists of two data centers that each contains 3 servers that host the services. These services hosts host 100+ services each and each server is hosting exactly one instance of each service; so they are in effect mirrored.

            When we deploy to these servers, we do it one data center at a time. Since there are so many services per server, we can’t just remove the server from the load balancer. Also since we do round robin load balancing and want to have zero downtime and keep consistency in our responses during…

            3 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
            • Display channel description when creating a new release

              The selected channel's description should be displayed when creating a new release, otherwise a user may miss important information that is not fully conveyed by the channel's name. Currently a user would have to navigate to the separate channels tab to see this, which breaks the UI flow and which they may not necessarily do.

              5 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
              • Terraform support for SSH Workers

                Currently the built in terraform steps only support Windows workers. It would be good if the steps were platform agnostic and able to run on any worker.

                6 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                • Kubernetes Ingress doesn't allow to configure TLS

                  Allow kubernetes ingress to specify TLS configuration.

                  4 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                  • Consistently sort the environments on the tenant variables page

                    Click on Tenants at the top, click on a tenant, then click on variables on the left, then expand a Project. You will see the environments enumerated. I suggest that you sort these environments.

                    This is currently sorted arbitrarily, and similar tenants can have a differing order of environments on this page, which has led to mistakes on our end. Lifecycle order would probably be best, but Alphabetic order would also be better than the current sort.

                    7 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                    • Schedule Trigger of Latest Release without Promotion

                      We wish to schedule deployment of the latest existing release to a given environment.

                      Current functionality allows:
                      1. Create and deploy a new release, or
                      2. Deploy latest release (by promoting latest deployed release from one environment to another), or
                      3. Re-deploy latest release on a given environment.

                      None of these suit our needs.

                      Our desired functionality is:
                      1. Pick the latest existing release for the nominated channel;
                      2. Deploy the release, with all steps enabled, to the nominated environment/s.
                      3. If the release version has already been deployed, deploy it again, with all steps enabled.

                      3 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                      • option to Download / copy certificate files through Build Step

                        We are able to manually download the certificates from octopus certificate store, it will be helpful to do the same in build step as sometimes we need to copy certificate files to the application servers.

                        1 vote
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                        • Move "Excluded Steps" above tenant selection.

                          It's a hassle to scroll to exclude steps during a deployment particularly when your debugging a deployment and don't want to/can't disable steps.

                          3 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                          • 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

                            9 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                            • Scoped Tenant Variable

                              Here's the scenario:

                              I have a web application that is being used across 12 countries.

                              Every country has its own environment, databases.

                              While the current Octopus allow us to create tenant variable like Alias, it is useful but when it comes to scope variable this feature is not there.

                              Example: Tenant A has a different Database credential for UAT and PROD. Currently the workaround is to create 2 tenant variable, like UAT Database, PROD Database.

                              It would be useful to have this scoped as well.

                              6 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                              • Create step to delete a Helm release

                                Pretty straight-forward. 2018.8 introduced a step (in alpha) to deploy Helm releases. A step to delete the Helm release would be helpful for garbage collection when it's no longer needed.

                                6 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                • Add StorageAccount to Azure Targets

                                  Add StorageAccount to Azure Targets. Azure storage accounts now support creating static website in a blob in a storage account, so it would be much appreciated if it would be possible to deploy to a StorageAccount on Azure as part of the Azure Targets. Please use SAS key instead of requiring the installation of ServicePrincipal

                                  9 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Allow Terraform step script packages to have deploy.ps1 scripts

                                    Script packages used in a terraform step should be able to execute deploy.ps1 files, like all other script packages. This would support use cases such as needing to perform a custom terraform command, or do some dynamic editing of .tf files (say download some from a common http location), or special config for your backend (as this is a bit painful in regular terraform).

                                    2 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Support multi-package deploy steps

                                      Allow package deploy steps to select multiple packages that are deployed in the selected order (with the ability to change the order). We have a website where we deploy a clean copy of a vendors files (makes upgrades easier), then we overlay different 3rd party modules and our solution into the same folder. These packages together create a whole website.

                                      32 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Hide project template variables on conditions

                                        Be able to hide "sections" of variables in a project template on a tenant and envrionment. For example: I have single-sign-on configuration in web.config. If the checkbox "Enable Single-Sign-On configuration" is checked is not checked I would like to remove the configuration variables bellow the checkbox.

                                        Having tons of these sections really clutters the overview and making it hard to configure.

                                        Also being able to group variables into +/- sections with a header would be really great.

                                        I would like to extend this even further on a tenant level using tenant variables to enabling features such as the "Enable feature…

                                        3 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Highlight the variable Snapshot difference while updating the release snapshot

                                          Whenever there is a change in the variable after the creation of the release, we used to get warning saying "Release Snapshot has been changed". But we do have only one option to update the entire release without knowing what has been changed. It would be great if you have any way to find/highlight the variables and their values that will be updated when I click "Update Variables" in the release Snapshot section. It will minimize the risk when it's comes to updating the snapshots for production deployment and it will give a transparent view of what changes are done…

                                          66 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1 3 4 5 21 22
                                          • Don't see your idea?

                                          Feedback and Knowledge Base