I'm trying to create an EKS cluster with an oidcProvider so I can use the efs-csi driver and have PVCs which work regardless of which AZ the pod which needs them is launched in. There is a helm chart for the driver (which also launches the pods which do the EFS attaching etc.) The instructions for that say we need to follow the instructions here https://docs.aws.amazon.com/eks/latest/userguide/enable-iam-roles-for-service-accounts.html to create the oidc Provider for the cluster. Now those instructions would be a step outside of the flow of the IaC so I would ideally like to write them in pulumi. What they say to do is to look up the cluster.identity.oidc.issuer in the output from

aws eks describe-cluster

command and then use that to create an oidc Provider in AWS with the right url. So given https://www.pulumi.com/registry/packages/aws/api-docs/iam/openidconnectprovider/ I assumed I would be able to get the oidc.issuer url from the stack object created by the eks.cluster call and pass that to the new aws.iam.OpenIdConnectProvider() and do what the aws docs suggest from Pulumi. However cluster.core.oidcProvider.url and cluster.core.oidcProvider.arn stay empty even when the cluster has been created. Perhaps I need to add https://www.pulumi.com/registry/packages/aws/api-docs/eks/identityproviderconfig/ but that also requires the url which the

aws eks describe-cluster

provides, and then I'm back to square one trying to work out how to replicate that in pulumi.

Excited to see what you all have been cooking for tomorrows event partypus

👋 Hi everyone!

I'm working on an AWS EKS cluster am trying to upgrade a helm chart and it's causing me to get a "resource already exists" error since the previous helm chart already had this resource. I'm trying to do a

pulumi import

on the resource so that my current state stops trying to re-apply the CRD but I noticed that there's 0 documentation or examples on how to import a CRD: https://www.pulumi.com/registry/packages/kubernetes/api-docs/apiextensions/customresource/ Are there any examples anywhere for what the format is for doing an import for a CRD that's part of a helm chart? How do I ID it? What's the format for specifying things like the

kind

,

apiVersion

,

namespace

, etc?

When using python, is it possible to have more than one

__main__.py

for one project? eg.:

pulumi up file.py

?

Hi. I have some code that stores API tokens in AWS SSM. During a pulumi update, I issue a call to SSM to get the secret value using

aws.ssm.getParameter

. The response is wrapped like so

pulumi.output(resp).apply(r => r.value)

. I am seeing a weird behavior. I have changed the value of my SSM parameter, and pulumi is still returning the old value. Even weirder is that the old value is only returned on the CI and not when I run on my local machine. Any pointers on what is going on?

Does anyone have any examples of associating a new CloudWatch log group to a Lambda?

Hi, I am having problems all of a sudden with my deployments. I am getting this error. I have updated the cli and

npm install

only to get these errors:

waterledger/waterrecharge-infra/waterrecharge-staging (pulumi:pulumi:Stack)
Found incompatible versions of @pulumi/pulumi. Differing major versions are not supported.
 
  Version 2.25.2 referenced at node_modules/@pulumi/aws/node_modules/@pulumi/pulumi/package.json
 
  Version 3.10.3 referenced at node_modules/@pulumi/pulumi/package.json

and these errors on npm install:

Someone said on reddit that "pulumi is a node app that requires the npm ecosystem", and for him there is a security concern to work with Node/npm in its organization. From my understanding pulumi is written in go, so is a go application not a node app and npm is not required if you don't use npm runtime. Am I wrong and not understanding things correctly?

might be a provider question, might be an Azure question. I'm creating an Azure RoleAssignment - and this has worked before - now I disabled the azure provider, and instantiated my own (but note: I didn't pass it to anything - I just instantiated it). When I create the RoleAssignment, pulumi up complains with: azure-nativeauthorizationRoleAssignment (sreg-role-assignment): error: autorest/azure: Service returned an error. Status=404 Code="ResourceGroupNotFound" Message="Resource group 'x25container6750c5ea' could not be found." The interesting part is that the resource group isn't specified anywhere that I can see in the definition of the RoleAssignment. So I wonder what's going on? Culprits in my mind would be: the provider, maybe the Service Principal rights. How might I debug this further?

Does anyone have sample code showing how to create an (azure) provider, that is then used implicitly with another resources that DO NOT specifically take a provider instance? I've got a c# library of code that constructs stuff, non of it should care about which provider is being used in my opinion - so I definitely do not want to be forced to inject a "provider" arg into every single ctor, that seems like a code smell. I've just noticed now that when I provide a resource with a ComponentResourceOptions instance (for example, to ensure a RG is retained on delete); then my default provider is entirely ignored and the RG doesn't even get created.

Hi ! I use pulumi eks to manage our EKS clusters. We add

ignore_changes=["scalingConfig.desiredSize"]

inside eks.ManagedNodeGroup() to let the autoscaler manage this value, but it doesn’t seems to work. When I run pulumi preview --diff, the config si not ignored :

~ scalingConfig: {
              ~ desiredSize: 4 => 1
            }

Does someone had a similar issue ?

Hi all. Is there any documentation/code available that describes the differences between Pulumi outputs and Pulumi configurations, and when to use what? I've had some discussions with my colleagues on how approach certain things: • We did split our infrastructure in separate Pulumi projects so they can be executed separately. • However, there are some dependencies between these projects: ◦ The first project creates a GCP project ◦ the second projects creates basic networking components (VPC, subnets, etc.). • Higher projects might require some information that was created/updated in other projects. My colleagues propose to use the automation API and to write the information to the dependent projects' configuration so that they will retrieve the updated config during the next run. I see a few downsides here: • As far as I understand the Pulumi config, it resides in a .yaml file so I expect that it should always be read from there and implies that it requires a Git/code commit/push/pull before it's shared. This could create weird syncing issues. • It feels like the opposite way to manage dependencies, as the code delivering the shared data should know it's dependencies My stance would be that you should retrieve provisioning information from the Pulumi project's state, by using the get_ functions, or by reading it from the outputs (which requires you to export it). The purpose of the Pulumi config/secrets is different than the state/outputs but I have trouble putting it into the right words to convince them. Any tips, thoughts, links that can help us to settle the discussion? (I'm also happy to be wrong here :)) (Please let me know if I'd rather need to repost this in a specific channel)

Anyone that has experience SIGKILL when running pulumi up and have any suggestions on how to debug? I have that now in my automation app, and not sure where to start.

When I register for PulumiUp, all I get is an email that says "... We've saved your spot and you can expect to receive your personalised link shortly". This was a long time back, and I haven't got anything yet. How do we join?

After upgrading to Pulumi

3.32.0

, I just got this error:

panic: fatal: An assertion has failed: action must be non empty

goroutine 2009 [running]:
<http://github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.failfast(...)|github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.failfast(...)>
	/private/tmp/pulumi-20220504-79959-1budjvw/sdk/go/common/util/contract/failfast.go:23
<http://github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.Assertf|github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.Assertf>(0x0?, {0x1053aa67e?, 0x140010182d0?}, {0x0?, 0x10537c4e7?, 0x3?})
	/private/tmp/pulumi-20220504-79959-1budjvw/sdk/go/common/util/contract/assert.go:33 +0xe4
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.makeActionProgress({0x106864480|github.com/pulumi/pulumi/pkg/v3/backend/display.makeActionProgress({0x106864480>, 0x1}, {0x0, 0x0})
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:59 +0xa8
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshColumns(0x14001d94780|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshColumns(0x14001d94780>, {0x106864480, 0x1}, {0x140021259f0, 0x5, 0x5}, {0x14000a46060, 0x5, 0x5})
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:437 +0x9c
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshAllRowsIfInTerminal(0x14001d94780)|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshAllRowsIfInTerminal(0x14001d94780)>
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:655 +0x598
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processNormalEvent(0x14001d94780|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processNormalEvent(0x14001d94780>, {{0x105398980?, 0x7?}, {0x105a667e0?, 0x14000849400?}})
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:1134 +0xd48
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processEvents(0x14002d61e40|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processEvents(0x14002d61e40>?, 0x140035a49b0, 0x1400079f6e0)
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:1202 +0xc0
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents.func1()|github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents.func1()>
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:342 +0x34
created by <http://github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents|github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents>
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:341 +0x658

Any ideas why this may happen?

@quiet-wolf-18467 ping

Our new YAML support opens up a LOT of possibilities because so many languages can generate YAML or JSON. Some of them are good ideas, some: not so much: https://twitter.com/briggsl/status/1521886410235473921

I just upgraded to pulumi 3.32.0 and now pulumi is not honouring my

PULUMI_CONFIG_PASSPHRASE_FILE

environment variable. If I load the value into

PULUMI_CONFIG_PASSPHRASE

then it works, but I'd prefer not to do that. Anyone else noticed similar?

👋 Hey folks, is there a recommended way to try and debug performance issues outside of the docs? I'm not sure what changed but my deploys now take nearly 20 minutes for a stack 74 things (including component resources & providers). Using the S3 backend (DO Spaces), docker, vault, postgres, and minio packages, and deploying docker via an ssh tunnel. Currently running the verbose output to a log file, but it's been going for 10 minutes and hasn't shown any completed updates yet

Anyone know where I might find examples or docs related to usging pulumi to interact with vercel?

Aside from running

pulumi stack ls

(or making an equivalent API call), is there any way to determine the active stack for a Pulumi project? I'm not seeing anything in the stack-specific YAML files that would denote active or not.

Does anyone have pulumi APIGatewayV2 (not Crosswalk) recipe guide/cookbook? I'm trying to expand out of Crosswalk and would love to get some ideas on how to implement an API Gateway with multiple routes backed by lambdas.

What are the advantages of Pulumi compared to Terraform?

It is mainly used as Terraform in AWS and Azure environments, but when I coded it in Pulumi Python, it seems inconcise.

In order for Pulumi to be widely used, it must be easy to understand, but the manual is a pity.

Terraform can be used freely by studying with books, manuals, and github without anyone’s help, but Pulumi seems to need help from experts.

Hello everyone. I am using Azure Classic to deploy an Azure Function App which logs traces that help me detect cold starts: see attached screenshot from Azure Portal. However, I do not seem to be able to produce the same information details about cold starts when deploying another Azure Function App not using Azure Classic. Does anyone know how to enable it?

Does anyone know of an existing project for the Pulumi state that diagrams resources similar to https://github.com/cycloidio/inframap for Terraform?