For Concourse CI users, there is a new release of the Pulumi resource type. Here is the changelog: https://github.com/ringods/pulumi-resource/releases/tag/v0.4.0

Is there an issue or epic that currently exists for tracking adding the

pulumi state unprotect

functionality to Automation API?

Have a fix for getting yarn workspaces to work with inline functions, would appreciate a review 🙂 https://github.com/pulumi/pulumi/pull/8215

I've made the second PR to the go-cloud library which is used by Pulumi for state storage. That will fix https://github.com/pulumi/pulumi/issues/7251 and even more! It will allow to have storage URLs in

Pulumi.yaml

like

backend:
  url: <azblob://container?account_name=storage_account&subscription_id=sub-id-xxx>

or similarly for S3

backend:
  url: <s3://bucket_name?profile=your_profile_name_from_config>

so you don't have to do

pulumi login

when switching between projects! The PRs are: https://github.com/google/go-cloud/pull/3008 https://github.com/google/go-cloud/pull/3072 That's a deal breaker for us!

Hello @broad-dog-22463, are these issues automatically created by a bot? https://github.com/pulumi/pulumi-keycloak/issues/100 Just asking, because we contributed to the upstream TF provider and v3.5.0 is available: https://github.com/mrparkers/terraform-provider-keycloak/releases/tag/v3.5.0 We would like to see this in a new Pulumi provider version. 🙏🏼

Hi all! Just joined this community, and learned about Pulumi a couple weeks ago. I'm looking to add some capabilities to our Python/K8s Pulumi build, and noticed that relative imports and custom, non-Pulumi packages are not supported. For this reason, I was looking to make a custom Pulumi package to support some generic creation handling for our team....I saw the https://github.com/pulumi/pulumi-component-provider-py-boilerplate Is there a (more) simple provider example - more simplistic than the eks one?

Hi! I've been loving pulumi and came across a bug in

pulumi-docker

(#310) I believe I have a fix and wanted to put forward a PR but just wanted to check if I need to name the branch in my fork anything specific (I see other branches using

<username>/<descriptivename>

but can't tell if the username gets applied upon merge or if I need to name the branch that in my fork. (First time contributing to open-source so apologies for the simple question)

@echoing-match-29901 @microscopic-florist-22719 @tall-librarian-49374 Hello 👋🏼 I've ported the Hashicorp Terraform Time provider to Pulumi using TF Bridge, because I missed the functionality of Time based resources. What is the official way to get the provider registered at Pulumi since the Pulumi Registry is in place? https://github.com/tmeckel/pulumi-time https://registry.terraform.io/providers/hashicorp/time/latest

Hi, I would like to add a feature to the Opsgenie provider, namely being able to use more of the SDK's configuration. Upstream Terraform provider maintainers seem to be very non-responsive, so I thought about adding it directly to Pulumi. I understand what I need to do in terms of Go code on the upstream provider, but I can't find information on how to work on a Pulumi provider and generate the code with the pulumi-terraform-bridge. Can anyone point me in the right direction please?

I'm trying to port the HCP Terraform provider (https://github.com/hashicorp/terraform-provider-hcp) to Pulumi, but am running into issues. The provider code itself is in an

internal

folder (https://github.com/hashicorp/terraform-provider-hcp/tree/main/internal), which my non-Go-coding self has discovered is how Go denotes private code that can't be used by other code. Is there some kind of way around this restriction for Pulumi's purposes, or is this provider effectively impossible to convert to Pulumi using the tfbridge? Thanks.

I was looking at what it would take to bootstrap a JVM language provider for Pulumi (likely Java, then Kotlin/Scala can just wrap the Java package) Reading through the docs on creating a new language -- I don't understand why each language requires its own gRPC server 🤔 The protobuf definitions are shared, and looking at multiple SDK implementations like Node vs .NET, the gRPC server code seems nearly identical outside of flags and a handful of custom behaviors

Hi, I'm writing a TF bridge based provider and fail to build the donet sdk.

Microsoft (R) Build Engine version 16.4.0+e901037fe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 398.46 ms for /home/secustor/repos/pulumi-exoscale/sdk/dotnet/Pulumi.Exoscale.csproj.
Config/Config.cs(49,31): error CS0542: 'Config': member names cannot be the same as their enclosing type [/home/secustor/repos/pulumi-exoscale/sdk/dotnet/Pulumi.Exoscale.csproj]

Build FAILED.

Config/Config.cs(49,31): error CS0542: 'Config': member names cannot be the same as their enclosing type [/home/secustor/repos/pulumi-exoscale/sdk/dotnet/Pulumi.Exoscale.csproj]
    0 Warning(s)
    1 Error(s)

I know that this error can come from resource names, but I do not have any resource which is called

Config

. I guess it is referencing the attribute of

ProviderInfo

with the same name? https://github.com/secustor/pulumi-exoscale/blob/implement_baseline/provider/resources.go#L76 My repo is based on https://github.com/pulumi/pulumi-tf-provider-boilerplate Thanks for your help in advance!

Hi, I’ve encountered the same issue as here https://github.com/pulumi/pulumi-gcp/issues/148 and solved the issue. Unfortunately, I couldn’t run checks using gitpod. Is there another quick option? Or can I just make a pull request? My solution: https://github.com/pjbizon/pulumi-gcp/tree/cloud-functions-ts-allow-extraIncludePaths

Hello, I noticed an AWS managed policy was missing and added it here: https://github.com/pulumi/pulumi-aws/pull/1833 Is this the correct process for contributing?

Hi, we are looking on how to mock rpc calls in our golang tests (mostly for

Lookup*

stuff). We would like to extract

ctx.Invoke()

function and wrap around that in the interface, with

DefaultInvoker

implementation. Would you see this as an acceptable option or can it cause some problems which would make it a no?

Hello, I’m using

pulumi-tf-provider-boilerplate

and updated all the info required for organization/namespace and provider name. Had to use the shim trick to expose the TF provider internal go package, but that is now in place. At the

make tfgen

step, I get this error now:

$ make tfgen
[ -x /usr/local/bin/pulumi ] || curl -fsSL <https://get.pulumi.com> | sh
pulumi plugin install resource random 4.3.1
(cd provider && go build -o /Users/ringods/Projects/pulumiverse/pulumi-unifi/bin/pulumi-tfgen-unifi -ldflags "-X <http://github.com/pulumiverse/pulumi-unifi/provider/pkg/version.Version=0.0.1-alpha.1646771690+ecf121e7.dirty|github.com/pulumiverse/pulumi-unifi/provider/pkg/version.Version=0.0.1-alpha.1646771690+ecf121e7.dirty>" <http://github.com/pulumiverse/pulumi-unifi/provider/cmd/pulumi-tfgen-unifi)|github.com/pulumiverse/pulumi-unifi/provider/cmd/pulumi-tfgen-unifi)>
# <http://github.com/pulumi/pulumi/pkg/v3/codegen/schema|github.com/pulumi/pulumi/pkg/v3/codegen/schema>
../../../golang/pkg/mod/github.com/pulumi/pulumi/pkg/v3@v3.23.2/codegen/schema/loader.go:120:30: not enough arguments in call to pkgPlugin.Install
        have (*os.File)
        want (io.ReadCloser, bool)
make: *** [tfgen] Error 2

Am I using a wrong package version of something? https://github.com/pulumiverse/pulumi-unifi

To support Pulumi plugins to be downloaded from more various sources, the

pulumi plugin install

command needs a thorough revision. I made a proposal for this, hoping to get this in the v4.0 release on time, in the corresponding ticket: https://github.com/pulumi/pulumi/issues/9007#issuecomment-1101347426 I hope we can get the discussion started!

@broad-dog-22463 In the Python codegen code, I see the following snippet: https://github.com/pulumi/pulumi/blob/45f7a064846a4a8e541e5d6647ba5f673a07f040/pkg/codegen/python/gen_program.go#L133-L138 Am I right to assume that the

"python":

section in the

schema.json

can accept a

"packageName":

property? If so, is it an oversight that this property is not generated by the TF bridge? https://github.com/pulumi/pulumi-terraform-bridge/blob/5c2d9875a867700c3e03df6fa21323ce407b96e3/pkg/tfgen/generate_schema.go#L309-L316

I'm building a Pulumi provider from a Terraform one, using Pulumi's boilerplate as usual. I built another one last week which works fine. The current one is having issues when testing the Python SDK. In particular, it doesn't work because it seems like

wheel

is needed in the virtualenv, but it's not present in the virtualenv. It also doesn't work when I add

wheel

to my test project's

requirements.txt

file. Has anyone else run into this before? Thanks.

Question re: Pulumi roadmap RUST support?

Hey Folks! Recently, I was struggling with AWS infrastructure deployment and had the idea to create a tool. It’s based on Pulumi: https://github.com/cloudytool/cloudy And I created AWS EC2 cluster Pulumi template: https://github.com/cloudytool/pulumi-aws-cluster

Hello, I wonder if we could get some eyes/review on https://github.com/pulumi/pulumi/pull/9610 . We're hitting some major perf issues using the self hosted backend, and can't move to the managed one yet (for reasons). So this one addition would make a very large improvement for us (we see something ridiculous like 10GB+ of transfer on a pulumi preview atm).

I maintain the HCP provider and am in the process of updating it to use the latest version of the underlying Terraform provider. In the course of doing this, however, I see that nearly all the documentation strings for the inputs of the functions (as opposed to resources) have been removed (see, e.g., https://github.com/grapl-security/pulumi-hcp/pull/11/files#diff-f325ddd0ffc367195603053fa9d5c8ba562d0e867d1520f05da6cda9678c9fe9L1698) I didn't update any of the Pulumi code (e.g., the terraform bridge, the forked terraform plugin SDK repo, etc., though subsequent experimentation shows this happening with all the Pulumi code updated to current versions). I'm not quite sure why this happened; I don't see any terms that might trigger the dreaded

Found <elided> in parsing...

messages in many of these descriptions. I'm also curious if there's any way to manually affect these documentation strings, both to fix this, as well as to fix some other documentation parsing issues I've seen in this and another provider I maintain. The "overlay" mechanism from the bridge sounds like it would be potentially useful, but I can't find any documentation around it to know one way or another. Anybody have any ideas or suggestions (@broad-dog-22463?) Thanks in advance 🙇

Is this channel redundant with the addition of #contribex, or do they serve different purposes / audiences?

I grabbed some setup from

pulumi-kubernetes

for OpenAPI to Pulumi schema generation. Can someone from the dev team shed some light on what

pulumictl get version

exactly does to determine a version? This command doesn’t work for me, given I’m bootstrapping a new native provider and don’t have any commits nor tags yet in that repo.

Starting in 5 minutes!

@quiet-wolf-18467 regarding pulumi-kubernetes: The SDKs are generated from

schema.json

. Is the provider’s plugin binary code also generated (partially)?

Hi all, would appreciate some quick 👀 on https://github.com/pulumi/pulumi-kubernetes/pull/2007

Hi contributors (and potential contributors)! We’re going to start having a monthly contributor community meeting to help facilitate communication between all of you and our internal contributors, and all contributors and potential contributors are invited to come participate! The meeting will happen at 10a Pacific on the second Wednesday of every month for the rest of the year, starting with our first meeting on 13 July 2022 at 10a PDT. The meeting will be recorded and published publicly on YouTube. This meeting is focused on the open-source community and contributions. The agenda is driven by contributors (that's you!), and it will focus on any and all open-source projects related to Pulumi and the Pulumiverse, including community integrations and other elements of the Pulumiverse. Examples of questions or topics that will be included: • How can I find good first issues to work on? • How do we want to approach… in the code? • Discussion around an architectural approach for providers It is not a support call; those kinds of questions or topics should be directed to Slack, GitHub Discussions, or Office Hours (livestream). Examples of questions or topics that will not be included: • How do I use Pulumi to do…? • When will you fix…? • What is <this Pulumi term>? If you’re a contributor or wish to contribute and are interested in joining the meeting, please let me know where I can send a meeting invite! I’ll be opening up a list of topics to vote on next week after the US holiday. If you have a topic you'd like me to include in the voting list for the agenda, please let me know! Thanks! Excited to get this going!