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

warning: Configuration 'newrelic:apiKey' value is a secret; use getSecret instead of get #7126

Closed
austinbutler opened this issue May 21, 2021 · 1 comment · Fixed by #7129
Closed

warning: Configuration 'newrelic:apiKey' value is a secret; use getSecret instead of get #7126

austinbutler opened this issue May 21, 2021 · 1 comment · Fixed by #7129
Assignees
@justinvp
Labels
kind/bug Some behavior is incorrect or out of spec p1 A bug severe enough to be the next item assigned to an engineer resolution/fixed This issue was fixed
Milestone
0.57

Comments

@austinbutler
Copy link

Following the upgrade to Pulumi 3.3.0, I get this warning:

warning: Configuration 'newrelic:apiKey' value is a secret; use `getSecret` instead of `get`

I never directly refer to apiKey config, so I assume it's due to how this resource gets the secret internally.

Expected behavior

This resource provider should access via getSecret instead of get and no warning should be emitted.

Current behavior

Warning is emitted.

Steps to reproduce

Just use this resource in Pulumi and run pulumi up.

Context (Environment)

Just using it.
@justinvp justinvp self-assigned this May 24, 2021
@justinvp justinvp transferred this issue from pulumi/pulumi-newrelic May 24, 2021
@justinvp justinvp added kind/bug Some behavior is incorrect or out of spec p1 A bug severe enough to be the next item assigned to an engineer emergent labels May 24, 2021
@justinvp justinvp added this to the 0.57 milestone May 24, 2021
@justinvp justinvp mentioned this issue May 24, 2021
Open
@justinvp
Copy link
Member

We're going to temporarily disable this new warning in a patch release. #7127 tracks re-enabling the warning without this issue.

@justinvp justinvp mentioned this issue May 24, 2021
Merged
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label May 24, 2021
lblackstone added a commit to pulumi/pulumi-kubernetes that referenced this issue May 26, 2021
@lblackstone
Update pulumi deps
5961612 
- Codegen change from pulumi/pulumi#7128
and remove hardcoded templates for v1/Secret resources
- Nondeterministic import ordering fix from pulumi/pulumi#7126
@lblackstone lblackstone mentioned this issue May 26, 2021
Merged
lblackstone added a commit to pulumi/pulumi-kubernetes that referenced this issue May 26, 2021
@lblackstone
Update pulumi deps
7bf7186 
- Codegen change from pulumi/pulumi#7128
and remove hardcoded templates for v1/Secret resources
- Nondeterministic import ordering fix from pulumi/pulumi#7126
lblackstone added a commit to pulumi/pulumi-kubernetes that referenced this issue May 26, 2021
@lblackstone
Update pulumi deps (#1588)
6f45fa6 
- Codegen change from pulumi/pulumi#7128
and remove hardcoded templates for v1/Secret resources
- Nondeterministic import ordering fix from pulumi/pulumi#7126
@renovate renovate bot mentioned this issue May 26, 2021
Open
1 task
@renovate renovate bot mentioned this issue Jun 6, 2021
Open
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justinvp justinvp

Labels
kind/bug Some behavior is incorrect or out of spec p1 A bug severe enough to be the next item assigned to an engineer resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.57
Development

Successfully merging a pull request may close this issue.

Temporarily disable config secrets warning pulumi/pulumi
3 participants
@austinbutler @justinvp @pulumi-bot