Ability to publish Java SDKs

[ringods]

We should investigate what is needed to publish the Java SDKs of all the providers under the Pulumiverse umbrella.

[ringods]

Info from @dirien:

• https://www.jetbrains.com/help/space/publish-artifacts-to-maven-central.html
• https://central.sonatype.org/publish/requirements/

[ringods]

Request for a repository at Maven Central:

https://issues.sonatype.org/browse/OSSRH-86096

[ringods]

@cobraz to publish Java SDKs to Maven Central with com.pulumiverse we must:

To register this Group Id you must prove ownership of the domain pulumiverse.com. Please complete the following steps to continue:

Add a DNS TXT record to your domain with the text: OSSRH-86096. Please read https://central.sonatype.org/faq/how-to-set-txt-record/
Edit this ticket and set Status to Open.

More info: https://central.sonatype.org/publish/

Can you execute this on a short term?

[simenandre]

Record is added! Can you change the status to open on the ticket?

[ringods]

@cobraz tnx. Sonatype ticket is set to open.

[muhlba91]

is there already any update?

afaik, we‘d require the publish username and password secrets, and signing certificate and password set as github actions secrets in this org.
e.g. see the gcp provider action: https://github.com/pulumi/pulumi-gcp/blob/master/.github/workflows/release.yml

[ringods]

I still need to finish the setup of the upstream Sonatype registry. But our Github Actions workflows in general have a lot of inconsistencies over all the current providers. I would like to have some more generalization there so that adding Java publishing becomes much easier.

[ringods]

Support to publish Java packages is dependent on this upstream issue:

pulumi/pulumi-java#1359

Please upvote the upstream issue as much as possible if you need Java support.