pulumiverse / pulumi-mssql

Pulumi provider for Microsoft SQL Server and Azure SQL
Apache License 2.0
2 stars 1 forks source link

fix: backout of pulumi/pulumi-package-publisher@v0.0.6 #4

Closed tmeckel closed 1 year ago

tmeckel commented 1 year ago
tmeckel commented 1 year ago

@ringods Sorry. But I found a wrong variable reference. 😞

image

Because I copied the release.yaml from a working provider this error effects many (or all) Providers hosted on Pulumiverse

https://github.com/search?q=org%3Apulumiverse%20matrix.dotnetverson&type=code

So I wonder why the publishing process could ever worked.

ringods commented 1 year ago

@tmeckel the main problem is that the GHA workflows used by Pulumi to manage the providers are not in a state to be reused in a 3rd party context (like Pulumiverse). For example, at the moment I working on getting this fixed: https://github.com/pulumi/schema-tools/issues/42

There is work going on to bring the tooling around this to a reusable state, but we aren't there yet. If you copy snippets from different places, each having a different point in time state & situation, it probably won't work. For the moment, take the release workflow from a working setup like the aquasec provider. That should get you in a releasable state for now.

tmeckel commented 1 year ago

@tmeckel the main problem is that the GHA workflows used by Pulumi to manage the providers are not in a state to be reused in a 3rd party context (like Pulumiverse). For example, at the moment I working on getting this fixed: pulumi/schema-tools#42

There is work going on to bring the tooling around this to a reusable state, but we aren't there yet. If you copy snippets from different places, each having a different point in time state & situation, it probably won't work. For the moment, take the release workflow from a working setup like the aquasec provider. That should get you in a releasable state for now.

@ringods That's my point. The aquasec provider is suffering from the mentioned issue as well

image

That's why I wonder why the publishing steps work anyway.