Skip to content

Utilizing Structured Configuration Mixed with Secrets #7418

Discussion options

You must be logged in to vote

Both config.RequireObject and config.RequireSecretObject work here.

You should generally use RequireSecretObject in cases where there are secrets in the config, or else the secretness will not be tracked and secrets could get leaked by your program. We are soon going to make this a warning/error to not use RequireSecretObject in these cases.

Both end up working the same in my scenario, properly decrypting the secrets into Parameter Store, but showing them as `[secret]' when output to the console.

I suspect this is because there's an additional filter on all CLI output which replaces anything that is a secret config value with [secret], even if it's not actually being treated as a Secret

Replies: 2 comments 3 replies

Comment options

You must be logged in to vote
0 replies
Answer selected by lukehoban
Comment options

You must be logged in to vote
3 replies
@lukehoban
Comment options

@dustinbrooks
Comment options

@dustinbrooks
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions about existing features resolution/fixed This issue was fixed
2 participants
Converted from issue

This discussion was converted from issue #7384 on July 01, 2021 23:29.