fierce-art-88136
08/04/2023, 11:13 AMCan someone please help with that?(link to job)Unable to publish @pulumiverse/pulumi-esxi-native v0.0.1 to NPM
limited-rainbow-51650
08/04/2023, 1:05 PMfierce-art-88136
08/04/2023, 1:07 PMlimited-rainbow-51650
08/04/2023, 1:22 PMfierce-art-88136
08/07/2023, 8:57 AMlimited-rainbow-51650
08/09/2023, 11:05 AMpulumi plugin install resource esxi-native <version> --server <github://api.github.com/pulumiverse>
fierce-art-88136
08/09/2023, 11:14 AMlimited-rainbow-51650
08/09/2023, 11:44 AMfierce-art-88136
08/09/2023, 11:47 AMlimited-rainbow-51650
08/14/2023, 1:57 PMfierce-art-88136
08/14/2023, 2:00 PMlimited-rainbow-51650
08/14/2023, 2:07 PMBlocked on
section in the description. Don't mind that PR. I have updated the repo access to level Maintain
manually.fierce-art-88136
08/14/2023, 2:09 PMlimited-rainbow-51650
08/14/2023, 2:10 PMpulumi/registry
, similar to this one, but for your repo?
https://github.com/pulumi/registry/pull/2992fierce-art-88136
08/14/2023, 2:11 PMlimited-rainbow-51650
08/14/2023, 2:12 PMfierce-art-88136
08/14/2023, 2:21 PMlimited-rainbow-51650
08/14/2023, 2:32 PMpulumi-esxi-native
. At Nuget, the key is definitely still valid. Last week, with a similar setup, the vercel provider was succesfully published. Not sure what's wrong here.Manage package
in the menu on the right of your package listing. After clicking that, you should see a section > Owners
. Please add pulumiverse
as an owner.fierce-art-88136
08/14/2023, 2:54 PMlimited-rainbow-51650
08/14/2023, 2:58 PMfierce-art-88136
08/14/2023, 3:01 PMlimited-rainbow-51650
08/15/2023, 9:16 AMfierce-art-88136
08/15/2023, 9:24 AM