The Zoom link was just updated in the document. If you have problems entering the call, this is the correct Zoom link for today’s Pulumi & Pulumiverse contributor call: https://pulumi.zoom.us/j/87909483977?pwd=R210SHhtaVdXUHdNZTA1UC9uREt1QT09

We are now in Serverless Land. Submit your patterns if you want to have it included. https://twitter.com/jbesw/status/1633128056419393537

Because not everyone is in #pulumiverse, I also share this here.

When creating a provider using the terraform boiler plate, is there a way to handle an instance where the module path is different than the repo path?

I am looking to add test coverage to my custom provider created using the pulumi-provider-go, are there any examples of using the integration server to test component creation? I only see an example of testing function invocations here but not seeing how I would test a resource/component. Thanks.

Is there a way to handle a tf provider that calls a sub provider passing it command line args? The acme plugin I've been working on started doing that a few months ago. So going through the tf boiler plate works but the plugin blows up because it tries to pass the command line arg

-dnsplugin

to the pulumi plugin 🙂

Hi, Do you know any ways to debug node js native provider (adding flags to pkg or run it through bash as in python) and core engine (cli)?

Greetings, At the moment I am trying to add Import Feature to My Proof-of-concept Provider. I succsefuly implemented create,update,delete,diff,check methods, but I can not implement a Read properly. I am a little bit confused becase nodejs return signature is different from the go signature and I couldn't find an example for nodejs. My signature, but I tried also include inputs here and only inputs. Is it something about my code( if yes, can you please give some advice) or at the moment there is no import feature for nodejs providers?

{
	id:AsIRececivedIt,
	props:{
	allKeysOfTheBackend
}
}

Do you want to keep your Pulumi Personal Access Token secure in 1Password? You can now! The shell plugin for Pulumi I contributed a few weeks ago landed in 1Password CLI v2.17.0! 🎉 https://app-updates.agilebits.com/product_history/CLI2 https://developer.1password.com/docs/cli/shell-plugins/pulumi/

debugging plugins and configuration keys Hello, on GitHub I found the PR that adds support to attach the engine to a running plugin via the env var

PULUMI_DEBUG_PROVIDERS

. My problem is that, even before being able to use the debugger, I get an RPC error as follows: Start plugin and get port:

~/.pulumi/plugins/resource-hcloud-v1.11.1/pulumi-resource-hcloud
52401

Start the engine:

$ PULUMI_DEBUG_PROVIDERS=hcloud:52401 pulumi up
Previewing update (dev):
...
Diagnostics:
  pulumi:providers:hcloud (default):
    error: rpc error: code = InvalidArgument desc = required configuration keys were missing

Where do I get these

required configuration keys

? thanks!

Hi, new guy here. I am currently looking at a good-first-issue issue that is related to the cmd. I have implemented the change, I would like to test my change functionally locally before creating a PR, however, I am getting a lot of errors for attempting to build it using the command

make dist

. Normally what would be the best approach to test functionality changes? Would it be local or directly on the CI/CD pipeline? WOuld love to know the best approach here.

Hi, the file

sdk/go/pulumi/config/require.go

says at the beginning: // Code generated by "generate.go"; DO NOT EDIT. What that does even mean for this case?. I see here there are functions used to load the secrets from a stack there and could not find anywhere where the codegen generate the functions based on any parameter. If not in this file, where then? 🤔

Hi, I was setting up my local for pulumi repo and while running the

make dist

command I am getting the following error. Can anyone please help me resolve it ?

Hello all, I opened a PR a couple of days back for a Feature Request that I was encouraged to implement. I am not sure how it continues now. Is there anything I should do to trigger feedback/reviewing?

👋 Hey there, I've pushed this PR a while back: https://github.com/pulumi/pulumi-command/pull/194, would be super helpful to get it merged. I am looking for a review on it.

Hi all, I'm trying to package pulumi for a well known linux distro and i'm having a bit of a hard time tracking the build when it comes to SDKs (the version (i.e.

v3

is now appended to the end of the module string in go.mod for nodejs and go however the SDK folder hierarchy in the repo doesn't.. track?)).. I'm also trying to forgo the

go install

in the Makefile and instead use

go build

which is introducing it's own set of issues... is there someone i could DM with that would be willing to give some pointers as i work through packaging?

👋 Hello again, I've submitted another bugfix PR for the EKS plugin: https://github.com/pulumi/pulumi-eks/pull/886 Since

1.0.2

the plugin is just broken if you use EKS Fargate without explicit subnetIDs (which, I would argue, is most common use case). It's also fixing an issue with using non-default AWS provider with this plugin.

I'm looking into modifying the YAML runtime to support a

!include extra.yaml

reference type to allow for multi-file referencing. Does that conflict with any underway work? Proposal: Main entry remains the same,

main.yaml

, or

pulumi.yaml

. Within that file, a reference of

!include xyz.yaml

would cause the yaml decoder to locate the referenced file and append and overwrite values into the main.yaml. A simple overwrite-last method would be used, meaning contents of

!include 1.xyz.yaml

would be overwritten by

!include 2.zyx.yaml

if any keys or attributes match. Otherwise, unique values would just be added. Concerns: I'm trying to decide if

!include

should be a local reference level or global. Consider:

main.yaml

resources:
  s3-bucket:
    !include s3-bucket.yaml

s3-bucket.yaml

type: aws:s3:Bucket
properties:
  name: mybucket

vs:

main.yaml

resources:
  !include s3-bucket.yaml

s3-bucket.yaml

resources:
  s3-bucket:
    type: aws:s3:Bucket
    properties:
      name: mybucket

Write order:

main.yaml

resources:
  !include 1.s3-bucket.yaml
  !include 3.s3-bucket.yaml
  !include 2.s3-bucket.yaml

1.s3-bucket.yaml

resources:
  s3-bucket:
    type: aws:s3:Bucket
    properties:
      name: original-bucket
      tags:
        Application: something-useful

2.s3-bucket.yaml

resources:
  s3-bucket:
    type: aws:s3:Bucket
    properties:
      name: final-bucket
      tags:
        Owner: myself

3.s3-bucket.yaml

resources:
  s3-bucket:
    type: aws:s3:Bucket
    properties:
      name: applied-but-overwritten-bucket
      tags:
        Environment: Dev

Output:

resources:
  s3-bucket:
    type: aws:s3:Bucket
    properties:
      name: applied-but-overwritten-bucket
      tags:
        Application: something-useful
        Owner: myself
        Environment: Dev

Also, I desire the workflow of having wildcard support:

main.yaml

resources:
  !include account*.yaml

account_main.yaml

main-aws-account:
  type: aws:organizations:Account
  properties:
    name: main-aws-account

account_secondary.yaml

secondary-aws-account:
  type: aws:organizations:Account
  properties:
    name: secondary-aws-account

Hello! I opened a PR to resolve this Issue about a week ago to bump the aws-sdk version to support sso-session backed profiles for AWS S3 Login and AWS KMS Secrets. Is there anything else I needed to do for the PR to be reviewed/accepted or is it just a waiting game until someone has time?

Hello! Totally forgot about reaching out through Slack, I created a pull request, pulumi/actions#986 to take advantage of writing output to the GitHub step summary. Who can I ask for review?

Hi all 👋 . I've just made my first contribution (https://github.com/pulumi/pulumi-aws/pull/2701) that adds Java 17 runtime -- just wanted to give a heads up for the team!

Morning all. I'm looking to understand the build process for the azure-native provider. There is a string[] that should be a string in the azure api spec, and this has halted our customer onboarding process. My options seem to be: 1. Downgrade to an old version of the azure-native provider, so that I can downgrade the api for the resource type in question 2. Manually patch the az-native provider - this seems hard 3. Make a PR against the azure spec - this seems to be the easiest option, I just want to make sure I do it in the right place

Hi Pulumi! I’d like to build a provider for Jotform. I found the provider boilerplate, created my own Github repo from it, and I am using the official pulumi docker image (tag 3.80.0) to build it, following the boilerplate instructions. But I’m getting an error from the dotnet build,

/root/.dotnet/sdk/6.0.413/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.GenerateAssemblyInfo.targets(206,5): error MSB4044: The "GetAssemblyVersion" task was not given a value for the required parameter "NuGetVersion". [/data/sdk/dotnet/Pulumi.Jotform.csproj]

Any ideas? I’ll post some more details in a thread in case anyone is curious

Er, somehow fixed it,

pulumictl

was not installed on the docker container

Hi again! When developing a provider, what is the best practice for storing a secret such as an API key that will be used to create/update the resources?

Can someone point me in the direction of how to submit requests for the documentation pages? I spend a lot of time reading the api docs for pulumi-aws and want to help fix things like: https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketlifecycleconfigurationv2/ like where the example has

opts*=*pulumi*.*ResourceOptions(depends_on*=*[versioning]))

even though "versioning" object doesn't exist anywhere in example.. someone could get confused by this.

I see these slight issues a lot and some of the documentation just completely missing.. happy to try and help if its something easy and straight forward.

hey folks - is there a channel to request PR reviews to official pulumi providers? https://github.com/pulumi/pulumi-aws-iam/pull/17