many-psychiatrist-74327
04/01/2022, 1:32 PMpackage.json
and removing node_modules
and calling yarn install
again, when I run pulumi preview
, I get:
aws:iam:Role (eks-cluster-node-group-role):
error: could not validate provider configuration: 1 error occurred:
* Invalid or unknown key
followed by a bunch of stack traces that look like this:
Error:
at Object.debuggablePromise (/scratch/node_modules/@pulumi/pulumi/runtime/debuggable.js:69:75)
at /scratch/node_modules/@pulumi/pulumi/runtime/invoke.js:126:45
at Generator.next (<anonymous>)
at fulfilled (/scratch/node_modules/@pulumi/pulumi/runtime/invoke.js:18:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
unhandled rejection: CONTEXT(6017): Invoking function: tok=kubernetes:yaml:decode asynchronously
STACK_TRACE:
Error:
at Object.debuggablePromise (/scratch/node_modules/@pulumi/pulumi/runtime/debuggable.js:69:75)
at /scratch/node_modules/@pulumi/pulumi/runtime/invoke.js:126:45
at Generator.next (<anonymous>)
at fulfilled (/scratch/node_modules/@pulumi/pulumi/runtime/invoke.js:18:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
unfortunately this error isn’t very useful
Any hints?infra
(doesn’t conflict with the provider names)
• I’m not using an explicit aws Provider. Instead, I’m setting aws:account
and aws:region
in my Pulumi.<stack>.yaml
fileaws:account
is the invalid key. would be nice if the error showed which was the missing or invalid keygreat-queen-39697
04/04/2022, 9:03 PMpulumi about
and a pulumi config ls
for me (and please redact any confidential info) if you haven't figured this out yet? I'll see if I can help