Repository navigation
Pulumi provider releases lag behind upstream terraform-provider-stackit #295
Description
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.0It 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!
Activity
s-inter commentedon May 6, 2026
Hey, thanks for the write-up and the offer to contribute!
To answer your question:
release.yamlisn't the bottleneck. The gap comes one step earlier — our upgrade pipeline opens a PR that requires a manual review before it gets merged and a release is cut, and that step is hard to avoid right now.While looking into this, I also noticed that the latest release is
v0.89.0even though the upgrade tov0.91.0is already merged. I'll check with the team why that release hasn't been triggered yet.s-inter commentedon May 8, 2026
Just wanted to follow up on this!
As the provider is still in alpha, we are keeping the release process manual for the time being. Depending on the changes introduced upstream, each update might require several adjustments, which takes time. We are committed to keeping the delta between this provider and the upstream terraform-provider-stackit as small as possible.
Automating the release pipeline is something we may revisit down the road, but there is no concrete timeline for that at this stage.
Closing this for now, but feel free to reopen or start a new discussion if anything comes up!