Send a list of paths that should be redacted to the policy runtime#38600
Draft
dsa0x wants to merge 21 commits into
Draft
Send a list of paths that should be redacted to the policy runtime#38600dsa0x wants to merge 21 commits into
dsa0x wants to merge 21 commits into
Conversation
Contributor
Changelog WarningCurrently this PR would target a v1.16 release. Please add a changelog entry for in the .changes/v1.16 folder, or discuss which release you'd like to target with your reviewer. If you believe this change does not need a changelog entry, please add the 'no-changelog-needed' label. |
jbardin
reviewed
May 21, 2026
| var priorAttrRedactedPaths []cty.Path | ||
| if schema != nil { | ||
| attrRedactedPaths = schema.SensitivePaths(attrs, nil) | ||
| priorAttrRedactedPaths = schema.SensitivePaths(priorAttrs, nil) |
Member
There was a problem hiding this comment.
Sensitive paths don't come from the schema, they come from the state value. The schema contributes to those paths, but it is not the only source. The current and prior values may also have different sensitive paths.
dsa0x
force-pushed
the
policy-pr5-init-policy
branch
6 times, most recently
from
ceca9d8 to
f6cce9a
Compare
dsa0x
force-pushed
the
policy-pr5-init-policy
branch
from
f6cce9a to
abe1c41
Compare
dsa0x
force-pushed
the
policy-pr5-init-policy
branch
2 times, most recently
from
fcb3f12 to
6c5df78
Compare
dsa0x
force-pushed
the
policy-pr5-init-policy
branch
2 times, most recently
from
137d602 to
cc2ed92
Compare
dsa0x
force-pushed
the
policy-pr5-init-policy
branch
from
cc2ed92 to
1b55da5
Compare
dsa0x
force-pushed
the
sams/redact-sensitive-paths
branch
from
a8c2c3d to
fe23d22
Compare
dsa0x
force-pushed
the
policy-pr5-init-policy
branch
6 times, most recently
from
3d0811b to
7155955
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #
Target Release
1.16.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry