No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

image.png

<@UK4HNFLCB> I had to laugh so hard, when I saw THIS:

Perhaps we should configure soem `pre-commit`rules for this. Great tool BTW. Did you ever use it in a project?

<@UK4HNFLCB> just filed the PR for fixing the linting errros

<@UK4HNFLCB> merged the PR. Will you trigger the registry publication process again?

Maybe it’s a good thing you try it yourself. One note: don’t use signed git tags for now. (git tag cli arg `--no-sign`)

Ummm ... Didn't get you. I created the v0.0.6 tag by myself, what created the first successful publication of the provider. But I mean: who triggers the pipeline in the Registry repo again. Or are the Registry CI connected to the different provider repos and fire when a new release tag in he provider repo is defined?

There is a cron job which checks the provider repos for new releases. When a new release is available, a PR is auto-created in the registry repo which is then processed by one of the engineering teams at Pulumi. So nothing to be done by any of us

Example of such an automatic PR: <https://github.com/pulumi/registry/pull/1410>

<@UK4HNFLCB> thanks for elaborating on this :+1::skin-tone-3:

<@UK4HNFLCB> just created a new Tag `v0.0.7`without signing. Hope we're done publishing the first version of the Time provider :crossed_fingers::skin-tone-3: Hopefully the Registry pipeline will finish successfully.

<@UK4HNFLCB> I'm a bit surprised: I used `git tag --no-sign v0.0.7` to create the tag. But GitHub is showing it as `verified` . That's a bit odd.

Last week, I always had the args reversed: `git tag v0.0.x -m "Some message" --no-sign`

Ugh :disappointed: Didn't expect that the sequence of parameters to the `tag`  command is of any relevance. Thanks for the tip :+1::skin-tone-3:

It shouldn’t, according the docs. Not sure what would happen if I would have changed the order of the args on my system. Was just reporting that I had them reversed last week. :wink:

Next time I'll add `--no-sign`  at the end of the command like you did. We'll see then what happens