Seeing an error with the latest Pulumi CLI and the AWS provi

Question

Seeing an error with the latest Pulumi CLI and the AWS provider running in a Dev Container see thread

quick-hospital-63970 · Answer

Nothing has changed that I m aware of other than recently rebuilding the container and probably getting a new Pulumi version

quick-hospital-63970 · Answer

```error could not load provider for resource urn pulumi dev bouncer awsx ecs FargateService$aws ecs service Service medbillai dev bouncer ecs service could not create provider urn pulumi dev bouncer pulumi providers aws default 5 35 0 5c0fb91f acda 46bf 80a8 f2e0e807e69c load plugin for aws provider urn pulumi dev bouncer pulumi providers aws default 5 35 0 failed to load plugin home node pulumi plugins resource aws v5 35 0 pulumi resource aws fork exec home node pulumi plugins resource aws v5 35 0 pulumi resource aws exec format error```

quick-hospital-63970 · Answer

I m using Pulumi programs with a custom executor built on Automation API so it s a little hard to test plain `pulumi` commands but our `refresh` action fails without output and `destroy` gives the above

quick-hospital-63970 · Answer

I m on v3 91 1 of the CLI

quick-hospital-63970 · Answer

Tried updating all our NPM packages to latest too but no dice

quick-hospital-63970 · Answer

Ahh we were also using a pretty out of date AWS plugin we manually install a specific version updating that to <https github com pulumi pulumi aws releases|latest> seems to have resolved the problem

quick-hospital-63970 · Answer

Does anyone happen to know if `installPlugin`<https github com pulumi pulumi blob a6050592f15ed3f8c494e98fa247e00b1c44d031 sdk go auto workspace go L120C1 L121| supports> a latest specifier or something instead of specific version