Hey team, I'm currently using the new `awsx` beta,...
# general
a
Hey team, I'm currently using the new
awsx
beta, version
1.0.0-beta.5
. I am encountering an issue with the plugin when attempting
pulumi up
locally on my M1 mac. Plugin seems to be working fine on github actions linux hosts.
Copy code
error: could not load plugin for awsx provider 'urn:pulumi:dev::cfx-solana::pulumi:providers:awsx::default_1_0_0_beta_5': could not read plugin [/Users/wizardfiction/.pulumi/plugins/resource-awsx-v1.0.0-beta.5/pulumi-resource-awsx] stdout: EOF
o
If you run this command does it solve the issue?
pulumi plugin install resource awsx 1.0.0-beta.5
And if you could entertain another question, what's the output of:
Copy code
ls -laR ~/.pulumi/plugins/resource-awsx-v1.0.0-beta.5
a
o
huh
a
I'm wondering if it's an M1 mac thing
I have another stack that is using
0.40.0
, and I have no issues locally
o
Yeah it could be. What happens when you try to run that file manually - I expect you should get some sort of error, but I'm wondering what MacOS will do since the error you gave suggests the file is empty/doesn't exist.
a
Although I'm a little confused bc these plugins seem global
o
From a shell:
Copy code
~/.pulumi/plugins/resource-awsx-v1.0.0-beta.5/pulumi-resource-awsx
a
something seems borked
o
huh, okay, I think the process being killed might be expected - those plugins have a handshake they do with the pulumi engine and maybe that's what it should look like?
but it looks like MacOS let you "run" it
what happens when you try to use it in your pulumi project now?
a
when i run
pulumi up
i get the original error
I uninstalled the awsx plugin and it wont let me reinstall at version 0.40.0. Get the 403 HTTP error in the screenshot above
it does let me install the beta
o
I've added some info from this thread here: https://github.com/pulumi/pulumi-awsx/issues/850 I think our platform team is looking into this
1
a
For what it's worth, seems to be working as expected on linux (github actions runner)
I'm not really sure why i'm getting the 403 trying to install version 0.40.0
o
If you try to install latest - no 0.4.0 - does that work?
Oh I see, you did
a
Weirdly I have another stack that seems to behave correctly
Although my package.json is set to 0.40.0
If the plugins are global to my machine, I would expect this other stack to have issues as well
o
Hmm
I wish I could dig in further, I know we have some M1 team members - please comment and let them know and share any additional details on that thread.
I unfortunately am on Windows & Ubuntu, I wish I could help more
a
No worries, will do
Appreciate your comments