A call to all the provider/package maintainers: please update the

layout

field in the Mardown files in the

docs

folder are set to

package

. On Pulumi side, there are changes to the rendering of packages in the registry that requires it.

yall do not need to do a special release, just make sure its included in your next release ⬆️

@elegant-window-55250 @many-telephone-49025 @cuddly-flower-91328 @busy-journalist-6936 working on easier reusable workflows for the providers hosted here. Please review: https://github.com/pulumiverse/infra/pull/73

@limited-rainbow-51650 any interest of Pulumiverse to accept the donation of the Fly.io provider? https://github.com/dirien/pulumi-fly

@bulky-wall-65429 https://github.com/pulumiverse/pulumi-unifi/pull/110

Can someone help out on this issue? https://github.com/pulumiverse/pulumi-vra/issues/7

I can take a look tomorrow

hi there, I like to add vercel bridge provider, opened https://github.com/pulumiverse/.github/issues/36 but just wanted to say I’m here if you wanted talk online

@white-chef-55657, thanks! I am off om holiday right now, but maybe we can chat about this tomorrow? I can help you get started 🙌

Hi guys, recently I have been working on creating a new native provider for managing ESXi resources. Thanks to @limited-rainbow-51650 the repository is transferred under Pulumiverse. I managed to set up the release and CI workflows, but we are missing the repositories under NPM, Nuget, and PyPI.

Unable to publish @pulumiverse/pulumi-esxi-native v0.0.1 to NPM

(link to job)

Can someone please help with that?

https://github.com/pulumiverse/pulumi-vercel Repo is aligned to pulumiverse (thanks @limited-rainbow-51650 !) Who can help add relevant secrets so I can create and publish a release?

should I add my repo to https://github.com/pulumiverse/infra/tree/main/02-repositories so its CI is managed properly ?

https://github.com/pulumiverse/pulumi-vercel/pull/40 would appreciate a review so I can release

published https://github.com/pulumiverse/pulumi-vercel/releases/tag/v0.15.0 ! https://www.npmjs.com/package/@pulumiverse/vercel will it eventually show on the provider registry?

@white-chef-55657 congrats on the first release of the vercel provider. To register the vercel provider in the Pulumi Registry, add the vercel repo info to this file and submit a PR.

I’m considering the version pattern of my bridge provider, I’d like to somehow align it with the upstream provider was thinking of a scheme where the bridge has it’s own version, with a prerelease tag indicating the upstream provider version this will allow 1) updating the bridge as needed without losing the reference to the upstream version 2) updating the upstream provider without increasing the bridge itself something like 1.0.0-0.1.1 where 1.0.0 is the bridge version and 0.1.1 is the upstream provider version has this been discussed/thought of in the past? wondering if I can align myself to something that was already agreed upon

Hello everyone! For Canonical’s MaaS (Metal As A Service) users, I’ve produced this provider: https://pypi.org/project/pulumi-maas/ Slack Conversation

How come the installation instructions and API key instructions not make it into the registry entry? https://www.pulumi.com/registry/packages/vercel/

@billowy-army-68599 trying to use https://github.com/lbrlabs/pulumi-grafana/tree/main for my cloud grafana.net but i can't seem to make sense of the authentication. In the config i have:

config:
  grafana:auth:
    secure: <api key from grafana with Admin permissions>
  grafana:url: https://<my stack url>.<http://grafana.net|grafana.net>

I want to create a alerting rule so i start with just creating a folder like in the docs

const ruleFolder = new Folder(sanitizedClient, {
    title: client,
  });

Type                     Name                            Status                  Info
     pulumi:pulumi:Stack      xxx                             **failed**              1 error
 +   └─ grafana:index:Folder  yyy                             **creating failed**     1 error


Diagnostics:
  pulumi:pulumi:Stack (xxx):
    error: update failed

  grafana:index:Folder (yyy):
    error: 1 error occurred:
    	* status: 401, body: {"message":"Unauthorized","traceID":"b8784cb15a10a2d5d8f82ff44c8f37bd"}

Resources:
    1 unchanged

Duration: 3s

Any hints on which keys/urls to use?

can I get someone to either a) install renovatebot on my repo https://github.com/pulumiverse/pulumi-vercel b) configure dependabot so I can get regular dependency/security updates?

https://github.com/pulumiverse/pulumi-vercel/pull/45 can I get someone to approve this please?

Hello - I seem to have lost write access to https://github.com/pulumiverse/pulumi-vra (gh user:

schmidtw

) Could I be re-instated? We're ready to release 😄

@fierce-art-88136 you should have received an invite to join the

pulumiverse

organization.

Hi there, can someone review this PR: https://github.com/pulumi/registry/pull/3015

@elegant-window-55250 to keep our Pulumi SDK dependencies up to date for our Pulumi managed Github org, I'm also activating Renovate for the repo: https://github.com/pulumiverse/infra/pull/79

Should work fine 👍

Just don't close the

Dependency Dashboard

issue. 🙂 https://github.com/pulumiverse/infra/issues/81 Renovate continuously updates this ticket with the open PRs for dependency updates. I like that.

Hi All. I am looking to update a couple Pulumi providers I current maintain to add some new resources/features/attributes that were introduced. I attempted to re-run the

make tfgen

again, but it failed with the following error:

# <http://github.com/pulumi/pulumi/pkg/v3/resource/deploy/deploytest|github.com/pulumi/pulumi/pkg/v3/resource/deploy/deploytest>
../../../../../pkg/mod/github.com/pulumi/pulumi/pkg/v3@v3.76.1/resource/deploy/deploytest/languageruntime.go:31:9: cannot use &languageRuntime{…} (value of type *languageRuntime) as plugin.LanguageRuntime value in return statement: *languageRuntime does not implement plugin.LanguageRuntime (wrong type for method GeneratePackage)
                have GeneratePackage(string, string, map[string][]byte) error
                want GeneratePackage(string, string, map[string][]byte, string) error
# <http://github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tf2pulumi/il|github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tf2pulumi/il>
../../../../../pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.58.0/pkg/tf2pulumi/il/plugin_info.go:182:82: not enough arguments in call to workspace.GetPluginPath
        have ("<http://github.com/pulumi/pulumi/sdk/v3/go/common/workspace|github.com/pulumi/pulumi/sdk/v3/go/common/workspace>".PluginKind, string, nil, nil)
        want (diag.Sink, "<http://github.com/pulumi/pulumi/sdk/v3/go/common/workspace|github.com/pulumi/pulumi/sdk/v3/go/common/workspace>".PluginKind, string, *"<http://github.com/blang/semver|github.com/blang/semver>".Version, []"<http://github.com/pulumi/pulumi/sdk/v3/go/common/workspace|github.com/pulumi/pulumi/sdk/v3/go/common/workspace>".ProjectPlugin)
# <http://github.com/pulumi/pulumi/pkg/v3/engine|github.com/pulumi/pulumi/pkg/v3/engine>
../../../../../pkg/mod/github.com/pulumi/pulumi/pkg/v3@v3.76.1/engine/plugins.go:190:76: not enough arguments in call to workspace.GetPluginPath
        have ("<http://github.com/pulumi/pulumi/sdk/v3/go/common/workspace|github.com/pulumi/pulumi/sdk/v3/go/common/workspace>".PluginKind, string, *semver.Version, []"<http://github.com/pulumi/pulumi/sdk/v3/go/common/workspace|github.com/pulumi/pulumi/sdk/v3/go/common/workspace>".ProjectPlugin)
        want (diag.Sink, "<http://github.com/pulumi/pulumi/sdk/v3/go/common/workspace|github.com/pulumi/pulumi/sdk/v3/go/common/workspace>".PluginKind, string, *semver.Version, []"<http://github.com/pulumi/pulumi/sdk/v3/go/common/workspace|github.com/pulumi/pulumi/sdk/v3/go/common/workspace>".ProjectPlugin)
# <http://github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfshim/sdk-v2|github.com/pulumi/pulumi-terraform-bridge/v3/pkg/tfshim/sdk-v2>
../../../../../pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.58.0/pkg/tfshim/sdk-v2/resource.go:24:26: r.tf.SchemaMap undefined (type *schema.Resource has no field or method SchemaMap)
../../../../../pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.58.0/pkg/tfshim/sdk-v2/resource.go:90:67: r.tf.SchemaMap undefined (type *schema.Resource has no field or method SchemaMap)
../../../../../pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.58.0/pkg/tfshim/sdk-v2/resource.go:91:22: r.tf.SchemaMap undefined (type *schema.Resource has no field or method SchemaMap)
../../../../../pkg/mod/github.com/pulumi/pulumi-terraform-bridge/v3@v3.58.0/pkg/tfshim/sdk-v2/schema.go:137:23: e.SchemaMap undefined (type *schema.Resource has no field or method SchemaMap)
make: *** [tfgen] Error 1

The same error is returned when attempting to regenerate the sdks. Any ideas on how I can solve this?

https://github.com/pulumi/pulumi/pull/13800 another breaking change, this time hurting the community building pulumi providers can we have an open discussion on how to improve communication on changes to the pulumi ecosystem ?