I’m having problems upgrading from pulumi 2 to 3 (...
# general
m
I’m having problems upgrading from pulumi 2 to 3 (and upgrading the plugin dependencies). After upgrading the CLI and changing the versions in
package.json
and removing
node_modules
and calling
yarn install
again, when I run
pulumi preview
, I get:
Copy code
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:
Copy code
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?
• My project name is
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
file
hmm looks like
aws:account
is the invalid key. would be nice if the error showed which was the missing or invalid key
g
can you run a
pulumi 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