I suggest you...

Provide a hash of sensitive variables so we can determine if they have changed

I'm working on code for a Terraform module for modifying Octopus Deploy configuration, and when we have variables with the type set to Sensitive (or IsSensitive=true), Octopus understandably does not return the value of the variable.

However, this means it is impossible to determine if the value is set correctly.

One workaround would be to provide a hash (even a salted hash) of the value when it is set. Then we could compare our hash against the hash in the API, and if they don't match then update the sensitive variable.

E.g. A new field called `ValueHash` which is `sha1(Name + Value)`

4 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark Henderson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Mark Henderson commented  ·   ·  Flag as inappropriate

        I neglected to mention - the reason it's very important to know if the value is correct is because otherwise Terraform will update the variable on every single run, which is not what we want if the value hasn't changed. As it is right now I cannot support Sensitive variables at all.

      Feedback and Knowledge Base