You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How a provider needs to be build, packaged and released is mainly defined by Pulumi. They also have a lot of automation for keeping the Github Actions workflows up to date in all of the provider repositories.
We could benefit from having an automated setup serving two purposes:
initial setup of the workflows for new providers being set up in Pulumiverse
updating the workflows to support new features coming from Pulumi (e.g recent addition was support for Java)
Pulumi is aware that building & releasing a provider must become must simpler. There is planned work to make the pulumi/ci-mgmt a consumable artefact. This artefact, with the proper configuration, would be able to generate the correct workflows for a provider repository.
Let's follow up on that work, test it, provide feedback (issues & PR), so we can build on top of that effort.
The text was updated successfully, but these errors were encountered:
How a provider needs to be build, packaged and released is mainly defined by Pulumi. They also have a lot of automation for keeping the Github Actions workflows up to date in all of the provider repositories.
We could benefit from having an automated setup serving two purposes:
Pulumi is aware that building & releasing a provider must become must simpler. There is planned work to make the pulumi/ci-mgmt a consumable artefact. This artefact, with the proper configuration, would be able to generate the correct workflows for a provider repository.
Let's follow up on that work, test it, provide feedback (issues & PR), so we can build on top of that effort.
The text was updated successfully, but these errors were encountered: