General

  1. Use IAM roles instead of AWS access secrets for all external resources, e.g. feeds, targets, community library tasks

    Currently, the only way to set up AWS authentication for an ECR external feed, AWS deployment target, community library task, etc, is with an IAM user secret such as API access keypair. Our product secrutiy team has exlicitly forbidden use of secrets such as keypairs like this and requires everything to use IAM role authentication via role assumption.

    It would be lovely to replace the access key and secret key inputs with a single input for an IAM role name to assume into in order to get the needed credentials. The authentication and login could then execute on workers with…

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Retention policies on offline targets (artifacts)

    Delete previous install files when new install (with an artifact) occurs (offline targets). These deletion should keep in mind the configured retention policy in the corresponding lifecycle

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support for High Priority Deployments/Tasks

    Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
    In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
    This is not possible now, the only solution now is to cancel all the existing tasks.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  6. Document Octopus Package metadata Json file format

    The octo.exe push-metadata allows to provide package build information, but its format is not documented.

    The documentation available at https://octopus.com/docs/octopus-rest-api/octo.exe-command-line/push-metadata states that the "metadata-file" parameter should be a "Octopus Package metadata Json file".

    What is the format expected for that "Octopus Package metadata Json file" ?

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Separate permissions in the User Role "Project Contributor"

    Currently, in order to allow developers to access and edit variables, they are also able to edit process steps including disabling them. This means that they are able to disable audit steps before deploying.

    If process edit was a separate permission we could split out the ability to edit variables and the ability to edit/change process steps

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…

    137 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Deployment features  ·  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

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support the creation of images as a task using packer

    Packer is a versatile tool, especially when working in a multi-cloud environment. It can be used for both creating both base gold images that can then be fully built on later or fully built imputable images.

    I see an octopus step being able to be used to:
    1) create or pull (from a repository) & update a json template with variables & transformation.
    2) next packer validate
    3) packer builds the image.

    ideally, there would also be an "Octopus" provisioner for packer that would allow the download of repos, call templates, transforms, variables install tenticle via cli

    but even it…

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  11. Option to hide Spaces in navigation

    Just upgraded to 2019.1 - the Spaces navigation item bothers me a lot. We only have one space, and don’t want more spaces (and won’t upgrade our license), yet I can’t seem to find an option to remove this. Something to add under Configuration > Features?

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support Azure DevOps Artifacts Universal Packages

    It would be nice to support Azure DevOps Artifacts Universal Packages feeds. We are slowly moving to Azure DevOps Artifacts (for artifact management only), and would like to use Universal Packages.

    https://docs.microsoft.com/en-us/azure/devops/artifacts/quickstarts/universal-packages?view=azure-devops&tabs=azuredevops

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  13. .NET Core 3.0 CLI support

    I have build agents with the .NET Core 3.0 SDK installed. I am unable to install the CLI as a dotnet tool, as the CLI will only run on .NET Core 2.X. I'd prefer not to have a separate container with the .NET Core 2.1+ runtime or SDK in order to use the CLI.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow 'Step Templates' to use fixed/specific package versions

    We've been trying to ensure that any 'Step Templates' created in Octopus contain scripts/code (PowerShell) that exists within a package. That package is then referenced as part of the 'Step Template'.

    The problem we have with this is that as soon as the package is pushed, it then gets used in any new releases. This means that we have no opportunity to test this in Octopus prior to new releases in pipelines using it.

    It would be useful if within the 'Step Template' we could specify/fix the package version (or specify a range) used so that all other pipeline releases…

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow date manipulation through use of the 'DateNow' and 'DateNowUtc' filters

    For example, allow us to add 1 hour to the time generated by 'DateNowUtc' or 'DateNow'.

    In my case, I want to pass in an expiry time when generating a SAS token in an ARM template, but it's inconvenient to have to use PowerShell to generate that expiry time and then set an output variable.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Increase the density of the dashboard

    The Dashboard somehow manages to show only 8 of my projects on a full-screen 1920x1080 browser. There is really no reason it shouldn't be able to show more than twice as many. There is just so much whitespace. This app should be about utility, and scrolling/searching really reduces the utility here.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. I have multiple nuget packages that I want to deploy to a single location, can this be done with Octopus Deploy?

    I have multiple nuget packages that I want to deploy to a single location (these nuget packages all make up the single Application), can this be done with Octopus Deploy?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Generate a deployment preview to show all variables and machines that will be utilized

    I would like to be able to generate a deployment preview without creating a release. I would like this preview to show all in-scope machines and variables that will be utilized given the selected parameters for the deploy. This will help greatly in identifying misconfigured scope for variables and machine roles/environments

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 64 65
  • Don't see your idea?

Feedback and Knowledge Base