big-architect-71258
06/07/2023, 10:53 AMrelease.yaml
is copied around by provider maintainers. #package-authoring
https://github.com/search?q=org%3Apulumiverse%20matrix.dotnetverson&type=code
So I'm wondering why the publishing step works anyway and if this is something that has to be fixed in all affected providers.
@limited-rainbow-51650limited-rainbow-51650
06/07/2023, 11:10 AMschema-tools
issue I'm working on, I have a related branch for reusable workflows which will make use of the patched schema-tools: https://github.com/pulumiverse/infra/tree/matrix-simplified
Once this is fixed, I'll be testing it in a provider I maintain myself:
https://github.com/pulumiverse/pulumi-unifi/tree/reuse-workflows
before I will communicate to roll this out for the other providers.big-architect-71258
06/07/2023, 11:14 AMlimited-rainbow-51650
06/07/2023, 11:18 AMbig-architect-71258
06/07/2023, 11:28 AMCheck worktree clean
step. I took every precaution I know of, especially using the same Go Version locally to create the SDK and the provider, as within the pipeline. Can you help me here to figure out why tfgen
created a new schema.json
, what changed the Python SDK, what eventually stopped the pipeline. The publishing process is definitely something that makes me think to stop contributing. Sorry to say, but it's really frustrating.
https://github.com/pulumiverse/pulumi-mssql/actions/runs/5199560930/jobs/9377293948make build_sdks
locally and check with git status
manually if the worktree stays clean.go clean -cache -modcache -fuzzcache
limited-rainbow-51650
06/07/2023, 3:29 PMbig-architect-71258
06/07/2023, 3:30 PM