Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

jsonplan and jsonstate: include sensitive_values in state representations #28889

Merged
merged 2 commits into from
Jun 14, 2021
Merged

jsonplan and jsonstate: include sensitive_values in state representations #28889

merged 2 commits into from
Jun 14, 2021

Commits on Jun 11, 2021

  1. jsonplan and jsonstate: include sensitive_values in state representat… 

    …ions

A sensitive_values field has been added to the resource in state and planned values which is a map of all sensitive attributes with the values set to true.

It wasn't entirely clear to me if the values in state would suffice, or if we also need to consult the schema - I believe that this is sufficient for state files written since v0.15, and if that's incorrect or insufficient, I'll add in the provider schema check as well.

I also updated the documentation, and, since we've considered this before, bumped the FormatVersions for both jsonstate and jsonplan.
    @mildwonkey
    mildwonkey committed Jun 11, 2021
    Configuration menu
    Copy the full SHA
    3eff3ff View commit details
    Browse the repository at this point in the history

  2. SensitiveValues should be an interface, not a bool

    @mildwonkey
    mildwonkey committed Jun 11, 2021
    Configuration menu
    Copy the full SHA
    f18e035 View commit details
    Browse the repository at this point in the history