<@UK4HNFLCB> can you please let me know how I can ...
# pulumiverse
s
@limited-rainbow-51650 can you please let me know how I can obtain write access on pulumi-grafana and pulumi-buildkite? Who would be the maintainer to speak to? Thank you! (I'm trying to build and publish upgrades!)
l
@shy-arm-32391 I'm the maintainer of the Grafana provider. You can talk to @miniature-musician-31262 for the Buildkite provider. https://github.com/pulumiverse/infra/blob/main/03-members/cnunciato.yaml
🙌 1
❤️ 1
@shy-arm-32391 a thread which might be of interest regarding resource versioning for the Grafana provider: https://pulumi-community.slack.com/archives/C04NPQTRKM4/p1774951240500259
s
Good morning and thank you! can you tell me more about these versioned resources? I do see them [on the registry](https://www.pulumi.com/registry/packages/grafana/api-docs/apps/v2beta1/dashboard/), what am I missing?
(lowkey this is why I love oss, I still get to work with you @limited-rainbow-51650 ❤️ )
💜 1
l
I wasn't satisfied with the default naming in the Pulumi provider based on the TF resource name. I knew from the Kubernetes provider that it also has submodules/namespaces in the SDKs for various API versions, so I asked Fraser how to do that. It ends up pretty similar.
And the module names in Pulumi provider map to the grouping you see in the menu on the left of Grafana TF provider: https://registry.terraform.io/providers/grafana/grafana/latest/docs
s
So, basically - the idea is to have the modules organized differently? Rather than a
v2beta1
module, have the API version appended to the end instead?
l
No, the version is at the end in the TF module name. I wanted the version like in Kubernetes:
<namespace>:<module/version>:<resource>