Has anyone had issues with GCP IamMembers and cloud run services ? I’m literally just trying to give allUsers the ability to invoke the service and not having any luck

Hi everyone! How can I define a dependency between a resource and a getter in my code? In my case, I have a PagerDuty ServiceIntegration resource created, and right after that, I need to call getServiceIntegration. I do that because right after the resource is created, a key is generated on the service provider and I'd like to retrieve that. Somehow it's not a part of the resource outputs. Of course, the

pulumi preview

fails because it tries to invoke the getter even if the resource doesn't exist yet. I can't use the

depens_on

argument as

ResourceOptions

has because

InvokeOptios

doesn't support that. Many thanks.

Hi, I am trying to deploy resources on Microsoft Azure with code I used 4 months ago. I have updated to pulumi 3.24.1 with the python sdk versions: pulumi 3.24.1 pulumi-azure 4.37.0 pulumi-azure-native 1.56.0 When running 'pulumi preview' I am getting the following error: pulumi preview Previewing update (test) View Live: https://app.pulumi.com/epiic/appsvcs/test/previews/704d3482-9297-42f3-b696-a0867edbbd1e Type Name Plan Info + pulumipulumiStack appsvcs-test create 3 errors + ├─ azurecoreResourceGroup epiic-appsvcs-rg-test create + ├─ azurestorageAccount eassatest create + ├─ azureappservicePlan eas-asp-test create + └─ azureappinsightsInsights eas-ai-test create Diagnostics: pulumipulumiStack (appsvcs-test): error: Program failed with an unhandled exception: error: Traceback (most recent call last): File "/opt/pulumi/pulumi-language-python-exec", line 107, in <module> loop.run_until_complete(coro) File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete return future.result() File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/stack.py", line 126, in run_in_stack await run_pulumi_func(lambda: Stack(func)) File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/stack.py", line 51, in run_pulumi_func await wait_for_rpcs() File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/stack.py", line 110, in wait_for_rpcs raise exception File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc_manager.py", line 68, in rpc_wrapper result = await rpc File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/output.py", line 98, in is_value_known return await is_known and not contains_unknowns(await future) File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/output.py", line 98, in is_value_known return await is_known and not contains_unknowns(await future) File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/output.py", line 98, in is_value_known return await is_known and not contains_unknowns(await future) [Previous line repeated 47 more times] File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/resource.py", line 514, in do_register resolver = await prepare_resource(res, ty, custom, remote, props, opts, typ) File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/resource.py", line 124, in prepare_resource serialized_props = await rpc.serialize_properties( File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc.py", line 172, in serialize_properties result = await serialize_property( File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc.py", line 389, in serialize_property return { File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc.py", line 390, in <dictcomp> k: await serialize_property( File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc.py", line 228, in serialize_property await serialize_property( File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc.py", line 389, in serialize_property return { File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc.py", line 390, in <dictcomp> k: await serialize_property( File "/home/rlrobert/gitlab/dataingress/pulumi-appsvcs/.venv/lib/python3.9/site-packages/pulumi/runtime/rpc.py", line 450, in serialize_property raise ValueError(f"unexpected input of type {type(value).name}") ValueError: unexpected input of type tuple error: an unhandled error occurred: Program exited with non-zero exit code: 1 I have no idea where to start debugging this. Any ideas/help would be appreciated.

I see that https://github.com/pulumi/pulumi-aws/pull/1054 has recently landed (👏), is there any way to do the same thing (build a

ContainerDefinition

with embedded

Input

’s rather than building a big JSON string) for the AWS classic provider? It’s defined as

pulumi.Input[str]

in

TaskDefinitionArgs

which seems to force us to serialize it as a string (after using all/apply/concat on the

Output

’s as usual). I assume this is an upstream (Terraform) restriction, yet it works for

awsx

somehow.

Hello @echoing-match-29901 If I want some custom code to be executed based on whether it is

pulumi up/destroy/preview/etc..

is there a variable which I could use inside my `python`programs? something like

pulumi.cli.arg[1]

or so?

Where is the pulumi plugin configuration stored? We have installed a new plugin which crashes terraform bridge, so we would like to remove it 🙂 We've removed all the references in the project and in

~/.pulumi

.

pulumi plugin ls -p

doesn't show that plugin in use. However, when we try to run pulumi up, it is still downloaded.

when creating a

docker.Image()

, how can I specify multiple tags? say ":1.0" and ":latest"? what I currently do to work around is to create two images, but that's a) annoying because they need to have different resource-names and b) leads to the creation of two resources where I logically have only one with 2 tags.

I ran into an interesting issue yesterday while importing a resource, and wanted to see if it was expected. Our stack uses an explicit AWS provider (so not the default one, which we’ve disabled since 3.23.0), and I need to import an RDS cluster. I ran the following command:

pulumi import "aws:rds/cluster:Cluster" my-rds-cluster "rds-cluster-name"

and I got an error saying the RDS cluster did not exist. After a while, I figured out it was just using the implicit AWS credentials I have on my machine, which are going to our main account (which doesn’t have this resource in it), as opposed to our prod account. So I created a profile to our prod account (with assume role) and did:

AWS_PROFILE=prod-account pulumi import "aws:rds/cluster:Cluster" my-rds-cluster "rds-cluster-name"

and then it “successfully” found and imported the cluster. I put it in quotes because it basically imported it under a new provider (I think the default one), which then conflicted with what I had in code so it wanted to re-create it. I manually exported the stack JSON, edited the provider reference, re-imported it and it was happy. With that in mind, my questions: 1. Is it expected that I would need to do something like the

AWS_PROFILE=prod-account

above? Should it not select the provider I have defined in my stack (or ask me which one I want to use)? 2. Is it expected that it imported it into the stack state with a brand new provider that didn’t exist before?

Hey folks! As you may know, we have a Github Discussions forum in addition to this community Slack. We encourage you to use the Github Discussions forums as well. We are using Discussions to provide a central location as a knowledge base and for users and other community members to help and connect with each other. We hope that you: - As questions that you might have related to Pulumi - Engage with other community members - Share what you are building with Pulumi! All forum posts are subject to the Code of Conduct. Use the Pulumi Community Slack for questions/issues where you want to collaborate in real time. However, moderators of the Community Slack may encourage you to move the discussion to Github Discussions if it seems like an area that will be helpful for others in the future (since Slack is not searchable and the content disappears over time). We also encourage you to use Github Discussions as we can much more easily connect these discussions (vs Slack) to Github Issues. If you want to collaborate with other people on your code, Slack is a great place to work through those challenges! If you are looking to find out about success patterns, architectural references, or if you’re not sure if something is a bug, GitHub Discussions is your place to go!

hey folks someone has some examples of how to use spot instances with eks? I am finding the docs to be a little confusing

we're trying to build a logic app, what does it want for the connector names? trying to use office 365 connection for our trigger and a create blob v2 for the for each

Is there a guide for creating and deploying containers to gcp compute instances? I tried using the same image i was deploying to cloudrun but i get an error that the image cannot be found

Hello Folks, could I possibly add post-deployment code to update database after a stack is successfully deployed? Thanks!

hey everyone. I am trying to connect to a private docker registry. But it seems that the password or username is not passed correctly. While not using the provider, it throws 401, and using the provider it changes to 403. That leads to the conclusion that the provider is indeed used, and tries to login. But is not able to login. I can use the same credentials with

docker login

and have it working in the terminal. Am I missing a setup step? Or is this just a bug?

new docker.Provider(
  `github-docker-provider`,
  {
    registryAuth: [
      {
        address: '<http://ghcr.io|ghcr.io>',
        username: 'XXX',
        password: 'XXX',
      },
    ],
  }
)

error: Running program ‘/Users/xxx/Documents/projects/xxx’ failed with an unhandled exception: Error: invocation of dockerindex/getRegistryImagegetRegistryImage returned an error: invoking dockerindex/getRegistryImagegetRegistryImage: 1 error occurred: * Got error when attempting to fetch image version xxx/xxx:latest from registry: Got bad response from registry: 403 Forbidden

hey guys, anyone knows how to propagate `Name`tag to my ec2 instances with an eks managed group? I tried

tags

,

cloudFormationTags

and

autoScalingGrouptTags

, but none of them worked

Hello, Is there a way to scan docker image before deploying it using Pulumi

hi @echoing-match-29901 - I want to achieve as follows in my stack which is monitored by k8s operator - When my RDS instance gets created successfully , i want to pipe the outputs to a k8s secret. Problem - The secret is getting created even before the RDS instance and hence it has garbage values. How to solve this ? I heard there is an DAG mechanism in-built which takes care of creating things in a proper order, but in my case that seems to be not woring

Hi @echoing-match-29901 is there an issue with the registry?

$ pulumi plugin install resource terraform v5.2.0
[resource plugin terraform-5.2.0] installing
error: [resource plugin terraform-5.2.0] downloading from : 403 HTTP error fetching plugin from <https://get.pulumi.com/releases/plugins/pulumi-resource-terraform-v5.2.0-darwin-arm64.tar.gz>

And in the browser for the same URL:

Or is it just me?

Hi @echoing-match-29901 - I've fell in love with Pulumi but I'd also like to use Stax.io as well for governance controls. Stax.io has packages which are based on CloudFormation templates. Can I use Pulumi to generate Terraform creation/update/deletion scripts managed by an external stack? I'm based in AU and doing a special purpose POC and have contacts internally at Stax.io in AU who I can engage to help solve 'wicked problems' which could include interop between the platforms

Anybody know the way to set up an outlook connector through pulumi? we can deploy the logic app up but the connector is not recognized... using whats in the template does not work

Anyone had this happen before? When modifying lambda code (created by

awsx.apigateway.API

) this happens: (I’ve played with modifying Lambda code like this yesterday and it worked without problems 😕 - just plain old JavaScript)

Hola everyone - Just started exploring Pulumi - where can i find more info and buzz about this ? Night young today and took a day off tomorrow - so want atleast scratch the first layer of this today

Hello all, before send an email to support, would anyone know why some of my typescript-aws project are created with a package(-lock).json and node_module folder and some just don't ?

and very "funny" part is, the ones that do have the package.json and node_module folder, they fail if I'm trying to register the autotag feature

if I already have a cloud setup in azure can I import a specific resource-group and all it's VMs and the subnets and the network security groups and the bastion host into pulumi using the pulumi cli import cmd? I cannot find any examples on doing that importing from azure?

I created a PR to allow disabling typechecking in typescript projects: https://github.com/pulumi/pulumi/pull/8981, defaulting to the current behavior of typechecking turned on. I think that is the only remaining change my company would need to stop using our fork off of 3.14.0: https://github.com/transcend-io/pulumi 😄

Hi folks, so we have updated our Heroku provider to Pulumi 3 - https://github.com/moneymeets/pulumi-heroku - but we actually would very much like to get it adopted by the Pulumi community. My colleague @wide-cat-87818 has talked to @broad-dog-22463 in the past, but in the end it somehow didn't happen. Maybe @white-balloon-205 would have an idea? Is there really no interest in Heroku at Pulumi? We're kind of struggling to keep our provider up to date due to the lack of manpower... 😕 P.S. Of course, if a great Python / Pulumi / AWS engineer is interested in joining us... 😉

Does anyone know how to stop Pulumi from collecting git information? I was quite surprised to find a lot of git info under the environment tab in the Pulumi UI. Not sure I like that Pulumi collects this info. at all.