Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. We're currently using Octopus to manage our Kubernetes clusters, but we're interested in transitioning to a GitOps Pull Model (rather than the current Push based approach where the Octopus Server is executing kubectl commands against our clusters) in which (in a similar fashion to the polling tentacles Octopus already offers), a service would run within our clusters and periodically
    poll both git repositiories and docker registries/helm feeds for changes and sync the cluster state accordingly.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. I have a prompted variable to ask the deployer to enter a ticket number. If they enter anything other than a number my automation breaks. So I would like to restrict the user input to being only a number.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Octopus is getting used more and more with Linux and CLI tools in the Linux ecosystem. Those tools often output ANSI codes, particularly for color.

    Most of the time it's possible to turn the color output/ANSI codes off but the lack of color can make deployment logs much less readable.

    Other tools in the CI/CD process do support basic ANSI codes (color), eg. Github Actions, Gitlab CI, Jenkins etc.

    As an example of log output that is much more difficult to read without color: terraform plan

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. This would be useful for replacing values especially in the values-file from Chart Package or Additional Package. With this feature we don't need to have variable replacement syntax in our source-files.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. When a deployment has failed, it shows on a tenanted dashboard as the latest release, when I'm wanting to know which version was last deployed/currently active (our deployments rollback if unsuccessful), but right now there's no way on showing only success deployments.

    It would be a great feature for this to be one of the Advanced Filters options.

    Also, maybe as a side and could be a bug, that latest release number, even if failed, actually shows up as the current released version when doing a multi deployment i.e. using the Deploy To window

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. On the Deployments -> Overview page, instead of just an = operator when filtering by release, it would be very helpful to allow filtering by >= and <= operators. It would also by very helpful to filter just on major and minor release numbers as well or both independently.

    Ex 1: filter by all tenants on major version X or greater
    Ex 2: filter by all tenants on major version X and minor version Y or less (to find everyone impacted by a specific bug)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. I have successfully set up an AWS ECR package feed and can find the Helm charts I have pushed there when I test the feed. However, ECR feeds do not show in the dropdown for package source in the Helm step.

    I also tried using the oci:// address of the ECR as a Helm Feed, but receive the message "Only 'http' and 'https' schemes are allowed. (Parameter 'requestUri’).”

    It would be great to be able to use at least one of these as a source for the chart.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. The ability to use variables exists in so many different places when setting up Kubernetes deployments, but one place I would think would make the most sense is the container image name.

    When creating step templates, I found this one field a barrier from allowing me to use the templates because we use that image name for checking logs for various debugging.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Add Deployments link to Worker View like what exists for deployment targets

    Deployment target link path example: /app#/Spaces-1/infrastructure/machines/Machines-xxxx/deployments

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. We have a case where we want to have a runbook to handle restoring Databases from different sources to different targets.

    To handle this we have a form sheet with prompted variables.

    But we also have the case where we want to do a restore daily to one of our databases. To do this we would need to be able set a trigger and also to set the prompted variables within that trigger.

    I understand this can be done through the API currently but would rather see this in the UI.

    My workaround for now is to duplicate the runbook…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Microsoft opened up a preview for ARM base Azure Cloud Service, which is probably hinting on them moving away from a Classic cloud service deployment model:
    https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/overview
    Please add support for this type of targets.

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. https://help.octopus.com/t/feature-request-variable-sets-spanning-spaces/26948/4

    We have multiple teams and have so far been avoiding spaces because we have no way that we know of to share variables and scripts between teams in different spaces.

    We have a lot of shared configuration that we wants accessible by all and with only one source of truth. For example, we have many apps that need to add whitelisting for our build/deploy servers. We store that ip whitelist in an octo variable set so all project can access it. If I need to alter that whitelist I can be confident that if I change the values in…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. when I choose “Create Release” and the lifecycle only runs in one place, the Save button should tell you it’s going to go ahead and run.

    idk what you call this icon with the orange square and white lightning bolt

    but when the lifecycle is in this state, the save button really means, “go ahead and run”.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. As a project leader I should be able to group variables on Octopus UI. This can be just logical separation.

    This solve the problem with linked variables and help mange them.

    For example It could collapse elements that are in structure - for example: db.username and db.password can be collapse as elements of root db or by labeling variables and then can be filtered by using specific label, for example - db.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Allow each individual determine what deployment emails they want to receive. Users on multiple teams, or large deployment teams, are bombarded with hundreds emails a day. Giving the user the ability to tell the system they only want to receive failures, or no emails at all, would provide a better user experience. Alternatively, if this is not possible, allowing the system to have a single designated email for deployment notifications. This would allow the users to designate something like a Teams Channel to receive the notifications, and cut down on the amount of emails being sent in general.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. I find that deployments to Azure Functions and standard app services will occasionally fail due to files being locked. This usually requires stopping the app service, re-running the deployment, and then restarting the function or app.

    This can be scripted with Powershell, but since this is such a common scenario, I’d love a checkbox built into the Azure App Service step that provides this ability. Something like “Stop App Service prior to deployment and restart after deployment”.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. First I want to say that the new API functionality added in latest versions is very appreciated especially the possibility to export/import project out of spaces. However we really miss the merge functionality when importing project from Non-prod octopus to Prod Octopus

    Our current automated procedure includes : Delete project-> Re-import Project-> Update prod variables

    Problems: It removes history and require a new release number in prod due to updated of variables.

    Addition to this feature requests includes: Exclusion of environment variables in export

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add ability to define custom substitution filters that can run scripts defined by the end user.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Tentacle retention policy is executed once all deployments steps are completed. When the retention policy step starts running, it blocks any other step.
    This behavior is by design and can't be configured.

    This design can cause issues if for some reason the retention policy step encounters issues and takes a long time to complete.

    As a workaround we can add a deployment step of a dummy package at the end of the deployment process. As result the tentacle retention is executed at the last step of the deployment.

    I would like to have an option to control when the retention…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 25 26
  • Don't see your idea?