This message was deleted.

Since awsx is a package a not a provider, there isn’t a plugin to install in this case. You do need the base

aws

plugin on which the awsx package is built though.

Ah ok - got it thanks!

Correct. You can filter in the registry by type. Component == package. https://www.pulumi.com/registry/

Just one more quick question for you - is there a way to specify the latest version in

ws.installPlugin

? Docs don’t mention anything about this and the version property seems to be required

There is not. Though, you could parse

requirements.txt

or

pip list

and automate installing the matching plugins.

So how do you know what version is required? I tried using the latest aws version (v4.34.0) but it errors out saying it expects v4.33.0. Locally, I’m using aws version v4.15.0 and it works fine so not sure how to figure out which version to specify. I don’t want my next release to randomly break obviously.

I would recommend just matching the plugin version to the sdk version. So if pinned to v4.15.0 of the aws sdk, you would use v4.15.0 of the plugin. That way you know things will work and it’s deterministic.

Hmm but I’m using v4.15.0 locally and when I specify that version for the plugin, Automation API errors out saying v4.33.0 is required?

I suspect the environment the automation api code is running in has v4.33.0 of the sdk installed. I just tested in a clean environment where I installed 4.15.0 of the sdk and the automation api code installed v4.15.0 of the plugin and things worked. If I repeat that experiment where I first install 4.33.0 of the sdk and try to install 4.15.0 of the plugin, I get the error about needing plugin v4.33.0. So, it seems like the environment has 4.33.0 of the sdk installed.

Hmm OK so I must have confused it somehow. I’ll take a look again. Thanks a lot for your help - it’s much appreciated!