JonG

My feedback

  1. 167 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Richard,

    There is a shortcut that can help – if you right click on a variable, there’s a Duplicate option. It doesn’t work with multiple selections however, but it should get you part of the way.

    Paul

    JonG supported this idea  · 
    JonG commented  · 

    Ollie's suggestion of having an Import/Export from/to csv option on a variable set for mass-update is critical, and should probably get its own feature request.

    Also, +1 for a dropdown when creating a "new" variable set to clone from an existing.

    I would also add an option to multi-select variables within a variable set to scope multiple selections at once.

  2. 447 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    JonG commented  · 

    Need ability to give teams permissions to edit the Library Variable Set used in their own environments without being able to view/edit variables in other Library Variable Sets.

    Possible solution is to add Scoping to variable sets as well as respecting scoping on individual variables within the variable sets.

    Add: Scoped and Unscoped Library Variable View/Edit permissions.
    Add: Scoped and Unscoped Library Variable Set View/Edit permissions.

  3. 31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    JonG commented  · 

    I would like to enhance this by also requesting Octopus also allow for loading/using a "Script Signing Certificate" on the Octopus server that will be consumable (in a domain/CA) by the destination (tentacle) systems, allowing servers in a locked down production environment to execute powershell scripts (my company wont allow staging and prod's powershell execution policy to be anything less than AllSigned (ie: does not allow Unrestricted or RemoteSigned) thus forcing us to load the signed scripts into Nuget packages and consume them on the tentacle boxes.

    However, to fully utilize Octopus's Step Templates, and other built in powershell execution capability, the Octopus server will need to be able to sign the scripts with a powershell script-signing cert that is installed in the domain CA, so the tentacle boxes can execute them with the security team's signoff (thank goodness Octopus has well-implemented project-level RBAC).

    Implementing script signing and Allowing admins to select which certificate Octopus uses to sign the scripts (per environment would be even more awesome, due to our multiple domains) will be the only way we will be able to use advanced octopus capabilities like step-templates and "Run a Script" steps against our internal server deployment locations.

    JonG supported this idea  · 

Feedback and Knowledge Base