Hey,
The Pulumi provider in this repo trails terraform-provider-stackit — new TF provider versions don't trigger a corresponding Pulumi release, so the gap between the two keeps growing.
As a workaround we've fallen back to Pulumi's generic terraform-provider package across our code base:
source: terraform-provider
version: 1.0.2
parameters:
- stackitcloud/stackit
- 0.93.0
It works, but we'd much rather consume the native Pulumi provider.
Is there a reason release.yaml isn't triggered on upstream releases? A scheduled job that diffs against the latest TF release, or a repository_dispatch fired from the TF provider repo, would close the gap. Happy to contribute a PR if useful.
Thanks!
Hey,
The Pulumi provider in this repo trails
terraform-provider-stackit— new TF provider versions don't trigger a corresponding Pulumi release, so the gap between the two keeps growing.As a workaround we've fallen back to Pulumi's generic
terraform-providerpackage across our code base:It works, but we'd much rather consume the native Pulumi provider.
Is there a reason
release.yamlisn't triggered on upstream releases? A scheduled job that diffs against the latest TF release, or arepository_dispatchfired from the TF provider repo, would close the gap. Happy to contribute a PR if useful.Thanks!