General

  1. Support the new In-VM metadata service for load balanced nodes

    Microsoft has just released the Azure in-VM metadata service that will let you know when a machine is going to be rebooted.

    it would be great to tie this into the node maintenance functionality so that the node is automatically drained.

    It might be useful to do this for AWS as well (similar to https://github.com/scopely/shudder), but that looks a lot harder.

    0 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 →
  2. Provide access to account credentials during deployments

    When a deployment is being executed, there may be some value in providing access to account credentials that have already been stored and managed in Octopus Deploy.

    While the primary motivating factor for creating the accounts section has been to provide access to deployment targets, some users may get value from using them to access or control other parts of their deployment process that sit behind some authentication mechanism. This would allow OD to better manage all the resources needed to fully complete a deployment with authentication details being securely managed in one place.

    The biggest concern with this approach…

    0 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 →
  3. 0 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 →
  4. Multi-select tentacles for changing environment/roles

    Enable a way to make a changes (add/remove environment, add/remove role) to multiple tentacles at once.

    0 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 →
  5. Hide Release

    Over time, older releases that are no longer in use just crowd up the release screen. I want to retain their history, so do not want to delete them.

    It would be nice to be able to hide releases.

    0 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 →
  6. Add an ability to define your own package install directory

    having a variable to be able to define your own package installation directory is needed. We have a situation where we rely on roles to define variables for customers, but the package on the same environment will not install if it already has been, even though it needs to be re-extracted for the role variables to be applied. Having to force the package redeployment on all projects then takes a lot longer than it should. Having the ability to add role to the path of the package directory would stop this from being an issue for us. Something similar to…

    0 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 →
  7. Add option to Rention Policy to 'Keep last package' always

    We need an option in the retention policy to allow for keeping the last updated package in the repository 'always'.
    There are cases where the latest release does not included the latest package, but that package may still be needed later on.

    Source: UV 941

    0 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 →
  8. Show differences in scope values

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

    When displaying snapshots, show any variables whose scope values don't appear in the current set available to the project (owner)

    At the start of deployment, warn if scope values have changed (e.g. if Production is deleted and recreated, there will be a variable scoped to the old Production environment ID, apparently useful but not applied)

    Where the name associated with a scope value has changed, show the old and new names

    0 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 →
1 2 61 62 63 65 Next →
  • Don't see your idea?

Feedback and Knowledge Base