Hey pulumiverse! First of all thanks for picking u...
# pulumiverse
Hey pulumiverse! First of all thanks for picking up the grafana provider 🙂 I've raised an issue to get the underlying terraform provider upgraded to 2.13.0 from the current 1.43.1 (https://github.com/pulumiverse/pulumi-grafana/issues/113), however I was wondering if there was a guide on how to do this as I'd love to help contribute
@lemon-angle-60291 had a quick look and the Grafana provider is now using the Terraform Plugin Framework. The currently mapped provider version is using the older Terraform Plugin SDK v2. This is a major upgrade, because it must be mapped via the
module of Terraform Bridge. @ancient-policeman-24615 @enough-garden-22763 do we have a description in place how to upgrade a SDKv2 provider to a PF provider? Or is https://github.com/pulumi/upgrade-provider capable of performing this upgrade. Oh and on top: the Pulumi Grafana provider requires a shim.
Hi Thomas and Thomas, hope this finds you well! We do in fact have some notes in https://github.com/pulumi/pulumi-terraform-bridge/blob/master/pf/README.md?plain=1#L119
As to automation I don't think it's in place yet. I have a sense the notes might have gotten a tad out of date, perhaps this is our opportunity to support you and update them.
@enough-garden-22763 I should definitely run a
find . -name '*.md'
in the Bridge repo. 😄 Thanks for pointing us in the right direction!
@lemon-angle-60291 With the
you should be ready to go 🙂 to try an upgrade of the Grafana provider. If you run into issues post them here. We're happy to help.
Awesome, thanks both for your help! I'll give it a go ❤️
I've raised a PR to do the upgrade - https://github.com/pulumiverse/pulumi-grafana/pull/114 It turns out that the Grafana Terraform provider supports both the plugin framework and the sdk so I was able to do the version bump without the migration.
When I find some time, and if no one beats me to it, I'll also try to move from supporting sdk to framework
@lemon-angle-60291 onboarding of the provider to Pulumiverse is not completely finished and I don't know who are the maintainers. @limited-rainbow-51650 @cuddly-flower-91328 what's the plan here? Maintainers? Pulumiverse Board Members? Didn't see someone assigned in PR 163
@big-architect-71258 I'm the maintainer of the migrated grafana provider. Now bear with me, we migrated 3 providers all at once and I had to execute the namespace changes, publishing etc this week. I will start with getting them up to date slowly. Co-maintainers welcome though!
@big-architect-71258 btw, why do you think the migration is not completely finished?
@limited-rainbow-51650 Sorry if my post sounded harsh or something. Blame it to my German nature 🙂 > @big-architect-71258 btw, why do you think the migration is not completely finished? The PR isn't merged yet.
Which PR?
Do I confuse here something?
That PR is only needed to bring the repositories under the Pulumi managed IaC setup of
github organization. Each of these providers are updated and re-published from Pulumiverse including migration docs: https://www.pulumi.com/registry/packages/grafana/installation-configuration/#migrating-from-the-lbrlabs-package Nobody should be blocked here.
That's what I meant. So you got confused by my wording. Sorry. But who will approve the PR of @lemon-angle-60291?
Me, when I get the time. (FYI: this is community and not part of my job description at Pulumi Corp)
I merged the PR and tagged v0.3.0. Release: https://github.com/pulumiverse/pulumi-grafana/releases/tag/v0.3.0
The Pulumi Registry has a cron based mechanism to check for new releases of third party providers. Within a few hours, this new release will be detected and a preview of the new docs will get published in a PR. I’ll make sure that Registry PR gets merged as well.
Thanks Ringo!