Hey friends, Pulumi Outputs have been rather difficult to work with. I feel like I am either doing something wrong or don't understand how they work. I have spent a day trying to get an output into a useable state. I am using the Okta.User.User resource to load users into okta. I am exporting an output of the Okta User Ids to user later so I can join those users to a group. However the output is coming out with an index and I have no way to turn it into a simple array so that I can load it into the Okta.GroupMembership resource that only takes a list. Output:

export const devopsUserIds = pulumi.output(devopsUsers).apply(userlist => userlist.map((user: { id: any }) => user.id))

This produces

+ devopsUserIds       : [

+     [0]: "00uyn0nldHI1SFLwasdfasd"

+     [1]: "00uyq0314ehGvU12121"

]

Somehow I am unable to extract it to something more like this

devopsUserIds['00uyn0nldHI1SFLwasdfasd', '00uyq0314ehGvU12121']

Hi folks! I have a (potentially stupid) question, but how do you keep parts of the provider configuration (or inputs) outside of the Pulumi state? The use case is that both the CI and local developer machines can manage the same set of infrastructure, but the connectivity to the provider from local machines differs from the machines in the CI. If I apply the infrastructure using my local machine then the CI cannot refresh the resources, because it tries to use the provider configuration inside of the state file. I tried to override the configuration in the CI using environment variables and

pulumi config set

but both approach don’t seem to work. Let me know if I’m missing something obvious 😅

Is there a way to merge outputs into one using typescript? I have several outputs that are arrays that I would like to be able to merge all of the values into a single flat array. Since these are outputs things like concat or flat do not work. so I have an out put called foo:

[ 'bar', 'cat'] and one called bar: ['abc,' '123]. that I would like to make into flat: ['bar", "cat", "abc", "123"]

I'm specifically looking for the code security and analysis section of the git-hub pulumi api https://www.pulumi.com/registry/packages/github/api-docs/ {{ Dependabot }}. I have a technical requirement where as this would be helpful?

Is there a way from within python / while running pulumi to access all the objects of a stack? Concrete example of what I am trying to do - I create some subnets, a few weeks later I want to add a subnet, I want to read the objects that were created before and make sure my new subnet is at the end of the previous. Instead of specifying every cidr I want to just say, make 5 /21 and have it math it out itself but I need to be able to see what was created before which in theory should all be in the state? (Using the pulumi saas for state if that makes any difference)

is there an ETA when this PR https://github.com/pulumi/pulumi-google-native/pull/410 will be merged and released ? it contains support for httproute etc.

Got a weird error when trying to used my crd generated with crd2pulumi. Anyone has already that kind of a problem?

TypeError: Invalid Version:
        at new SemVer (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:332:11)
        at compare (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:647:10)
        at Function.eq (/builds/${PROJECT}/pulumi/node_modules/semver/semver.js:693:10)
        at sameVersion (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:703:57)
        at register (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:718:17)
        at Object.registerResourcePackage (/builds/${PROJECT}/pulumi/node_modules/@pulumi/runtime/rpc.ts:780:5)
        at Object.<anonymous> (/builds/${PROJECT}/pulumi/node_modules/@ticketmaster/pipelog-crds/build/index.js:25:16)
        at Module._compile (node:internal/modules/cjs/loader:1103:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
        at Module.load (node:internal/modules/cjs/loader:981:32)

👋 Hi everyone! got this error trying to run

pulumi up

error: Program failed with an unhandled exception:
error: Traceback (most recent call last):
    File "~/.pulumi/bin/pulumi-language-python-exec", line 107, in <module>
    loop.run_until_complete(coro)
    File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
    File "~/project/venv/lib/python3.8/site-packages/pulumi/runtime/stack.py", line 126, in run_in_stack
    await run_pulumi_func(lambda: Stack(func))
    File "~/project/venv/lib/python3.8/site-packages/pulumi/runtime/stack.py", line 51, in run_pulumi_func
    await wait_for_rpcs()
    File "~/project/venv/lib/python3.8/site-packages/pulumi/runtime/stack.py", line 110, in wait_for_rpcs
    raise exception
    File "~/project/venv/lib/python3.8/site-packages/pulumi/output.py", line 169, in run
    value = await self._future
    File "~/project/venv/lib/python3.8/site-packages/pulumi/output.py", line 169, in run
    value = await self._future
    File "~/project/venv/lib/python3.8/site-packages/pulumi/output.py", line 194, in run
    transformed: Input[U] = func(value)
    File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/image.py", line 254, in <lambda>
    lambda args: get_image_data(_ImageArgs(*args))
    File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/image.py", line 231, in get_image_data
    unique_target_name = build_and_push_image(
    File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 243, in build_and_push_image
    build_result = build_image(base_image_name, path_or_build, log_resource, cache_from)
    File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 437, in build_image
    docker_build(image_name, build, log_resource, cache_from)
    File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 491, in docker_build
    return run_command_that_must_succeed("docker", build_args, log_resource, env=build.env)
    File "~/project/venv/lib/python3.8/site-packages/pulumi_docker/docker.py", line 608, in run_command_that_must_succeed
    raise ResourceError(
pulumi_docker.docker.ResourceError: 'docker build -t backend:dev ~/project/app/backend' failed with exit code 1
error: an unhandled error occurred: Program exited with non-zero exit code: 1

Hi guys, quick question. i have a multistep pulumi stack, where i initially create some aws kms keys and iam user / accesskey. in the 2nd. step i create some infrastructure where i need to inject this information as a string (since this is what the software recognizes). I'm unable to find a consistent method for extracting the initial resources information, as they are being created asynchronously is there a simple way in python - to await resources being created - before i fetch resource information to inject into the next phase of my stack creation ?

Morning all, has anyone used pulumi with aws codecommit instead of github? As a company we use codecommit as our standard repository and wanted to hear others experiences, mainly about importing packages hosted in codecommit.

👉 https://github.com/pulumi/pulumi-docker-containers/compare/main...DusanDimitric:patch-1 Hey guys I made a PR to upgrade Node.js to the current LTS version (16). This is very useful for our project, and it would be a nice thing to have in the next version of the Pulumi Docker Image. Thanks 🙏

Hi, I added the Pulumi GitHub App to my organisation and also provided access to the

.git

folder to Pulumi in GitHub Actions. Still I do not get a comment by the GitHub App. What could be the problem? I have a setup that does reproducible builds in containers, so there is no implicit access to the environment variables in github actions. Which ones do I have to forward?

Good day. Does anyone use https://www.pulumi.com/registry/packages/yandex/? I don't understand how you can assign multiple roles to a service account.

Hello, I'm struggling to get Values into my helm charts. I'm following the example here: https://www.pulumi.com/registry/packages/kubernetes/api-docs/helm/v3/chart/#set-chart-values My code looks like:

_, err = helm.NewChart(ctx, "influx", helm.ChartArgs{
			Repo: pulumi.String("influxdata"),
			Chart: pulumi.String("influxdb2"),
			Values: pulumi.Map{
				"storageClass": pulumi.String("efs-stor"),
			},
		},
		pulumi.ProviderMap(map[string]pulumi.ProviderResource{
			"kubernetes": eksProvider,
		}),)
		if err != nil {
			return err
		}

But when I run pulumi up, there is no StorageClassName set in the PVC spec:

+ kubernetes:core/v1:PersistentVolumeClaim: (create)
            [urn=urn:pulumi:influx-test::influx::kubernetes:<http://helm.sh/v3:Chart$kubernetes:core/v1:PersistentVolumeClaim::influx-influxdb2|helm.sh/v3:Chart$kubernetes:core/v1:PersistentVolumeClaim::influx-influxdb2>]
            [provider=urn:pulumi:influx-test::influx::pulumi:providers:kubernetes::eksprov::04da6b54-80e4-46f7-96ec-b56ff0331ba9]
            apiVersion: "v1"
            kind      : "PersistentVolumeClaim"
            metadata  : {
                annotations: {
                    <http://helm.sh/resource-policy|helm.sh/resource-policy>: "keep"
                }
                labels     : {
                    <http://app.kubernetes.io/instance|app.kubernetes.io/instance>  : "influx"
                    <http://app.kubernetes.io/managed-by|app.kubernetes.io/managed-by>: "pulumi"
                    <http://app.kubernetes.io/name|app.kubernetes.io/name>      : "influxdb2"
                    <http://app.kubernetes.io/version|app.kubernetes.io/version>   : "2.1.1"
                    <http://helm.sh/chart|helm.sh/chart>               : "influxdb2-2.0.10"
                }
                name       : "influx-influxdb2"
                namespace  : "default"
            }
            spec      : {
                accessModes: [
                    [0]: "ReadWriteOnce"
                ]
                resources  : {
                    requests: {
                        storage: "50Gi"
                    }
                }
            }

Can anyone see what I'm doing wrong? Or is this the wrong channel for this? Should I go and speak to influx or helm?

Hi, I recently started running into this error -

error: could not load plugin for aws provider 'urn:pulumi:plane-2::launchpad::pulumi:providers:aws::aws-provider': could not read plugin [/nix/store/d26ir9idflpfn2rb9x4w8z4xvhz9mqah-pulumi-3.26.1/bin/pulumi-resource-aws] stdout: EOF

Hi guys, I'm going to import some existing resources with

pulumi import [type] [name] [id]

command. How can I get

type

for my resources?

Hi, I'm trying to import some existing GCP resources to Pulumi. Some of them I have imported successfully, but still struggling with others. For instance, I'm trying to import BucketIAMMember using the command:

pulumi import gcp:storage/bucketIAMMember:BucketIAMMember disk1_iam_member "disk1--bucket--name roles/storage.Admin user:user1@example.com"

And I get this error message:

error: Preview failed: importing disk1--bucket--name roles/storage.Admin user:ab@playa.tech: Cannot find binding for "storage bucket \"b/disk1--data--sandbox--playa-tech\"" with role "roles/storage.Admin", member "user:user1@example.com", and condition title ""

So, it says that no such binding for this user. For me, this message looks odd because I'm pretty sure

user1

has a Storage Admin role for bucket

disk1--bucket--name

. I have just checked this in GCP console. Any ideas what I'm doing wrong? Tnx guys in advance

UPD: the doc about importing IAM binding: https://www.pulumi.com/registry/packages/gcp/api-docs/storage/bucketiammember/#import

Hi, i'm using pulumi to deploy k8s yaml file, when rerun pulumi, it will report the errors blow, is it normal or how to escape it?

kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-webhook:subjectaccessreviews):
    error: resource cert-manager-webhook:subjectaccessreviews was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-webhook:subjectaccessreviews" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:RoleBinding|rbac.authorization.k8s.io/v1:RoleBinding> (cert-manager/cert-manager-webhook:dynamic-serving):
    error: resource cert-manager/cert-manager-webhook:dynamic-serving was not successfully created by the Kubernetes API server : <http://rolebindings.rbac.authorization.k8s.io|rolebindings.rbac.authorization.k8s.io> "cert-manager-webhook:dynamic-serving" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-view):
    error: resource cert-manager-view was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-view" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-ingress-shim):
    error: resource cert-manager-controller-ingress-shim was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-ingress-shim" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-orders):
    error: resource cert-manager-controller-orders was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-orders" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-issuers):
    error: resource cert-manager-controller-issuers was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-issuers" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:RoleBinding|rbac.authorization.k8s.io/v1:RoleBinding> (kube-system/cert-manager:leaderelection):
    error: resource kube-system/cert-manager:leaderelection was not successfully created by the Kubernetes API server : <http://rolebindings.rbac.authorization.k8s.io|rolebindings.rbac.authorization.k8s.io> "cert-manager:leaderelection" already exists

  kubernetes:apps/v1:Deployment (cert-manager/cert-manager):
    error: resource cert-manager/cert-manager was not successfully created by the Kubernetes API server : deployments.apps "cert-manager" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-clusterissuers):
    error: resource cert-manager-controller-clusterissuers was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-clusterissuers" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-challenges):
    error: resource cert-manager-controller-challenges was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-challenges" already exists

  kubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> (<http://clusterissuers.cert-manager.io|clusterissuers.cert-manager.io>):
    error: resource <http://clusterissuers.cert-manager.io|clusterissuers.cert-manager.io> was not successfully created by the Kubernetes API server : <http://customresourcedefinitions.apiextensions.k8s.io|customresourcedefinitions.apiextensions.k8s.io> "<http://clusterissuers.cert-manager.io|clusterissuers.cert-manager.io>" already exists

  kubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> (<http://certificaterequests.cert-manager.io|certificaterequests.cert-manager.io>):
    error: resource <http://certificaterequests.cert-manager.io|certificaterequests.cert-manager.io> was not successfully created by the Kubernetes API server : <http://customresourcedefinitions.apiextensions.k8s.io|customresourcedefinitions.apiextensions.k8s.io> "<http://certificaterequests.cert-manager.io|certificaterequests.cert-manager.io>" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-certificatesigningrequests):
    error: resource cert-manager-controller-certificatesigningrequests was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-certificatesigningrequests" already exists

  kubernetes:<http://admissionregistration.k8s.io/v1:MutatingWebhookConfiguration|admissionregistration.k8s.io/v1:MutatingWebhookConfiguration> (cert-manager-webhook):
    error: resource cert-manager-webhook was not successfully created by the Kubernetes API server : <http://mutatingwebhookconfigurations.admissionregistration.k8s.io|mutatingwebhookconfigurations.admissionregistration.k8s.io> "cert-manager-webhook" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-certificates):
    error: resource cert-manager-controller-certificates was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-certificates" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-controller-challenges):
    error: resource cert-manager-controller-challenges was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-controller-challenges" already exists

  kubernetes:<http://apiextensions.k8s.io/v1:CustomResourceDefinition|apiextensions.k8s.io/v1:CustomResourceDefinition> (<http://orders.acme.cert-manager.io|orders.acme.cert-manager.io>):
    error: resource <http://orders.acme.cert-manager.io|orders.acme.cert-manager.io> was not successfully created by the Kubernetes API server : <http://customresourcedefinitions.apiextensions.k8s.io|customresourcedefinitions.apiextensions.k8s.io> "<http://orders.acme.cert-manager.io|orders.acme.cert-manager.io>" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRole|rbac.authorization.k8s.io/v1:ClusterRole> (cert-manager-edit):
    error: resource cert-manager-edit was not successfully created by the Kubernetes API server : <http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cert-manager-edit" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-certificates):
    error: resource cert-manager-controller-certificates was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-certificates" already exists

  kubernetes:apps/v1:Deployment (cert-manager/cert-manager-webhook):
    error: resource cert-manager/cert-manager-webhook was not successfully created by the Kubernetes API server : deployments.apps "cert-manager-webhook" already exists

  kubernetes:<http://rbac.authorization.k8s.io/v1:ClusterRoleBinding|rbac.authorization.k8s.io/v1:ClusterRoleBinding> (cert-manager-controller-orders):
    error: resource cert-manager-controller-orders was not successfully created by the Kubernetes API server : <http://clusterrolebindings.rbac.authorization.k8s.io|clusterrolebindings.rbac.authorization.k8s.io> "cert-manager-controller-orders" already exists

Hello, after creating a stack with automation api (PYTHON), some values are not available right away. ie im creating a stack with public IP in azure, but after the create there is no output containing the IP yet, only on the second "create" its showing up. Is there another way without running "create" again to fetch all outputs?

Hello, while using PYTHON is it possible to determine the stage of code execution (e.g. preview or update) by using SDK?

I need to make a change to an AWS LogGroup, that might exist and might not exist yet. How do you go about that? * If I use LogGroup(...), then it fails, if the group already exists * If I use LogGroup(..., opts=pulumi.ResourceOptions(import_='...')), then it fails, if the group does not exist yet Are there any create-if-needed option? Or a way to test if a group already exists? (I can live with the small timing-hole..., as I can "just" re-run the up command in case of errors)

Hello! I'm using pulumi typescript and I need to access a configuration cross stacks. I already use StackReferences in my project but I noticed that the configs are not accessible cross stacks. Is there a way to access the configs

pulumi.Config

cross stacks? If not, is there an option to go around it in a clean way?

Hey guys, I have an issue with Helm release but I think it’s a broader issue with pulumi. I’m trying to inject an Output<string> to the helm release values (which I already done in a different release and it worked great), but for some reason it fails my pulumi runtime with

panic: fatal: An assertion has failed

- in addition, there’s nothing in the values.yaml file that relates to these values. Here’s a screenshot of the code segment:

Hey! I’m having trouble with creating two pulumi projects. One has a stack “general” and the other has a stack “staging”. Running

pulumi stack ls

shows both stacks when I thought it should only show the stacks from the current project by default. The -p option does not change anything. Using

pulumi stack select theoneintheotherdirectory

creates a new yaml file… Is that expected?

Does anyone know if there's a way to access and modify the attributes of a default provider object? Failing that, has anyone worked out a way to automate replacing the provider object in an existing stack deployment to avoid having to recreate all of the resources?

hi 👋 I need some help. I have a GKE Cluster which is protected. After doing a

pulumi refresh

, every subsequent

pulumi preview

fails because the diff wants to delete-and-recreate the cluster, so it fails because the cluster is protected. However, pulumi doesn’t tell me why it wants to recreate the cluster. There’s no “details” to observe because the preview fails. So I have no idea how to edit the state or the code to bring everything back in sync. Is there a way to find out that information out of pulumi?

hi, is there a way to get stack references during runtime, i.e., suppose I want to know the hostname of some instance produced by pulumi in downstream service code, could I reference the typical "infra" pulumi program somehow, and get that value? other example would be like the name of a secret that gets pulled in runtime. the secret is created via pulumi. then the secrets SDK makes a call to the service to actually get the value

has anyone used the github provider

pull_request

resource? https://www.pulumi.com/registry/packages/github/api-docs/repositorypullrequest/ https://registry.terraform.io/providers/integrations/github/latest/docs/resources/repository_pull_request This one seems a bit weird. Like you’d have to constantly be adding resources to a stack (new pull requests), or you need to automatically “forget” the resource, so you can recreate it? (

pulumi state rm

) I’m curious if anyone has used this before, and how they are using it.