No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

hi room, i am seeing `pulumi up` trying to replace my current-state aws providers with an older provider version (even though i have the newer version of the plugin installed) … wondering how this is controlled and how i can get my `pulumi up` to not downgrade my providers (details in thread)

Screen Shot 2021-06-15 at 9.34.20 am.png

Screen Shot 2021-06-15 at 9.35.09 am.png

```providers = {}
for region in itplat_allregions_list:
    providers[region] = aws.Provider(region, region=region)```

just providing providers named by region we can iterate over as required

we use providers this way as we have resources duplicated in various groupings of regions

so we can as a pseudocode example
`for region in list: create bucket s3:myregional_bucket_&lt;region&gt; provider=&lt;region&gt;`

Check your library dependencies? `npm check-updates -u` or equivalent?

pip list shows
```pulumi            3.3.1
pulumi-aws        4.6.0
pulumi-eks        0.30.0
pulumi-kubernetes 3.1.0````


so the bit that has me confused is… i have read in the past that pulumi up will install all the latest plugins

so when i run pulumi up i would think it shoudl update pulumi-aws in my venv

but i just upgraded manually pulumi-aws in my venv and yeah it is no longer trying to downgrade… thanks <@U012UJTT55M>

The plugins and the libraries often share numbers, but they're not the same.

You need to upgrade the language clients (libraries). Generally, Pulumi looks after the provider binaries (plugins).