1458 results found

1. Disable deploy button when the 1st environment is Automatic Release

   When you manually create a release, and the 1st environment is automatically released, the Deploy button should be disabled so you don't accidentally re-release.

   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  ·  Edit…  ·  Delete…  ·  Admin →

2. Add "Substitute Variables in Templates" feature to "Upgrade Helm Chart" step

   Using values file to handle simple variable replacement is cool. It's painful to do that for multiline texts defined as Octopus Variable. It's very hard to get the indentation right. A somehow easier way will be using ".Files.Get" and then pipe to "nindent". This means we have a text file in which the variables are to be substituted during the same step like "Upgrade Helm Chart" and that file is not a helm values file at all.

   "Upgrade Helm Chart" already has a feature "Custom Deployment Scripts", which can be used to do this. But a much more easier way will be to add another optional feature "Substitute Variables in Templates" (as available to "Deploy a Package" step) to the step. This will make the deployment much cleaner.

   What is the downside of adding an optional feature "Substitute Variables in Templates" to all the steps in general?

   Using values file to handle simple variable replacement is cool. It's painful to do that for multiline texts defined as Octopus Variable. It's very hard to get the indentation right. A somehow easier way will be using ".Files.Get" and then pipe to "nindent". This means we have a text file in which the variables are to be substituted during the same step like "Upgrade Helm Chart" and that file is not a helm values file at all.

   "Upgrade Helm Chart" already has a feature "Custom Deployment Scripts", which can be used to do this. But a much more easier way… more

   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 →

3. Have Octopus listen to AWS S3 Endpoints

   While running Octopus on AWS it should listen to AWS VPC Endpoints and not go out over the interent to pull from S3 especially trying to go across regions which is a security concern

   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  ·  Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →

4. Have Octopus listen to AWS S3 Endpoints

   While running Octopus on AWS it should listen to AWS VPC Endpoints and not go out over the interent to pull from S3 especially trying to go across regions which is a security concern

   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  ·  Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →

5. Peer Review / Approval for release

   Our organization is split into development teams, which "owns" their project groups.

   The developers can release all they want up to our staging environment, however to promote the release from Staging to Production we have a manual intervention step, that needs to be approved before a release can be promoted.

   This works fine, and the team responsible can approve the manual intervention step and promote the release.
   However.. this is kinda bad practice that in theory a given developer can code, build and release their changes all the way up to Production.

   Can you add a feature so the approver can't be the same user which created the release? This would fit nicely as a peer review.

   A specific approver team would not fit the bill here, as the developers might in turn approve eachothers release and sign off on the QA.

   Our organization is split into development teams, which "owns" their project groups.

   The developers can release all they want up to our staging environment, however to promote the release from Staging to Production we have a manual intervention step, that needs to be approved before a release can be promoted.

   This works fine, and the team responsible can approve the manual intervention step and promote the release.
   However.. this is kinda bad practice that in theory a given developer can code, build and release their changes all the way up to Production.

   Can you add a feature so the approver… more

   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  ·  Releases  ·  Delete…  ·  Admin →

6. Support Jump Hosts for Indirect Connections to Targets

   Similar to the way TCP proxies can be configured, allow Jump Hosts to be configured for connections to targets that the Octopus Server cannot directly connect to and run commands on.

   This will be useful in segregated network environments where connections across different network zones must be made via designated servers.

   For Linux, this could perhaps be achieved using the ssh -J parameter and on Windows via nested use of PowerShell remoting.

   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  ·  Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →

7. syslog

   We need to forward Octopus Deploy Audit Logs to a Syslog Server. It will be grate if there will be an option to configure log forwarding to a syslog server in Octopus Deploy administration page.

   We need this feature because we are a payment facilititator and we need to store all of our logs in a centralized log server like syslog servers. This feature will help us to comply with PCI-DSS standards and our local legal authorities.

   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  ·  Infrastructure  ·  Edit…  ·  Delete…  ·  Admin →

8. Warning state

   We'd like to implement Canary Deploy in some of our projects.

   We have seen and tried different methods but for our needs the best solution would be this one:
   go, during deployment, to select the canary target and start the deployment only on that target(s).

   It works fine, however the problem is that at the end of the process we see the outcome in green and this is very misleading because in reality the deployment was successful but only on the selected target(s).

   We tried to manually edit the status but it seems it is only possible to put in the status Cancelled, Failed, Success.
   It is a pity because that small detail makes this method unusable.
   Please consider including an intermediate state (yellow, orange or any other color) in editing the status, I think it would be useful for many other purpose too.

   We'd like to implement Canary Deploy in some of our projects.

   We have seen and tried different methods but for our needs the best solution would be this one:
   go, during deployment, to select the canary target and start the deployment only on that target(s).

   It works fine, however the problem is that at the end of the process we see the outcome in green and this is very misleading because in reality the deployment was successful but only on the selected target(s).

   We tried to manually edit the status but it seems it is only possible to put in… 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  ·  Edit…  ·  Delete…  ·  Admin →

9. Ability to call a script rather than code it inline

   Hi,

   I have been looking at getting out deployment process under version control for our main project.

   I have successfully integrated Octopus with Azure Devops Repo and created a test project under version control etc.

   From what I can see, the entire deployment process is written to a /.octopus/deployment_process.ocl file, including any inline PowerShell scripts.

   For example:

   step "Swap Staging and Production Slots" {

   action {
       action_type = "Octopus.AzurePowerShell"
       properties = {
           Octopus.Action.Azure.AccountId = "#{AzureAccount}"
           Octopus.Action.Script.ScriptBody = <<-EOT
          ….
           ….
           …. 
           Lots of powershell coding
           ….
           ….
           ….
           EOT
           Octopus.Action.Script.ScriptSource = "Inline"
           Octopus.Action.Script.Syntax = "PowerShell"
           OctopusUseBundledTooling = "False"
       }
       worker_pool = "Azure Worker Pool"
   }
   

   }

   What I was hoping to do was modularise it even further so that instead of all the code being inside the .ocl file, have that step above in a separate script inside the repository.
   So instead of having an inline script, we call a script stored separately in the repository? Is this functionality possibly currently or is this a feature that is planned for the future?

   Hi,

   I have been looking at getting out deployment process under version control for our main project.

   I have successfully integrated Octopus with Azure Devops Repo and created a test project under version control etc.

   From what I can see, the entire deployment process is written to a /.octopus/deployment_process.ocl file, including any inline PowerShell scripts.

   For example:

   step "Swap Staging and Production Slots" {

   action {
       action_type = "Octopus.AzurePowerShell"
       properties = {
           Octopus.Action.Azure.AccountId = "#{AzureAccount}"
           Octopus.Action.Script.ScriptBody = <<-EOT
          ….
           ….
           …. 
           Lots of powershell coding
           ….
           ….
           ….
           EOT
           Octopus.Action.Script.ScriptSource = "Inline"
           Octopus.Action.Script.Syntax = "PowerShell"
           OctopusUseBundledTooling = "False"
       }
       worker_pool

   … 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  ·  Edit…  ·  Delete…  ·  Admin →

10. Add AuthorEmail to Octopus.Release.Package.Commits and Octopus.Deployment.Changes.Commits

    A concept of a commit generally includes author information, however this information does not seem to be currently available in Octopus.

    Having commit author in Octopus would be useful for notifications during deployment process, and for attribution in release notes.

    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  ·  Edit…  ·  Delete…  ·  Admin →

11. Add 2FA/MFA login support

    Add support to enable multi factor support to users.
    Now more than ever we need to protect our Octopus Deploy instances as it is more and more becoming the keys to the kingdom.
    Support for Authy/Google auth plus DuoSecurity would be a good start

    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  ·  Administration  ·  Delete…  ·  Admin →

12. Play a configurable audible bell at the end of a deployment

    When the user has an ongoing deployment visible in his/her browser, it would be great if we could add the possibility to play a customisable sound at the end of the deployment: deployments can take a very long time to finish and who runs the deployment interactively is definitely interested in being notified right after the deployment completes for various reasons. Please add this functionality to the product.

    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  ·  Edit…  ·  Delete…  ·  Admin →

13. Improve variable management

    Today, there are several levels to manage variables in Octopus, and it's a good thing:
    - Library variable sets
    - Project variables
    - Tenant variables (thanks to variable templates)

    I think you should really simplify this process to manage all of them from Library variable sets only. Indeed, when you create a variable from this section, you can link it to some environments, some targets, and some target roles. If you add the possibility to link it to tenants and projects, it's win :)

    Doing that would also allowing to set tenant/project variables only to some environments, that is not possible today.

    Today, there are several levels to manage variables in Octopus, and it's a good thing:
    - Library variable sets
    - Project variables
    - Tenant variables (thanks to variable templates)

    I think you should really simplify this process to manage all of them from Library variable sets only. Indeed, when you create a variable from this section, you can link it to some environments, some targets, and some target roles. If you add the possibility to link it to tenants and projects, it's win :)

    Doing that would also allowing to set tenant/project variables only to some environments, that is not… 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  ·  Administration  ·  Edit…  ·  Delete…  ·  Admin →

14. Add context menu to deploy button on Overview page

    On the release Overview page, it would be nice if the DEPLOY... button was enhanced with a context menu that as an option that behaves as it does now (navigates to release page).
    Having the "DEPLOY [↓]" deploy instantly without navigating would save some clicks when there are many channels.
    Perhaps there already exists a feature to deploy all channels to "next stage".

    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  ·  Edit…  ·  Delete…  ·  Admin →

15. Permissions on Tenant Tag level

    Currently it’s possible to limit rights of a Team to specific tenants but not to a tenant tag. With ~20 tenants and more it's really hard to maintain this. Also the list would become so long. It would really help to specify just the tenant tag.

    In our case we have only one risky tenant which should be assigned to a small Team. But we have to add all 19 less risky tenants to the bigger Team.

    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  ·  Tenants  ·  Delete…  ·  Admin →

16. Fix strange behaviour with skipping tenants in runbook that have latest snapshot

    When running a Runbook and only one tenant is available the tenant is automatically selected and a checkbox is shown saying "Skip tenants where Snapshot Y7484HM is the current version deployed to ExampleEnvironment". It's checked by default.

    However when deselecting the tenant and selecting it again this checkbox doesn't appear. It seems like it's connected to the automatic selection of the tenant which is strange.

    Additionally it would make sense to have this checkbox disabled by default (or configurable) because Runbooks are for routine tasks (as the website says) where we WANT to run the Runbook multiple times (although there are no changes in the Runbook). Right now our people use the Runbook multiple times per day and need to disable this checkbox every time.

    When running a Runbook and only one tenant is available the tenant is automatically selected and a checkbox is shown saying "Skip tenants where Snapshot Y7484HM is the current version deployed to ExampleEnvironment". It's checked by default.

    However when deselecting the tenant and selecting it again this checkbox doesn't appear. It seems like it's connected to the automatic selection of the tenant which is strange.

    Additionally it would make sense to have this checkbox disabled by default (or configurable) because Runbooks are for routine tasks (as the website says) where we WANT to run the Runbook multiple times (although there… more

    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  ·  Runbooks  ·  Delete…  ·  Admin →

17. Fill Promted variables from outer source

    Prompted variables are defined manually, the idea is to add the option of filling the values with information of an external source.
    For example, fill a Drop Down prompted variable with the values from a column of a MSSQL table.

    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  ·  Edit…  ·  Delete…  ·  Admin →

18. ability to add metadata to a tenant environment that shows up on overview screen

    So in our scenario we have multiple tenants and each one has 6 or more environments which are attached to the tenant. In the overview screen we see the list of tenants on the right hand column and the environments as the column header and their current version along the row. What we really need so that we don't get confused to which site we are deploying is some additional metadata on the overview screen so we can at a glance see something like what ownership of that deployment or what that deployment is for.
    
    So to explain I have tenant1, environment1, it displays V1.2.3 (timestamp) in the overview. I need somewhere there to possibly add a "?" so you could hover over and it gives you details about that specific deployment. So i could know that tenant1, environment1 is for custom deployment for customer X, managed by employee John, etc.

    So in our scenario we have multiple tenants and each one has 6 or more environments which are attached to the tenant. In the overview screen we see the list of tenants on the right hand column and the environments as the column header and their current version along the row. What we really need so that we don't get confused to which site we are deploying is some additional metadata on the overview screen so we can at a glance see something like what ownership of that deployment or what that deployment is for.
    
    So to explain I have… 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  ·  Projects  ·  Edit…  ·  Delete…  ·  Admin →

19. rollback

    I need to add automatic rollback process in my deployment pipeline.
    For example - If X release version deployment failed, then it will rollback to previous last successful release version Y in the same environment.
    Trigger must be automatically happen.

    Please guide if someone has any better solution here.

    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  ·  Edit…  ·  Delete…  ·  Admin →

20. Variable Set support for Tenants

    Variable sets should have Tenant support. Such variables to have a Tenant scope.

    This would allow common vars to be reused via variable sets. This should be a common requirement for multi-tenanted microservice setups. Without that you either have to have variable copied or have them all defined at the Tenant level. Both bad options.

    A work around is to have variables as #{if TenantName =="A"}TenantAValue{#/if}#{if TenantName =="B"}TenantBValue{#/if}
    this is pretty ugly and it doesnt work for snesative variables as far as I know.

    I know this tricky to implement but really important IMHO

    4 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  ·  Tenants  ·  Delete…  ·  Admin →