https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# pulumiverse
s
This message was deleted.
f
@limited-rainbow-51650 can you help with this?
l
Not today. Will be somewhere next week earliest.
🙌 1
f
Also for adding it to the Pulumi Registry, will you be able to help with it?
l
Yes, but we first need to get a release out which complies with all requirements.
🙌 1
f
hi @limited-rainbow-51650, did you have time to check it out?
l
They look good. Tnx.
Only the install command must be updated: 
pulumi plugin install resource esxi-native <version> --server <github://api.github.com/pulumiverse>
f
Already done 🙏
Okay then, as you prepare the repositories let me know so I can rerun the release to publish the first version 🙌
l
@fierce-art-88136 parallel to your esxi provider, we accepted the vercel provider. This provider got a first succesfull release today using this workflow file. You might want to compare or adopt this one for the esxi-native provider too: https://github.com/pulumiverse/pulumi-esxi-native/blob/main/.github/workflows/release.yml
🙌 1
f
Actually, I got the workflow from Time and Harbor providers and adopted it for ESXi one
@limited-rainbow-51650 the things I did change in there are adding names for the steps that were missing, using the latest versions for some steps, and for others instead of the commit hash version I used the semantic step versions.
what do you want there to be changed
Hi @limited-rainbow-51650, do you have some time to look into this? I will be going on vacation in Thursday, so I would like if we can publish it before that
l
I think I found it. The pre-pulumiverse publishing credentials you set on your repo override the org-level ones. I removed your repo-level ones. Can you retry publishing a new version?
f
sure thanks, I did not not know that the secrets got transferred too
I sow that you PR for adding me as a maintainer did fail can you check that again?
l
See the 
Blocked on
section in the description. Don't mind that PR. I have updated the repo access to level 
Maintain
manually.
f
l
In the meantime, can you prep a PR in 
pulumi/registry
, similar to this one, but for your repo? https://github.com/pulumi/registry/pull/2992
🙌 1
f
Will do it thanks 🙏
l
The processing of that latter PR is in the hands of another team. Given we have a company wide week off, that one might land no sooner than next week though.
f
I see well, at least I will prepare it before vacation
the nuget key is not working
can you check if it is still the old one present?
l
These are the Actions secrets for 
pulumi-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.
@fierce-art-88136 I found it. Can you remove the package published under your personal nuget account, or transfer ownership to the `pulumiverse` organization on Nuget? https://www.nuget.org/packages/Pulumiverse.EsxiNative/0.0.3-alpha.1691424086
@fierce-art-88136 on Nuget.org, you should see 
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.
f
Added
l
Ownership accepted and if your refresh the page, you should see it now. I retriggered the failing dotnet publish build.
And published!
🙌 1
f
🎉
I added the PR to the registry as well: https://github.com/pulumi/registry/pull/3015
l
Tnx. Expect a delay in processing that PR as the company is having a refresh week, which is a company wide week of time off.
🙌 1
f
thank you for the support 💪
Open in Slack
PreviousNext
Powered by