This message was deleted.
# general
s
This message was deleted.
b
Hey @ambitious-father-68746 What versions of plugins are you using?
a
This is a playthrough of what's happening to me:
Copy code
$ pulumi version
v2.11.2
Copy code
$ pulumi plugin ls | grep aws
aws         resource  3.6.1    246 MB  n/a        28 minutes ago
Copy code
$ venv/bin/pip list | grep aws
pulumi-aws        3.6.1
Copy code
$ pulumi up
Previewing update (prod):
[resource plugin aws-2.13.1] installing
Downloading plugin: 66.51 MiB / 66.51 MiB [========================] 100.00%
Copy code
$ pulumi plugin ls | grep aws
aws         resource  3.6.1    246 MB  n/a        32 minutes ago
aws         resource  2.13.1   228 MB  n/a        1 minute ago
From the stack:
Copy code
"resources": [
            {
                "urn": "urn:pulumi:prod::lytt::pulumi:providers:aws::default",
                "custom": true,
                "id": "20f38ddf-92c6-44a3-8dfe-a9b1f79df3fc",
                "type": "pulumi:providers:aws",
                "inputs": {
                    "region": "eu-west-1",
                    "version": "2.13.1"
                },
                "outputs": {
                    "region": "eu-west-1",
                    "version": "2.13.1"
                }
            },
I have multiple AWS accounts and I create a custom provider for each account, assuming a role to execute code there. I actually don't have any resource on the main account, I only use it as a jump point.
Maybe because of this the default provider is never updated?
Anyway, after validating that I had no resource that depended on that one, I've used
pulumi state rm
to get rid of it and I don't have that problem anymore.