Just checked policy-packs for the first time. Seem...
# general
s
Just checked policy-packs for the first time. Seems really promising šŸ‘ 1. Can you ā€œacknowledgeā€ a CrossGuard-policy,
enforcementLevel: "advisory"
, directly at the resource? To get this check out of the list of policy violations. Similar like
nolint
flags. 2. How can you check if a value is a secret value, i.e. encrypted in the stack? Just read that secrets are unencrypted in policy-pack checks.
m
Thanks for the questions, Dominik!
Can you ā€œacknowledgeā€ a CrossGuard-policy,Ā enforcementLevel: ā€œadvisoryā€, directly at the resource? To get this check out of the list of policy violations. Similar likeĀ nolintĀ flags.
We donā€™t currently have a way to do this, but itā€™s on our radar. I thought we had an existing issue tracking this, but couldnā€™t find it, so I went ahead and opened https://github.com/pulumi/pulumi-policy/issues/240.
How can you check if a value is a secret value
There isnā€™t currently a way to do this so Iā€™ve opened https://github.com/pulumi/pulumi-policy/issues/241 to track the suggestion. Please feel free to upvote and add more details on these issues. Thanks!
s
@microscopic-pilot-97530 Thanks for the answers & issues. Just one note: Weā€™re a Pulumi customer. Just mentioning this as you normally note this in the issues, I guess for prioritising stuff šŸ™‚
BTW: The
pulumi-policy
repo doesnā€™t have any topics in it, yet. I suggest to set at least
pulumi
,
policy
. Iā€™m not sure if adding the languages as topics is necessary. I think it wouldnā€™t hurt, on the other side. Githubā€™s topic listing seems to infer the language(s) from the code in the repo. E.g. for topic:policy, language:Typescript it would be easy to rank in the top 3 šŸ™‚
m
Edited those issues to indicate they indeed came from a customer. Great suggestion on adding the repo topics, thanks! Done. šŸ˜„
s
Yeah šŸ‘ Now the repos have enough marketing topics šŸ˜‰
Oh, donā€™t forget
javascript
on the
pulumi-policy
repo.
šŸ‘ 1