Skip to main content

Adding global secrets

Feature RequestsContent EditingPersonalization

As a user, I would like to have the option to define sensitive information as global secrets so that I can add them as variables in our templates. The benefits is two-fold:

1) In case the variable value changes, we can do it in just a single place and all usages will be updated automatically

2) We can then decouple the contents of sensitive information and "hide" it from editors. A quick example of this could be an API key that is part of a payload.

In addition, each secret could have an option to be redacted on previews if we still want to prevent the secret from being shown to editors.

Status: Backlog1 comment

Log in to comment and vote

Comments1

  • Rory Colsell

    Team•

    Jul 2, 2024

    Thanks for the feedback @Jorge Documet . This makes complete sense.

    Our current thinking is that we could introduce the concept of global variables that are defined at the project level and used in content or other parts of the product using something like {{ project.varaibleA }} tags, for example.

    We think this could solve for the use cases you mentioned, and some others. The point you make about redacting in previews is a good one. Perhaps we would need to add an option to redact for each variable or even for all variables.

    I don't have a solid date for when this will become available, its not on our immediate roadmap, but its something we're shaping internally and have plans to work on.

    If you have any further thoughts or questions, let us know.