What is the pulumiverse mascot meant to be? Pretty sure it's not a platypus.

set the channel topic: 😛ulumiverse: The universe of all things Pulumi (https://github.com/pulumiverse)

howdy 👋 trying to build a tf bridge provider, failing hard in the initial steps https://github.com/pulumi/pulumi-tf-provider-boilerplate/issues/79 would appreciate any help

or perhaps if there’s a different way I should great a tf bridge provider?

@quiet-wolf-18467 Hi David 👋🏻 I've created a Pulumi Provider out of the Terraform Time Provider using TF Bridge. I wonder if it would be possible to move the repo to Pulumiverse. https://github.com/tmeckel/pulumi-time

Made some updates to the awesome-pulumi list - https://github.com/pulumiverse/awesome-pulumi/pull/25

Hi I converted the quickstart k8s java example into Kotlin/JVM and I would like to share where: https://github.com/luistrigueiros/quickstart-pulumi-k8s-kotlin

@thousands-hairdresser-72380 hello. I was just watching the recording of the Pulumi Contributor Community Meeting. Regarding your question on structural representation of infrastructure, you can use our YAML support for custom resources, if you distribute your custom resources as a Pulumi Package (aka Multi-Language Component). https://www.pulumi.com/blog/pulumiup-pulumi-packages-multi-language-components/

is anyone able to add me to the pulumiverse org in npm?

@elegant-window-55250 I made a last minute change to https://github.com/pulumiverse/infra/pull/28 Can you re-approve?

Done

A bit of information in case you received a Github email that you are removed from a Pulumiverse provider repository: today I simplified the Pulumi code which manages the Pulumiverse Github organization. Before this change, the access was configured to include a Github Team:

GH repo <- GH team <- GH member

I changed this and now added everyone directly:

GH repo <- GH member

with the same permissions. So although you were removed from the team, you were added again directly. Too bad all those Github email notifications are sent out which might confuse you. 🙏🏼

If you are interested in helping out with some provider development, do let us know! 😉 https://twitter.com/pulumiverse/status/1562110045092978691

#pulumiverse What's the correct practice to request a PR review in Pulumiverse? Shall I pick one of the available reviewers or is there a defined procedure for this? @limited-rainbow-51650

Hi All. I am working on bridging a Terraform provider I’ve built into pulumi, and I intent to put that in the registry once it is ready. I have few questions regarding the boilerplate refactoring that are not super clear to me. 1. In the

provider/resources.go

In the Golang section below, I see the url pointing to the pulumi repository instead of the provider repo. Which one is correct?

Golang: &tfbridge.GolangInfo{
			ImportBasePath: filepath.Join(
				fmt.Sprintf("<http://github.com/pulumi/pulumi-%[1]s/sdk/|github.com/pulumi/pulumi-%[1]s/sdk/>", mainPkg),
				tfbridge.GetModuleMajorVersion(version.Version),
				"go",
				mainPkg,
			),
			GenerateResourceContainerTypes: true,

2. In

provider/cmd/pulumi-resource-foo/main.go

it also points to a pulumi repository i.e zpa “http://github.com/pulumi/pulumi-xyz/provider” Should the repository still point to pulumi instead? Looking at other providers, they all point to pulumi instead of their own repo as specified in the boilerplate.

@big-architect-71258 here is the PR with the correct secret configuration: https://github.com/pulumiverse/pulumi-time/pull/3

@limited-rainbow-51650 approved

@limited-rainbow-51650 who will create the initial release and when of the Time provider. The GitHub actions only get triggered if a new version tag is created.

Hi together, great to see, that Pulumiverse is growing 🙂 @limited-rainbow-51650 Supported me with transfering pulumi-heroku provider to Pulumiverse. Thanks for that. It would be great if it can be published as well. Is there somebody who can support me? I’ve created a draft PR: https://github.com/pulumiverse/pulumi-heroku/pull/4 Thanks in advance. 🙂

@big-architect-71258 FYI, I will continue after the weekend. I hope I have an answer on this by then: https://github.com/orgs/community/discussions/30927

@big-architect-71258 the

docs

folder of your

time

provider is copied over for registry publishing. But on the registry side, there are linting failures. Can you fix these in the provider repo? https://github.com/pulumi/registry/runs/8041632103?check_suite_focus=true#step:7:33

@limited-rainbow-51650 I had to laugh so hard, when I saw THIS:

@limited-rainbow-51650 The Time provider still doesn't show up in the Pulumi Registry. Is there something missing. Checked the registry pipeline already:

Hi there, I am bridging a Terraform provider I’ve built to Pulumi, but when testing the GO example, I am receiving the following error below. Any idea what may be the problem?

  pulumi up                                                                                       master 
Previewing update (zscaler/go_zpa_app_connector_group)

View Live: <https://app.pulumi.com/zscaler/go_zpa_app_connector_group/go_zpa_app_connector_group/previews/882288d9-8109-46a3-a2e7-b12fee77dfa2>

     Type                     Name                                                   Plan       Info
 +   pulumi:pulumi:Stack      go_zpa_app_connector_group-go_zpa_app_connector_group  create
     └─ pulumi:providers:zpa  default                                                           1 error

Diagnostics:
  pulumi:providers:zpa (default):
    error: could not read plugin [/Users/wguilherme/go/bin/pulumi-resource-zpa] stdout: EOF

Hi all, I would like to donate my Aquasec Pulumi provider to the Pulumiverse GitHub organisation. https://github.com/dirien/pulumi-aquasec Is there anything I have to do? I already used everywhere “Pulumiverse” (module, package, etc.)

Community contributor meeting in 5 minutes! https://pulumi-community.slack.com/archives/CB81H6DG9/p1663174129551209

@many-telephone-49025 if you want the aquasec provider be listed on Pulumi’s registry, first create a release of your provider to have it published. Then create a pull request in

pulumi/registry

like this one: https://github.com/pulumi/registry/pull/1030/files