Hello there, could someone help me check on import resource currently. I’m trying to import Cloudflare Tunnel with https://www.pulumi.com/registry/packages/cloudflare/api-docs/tunnel/#import but input

secret

is required and I didn’t find a way to add secret value during import,

Hello there, Does Pulumi automatically create logging policies for Lambda functions created by it (specifically aws.lambda.CallbackFunction), Is there documentation available regarding to that?

Is there any documentation that I can reference for hosting a private resource provider? I noted that

plugin install

has ability to accept a

--server

flag but how does that work? Also, I would prefer that

pulumi up

and

pulumi preview

would download the required plugins but unclear if it is possible if I have a mixture of these private resource providers and the public ones like aws. Thanks in advance.

Hello Gurus, I am looking to deploy resource in two different account and using providers. This is my code, how can I use multiple providers to create bucket in two different accounts? const devProvider = new aws.Provider("devProvider", { profile: "dev", region: "us-east-1" }); const prodProvider = new aws.Provider("prodProvider", { profile: "prod", region: "us-west-2" }); . const xyzBucket = new aws.s3.Bucket(

xyz-bucket

, { }, { provider: [devProvider, prodProvider], //Error here });

Hi there! I am developing Dynamic Resource Provider and faced with a strange trouble. Case: • Make intentionality configuration drift (update resource manually - NOT with Pulumi) • Run pipeline with

--refresh

option (method read is implemented) and expect that Pulumi to re-configure resource and eliminate drift • Language: Python • Pulumi version: 3.56.0 Details: • I run

pulumi preview --diff -r

• Pulumi shows that manually changed resource should be updated:

pulumi-python:dynamic:Resource: (update)

But there are no details in diff what are going to be substituted 😬

~ pulumi-python:dynamic:Resource: (update)
        filed_1          : "aaaa"
        filed_2              : "bbbb"
        filed_3           : [
            [0]: "cccc"
        ]
Resources:              
    ~ 1 to update
    X unchanged

• As I run

pulumi up -y -r

, Pulumi re-configures resource and eliminates drift (pulumi up works good but pulumi preview doesn't show details) • I checked preview json and couldn't find

diffReasons

for this resource. However, other resources that are supposed to be updated have this field 😬 code example:

def read(self, id_, args):
    ...
        value_1 = read_field_1()
        value_2 = read_field_2()
        value_3 = read_field_3()

        return ReadResult(id_, outs={'filed_1': value_1,
                                     'filed_2': value_2,
                                     'filed_3': value_3]
                                     })

    def diff(self, id, _olds, _news):
        return DiffResult(
            changes=_olds != _news,
            replaces=[],
            stables=None,
            delete_before_replace=True
        )

I would be grateful if someone help me with this issue.

hello folks 👋 I'm looking for some guidance on how to build a multi arch docker image. Would anyone have some pointers to the right doc ?

Hello Pulumians, Codefresh is running a March Madness. In round 1 of their poll, we are up against Terraform in the IaC tool category. If you like to express your preference for Pulumi, have a vote: • Twitter • LinkedIn (FYI we aren't doing so great in the LinkedIn poll at the moment) Thank you all for the small gesture!

hi there, I encountered a rare situation in which all the Datadog API call returns 403 forbidden during pulumi preview. The datadog app key and api key have bee the same and it's been working all these while until yesterday where things started to get broken :

[38;5;1merror: [0m[0mPreview failed: refreshing urn:pulumi:staging::spinoff::datadog:index/user:User::us5-standard-user-user1: 1 error occurred:
	* error getting user from <https://us5.datadoghq.com/api/v2/users/xxxxxxxxxxxxxxxxx>: 403 Forbidden: {"errors":["Forbidden"]}

Datadog support has requested the headers that was sent from Pulumi to Datadog, is there a way to retrieve this information? TIA

Hello, we’re using Pulumi CLI + self-hosted state (i.e. we are not self-hosting the platform components). Are stack references possible, in this case? It seems that the concept of “organization” doesn’t map onto this scenario, is that correct? Thanks.

Hello there, I'm getting a type mismatch error when defining the key_schema(with only the hashkey) for dynamodb using the aws_native provider ,

import pulumi_aws_native as aws_native

aws_native.dynamodb.Table(
       table_id,
       table_name="example",
       billing_mode="PROVISIONED",
       opts=pulumi.ResourceOptions(protect=True),
       attribute_definitions=[
           aws_native.dynamodb.TableAttributeDefinitionArgs(
               attribute_name="PrimaryKey",
               attribute_type="S",
            )
        ],
        provisioned_throughput=aws_native.dynamodb.TableProvisionedThroughputArgs(
            read_capacity_units=100,  
            write_capacity_units=1,
        ),
        key_schema=[
            aws_native.dynamodb.TableKeySchemaArgs(
                attribute_name="PrimaryKey",
                key_type="HASH",
             ),
        ],
)

And here is the error:

raise AssertionError(f"Unexpected type. Expected 'list' got '{typ}'")
AssertionError: Unexpected type. Expected 'list' got 'typing.Union[typing.Sequence[typing.Union[pulumi_aws_native.dynamodb._inputs.TableKeySchemaArgs, typing.Awaitable[pulumi_aws_native.dynamodb._inputs.TableKeySchemaArgs], pulumi.output.Output[NoneType]]], typing.Any, typing.Awaitable[typing.Union[typing.Sequence[typing.Union[pulumi_aws_native.dynamodb._inputs.TableKeySchemaArgs, typing.Awaitable[pulumi_aws_native.dynamodb._inputs.TableKeySchemaArgs], pulumi.output.Output[NoneType]]], typing.Any]], pulumi.output.Output[NoneType]]'

More info here. Appreciate any guidance, Thanks !

@echoing-dinner-19531 if you don’t mind, can you help me check this one? when I run

pulumi up

for Tunnel Config, it alway show

diff: ~config

Previewing update (<redacted>):
     Type                              Name                                          Plan       Info
     pulumi:pulumi:Stack               <redacted>             
 ~   └─ cloudflare:index:TunnelConfig  test_tunnel-TunnelConfig                      update     [diff: ~config]

click on details show

~ cloudflare:index/tunnelConfig:TunnelConfig: (update)
        [id=<redacted> ]
        [urn=urn:pulumi:<redacted>::pulum::cloudflare:index/tunnelConfig:TunnelConfig::test_tunnel-TunnelConfig]
        [provider=urn:<redacted>::pulum::pulumi:providers:cloudflare::default_5_0_0::1523d07a-58d4-404d-94ac-5494f67a769c]
      ~ config: {
          + warpRouting: {
              + enabled   : true
            }
        }

when I run

pulumi stack export

and search for urn

"urn": "urn:pulumi:<redacted>::pulum::cloudflare:index/tunnelConfig:TunnelConfig::test_tunnel-TunnelConfig"

, at

inputs

section, the value of

warpRouting

is

"warpRouting": {
                            "__defaults": [],
                            "enabled": true
                        }

but at

outputs

section, it’s

"warpRouting": null

so I guess it cause problem of diff when run

pulumi up/preview

Hello Team, I would like to ask you for assistance, I have installed chaos-mash via HELM, but I want to configure ingress to get chaos-mesh-dashboard accessible via ingress. Not sure how to proceed, do I need to use kubernetes-ingress-nginx.IngressController resource ? In my case I am using nginx ingress installed via HELM also. Thank you in advance. Ned.

const chaosMesh = new k8s.helm.v3.Release(
    "chaostest",
    {
      name: "chaos-mesh",
      chart: "chaos-mesh",
      namespace: "chaos-mesh",
      version: "2.5.1",
      repositoryOpts: {
        repo: "<https://charts.chaos-mesh.org>",
      },
      values: {
        controllerManager: {
          enableFilterNamespace: true,
        },
        chaosDaemon: {
          runtime: "containerd",
          socketPath: "/run/containerd/containerd.sock",
        },
        annotations: {
          "<http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>": "nginx",
        },
      },
    },
    { dependsOn: [k8sCluster] }
  );

Hi, quick question, if you are creating a lambda and the lambda requires you to use a resource provisioned by pulumi (e.g read from an s3 bucket) is there anyway of keeping this code separated from pulumi or do you now have to mix your lambda and infrastructure code? I wanted to keep them separate and upload zips of the lambdas to aws via pulumi but I now don't see how this would work as I would presumably be importing pulumi in a lambda layer but would not be able to run it as it would not be logged in on the aws lambda layer? Super confused

Hi Everyone, I am glad to join this amazing pulumi community and I am new here 🙂 , I am here to request some assistance on some pulumi related questions please, shown below 👇 We are using pulumi typescript to automate our AWS related infrastructure/services, & have been using to automate AWS EFS (Elastic FileSystem) creation along with an EFS '*replica*' created on a given AWS region. Highly appreciate if somebody give me a hand to assist me on getting the following working please? • EFS replica created isn't created with any "Name" and it doesn't have any AWS tags (Name is blank because the "Name" key value pair is empty), it appears to be having something like below. • The reason is we noticed that https://github.com/pulumi/pulumi-aws/blob/master/sdk/nodejs/efs/replicationConfiguration.ts#L185-L194 typescript interface doesn't support adding tags • Also EFSReplicationConfiguration doesn't seem to support adding LifeCyclePolicies for the EFSReplicationConfiguration object? (This means that I am able to add LifeCycle Management to the "primary" EFS but not to the "replica" EFS Looking forward to your advices...

export interface ReplicationConfigurationArgs {
    /**
     * A destination configuration block (documented below).
     */
    destination: pulumi.Input<inputs.efs.ReplicationConfigurationDestination>;
    /**
     * The ID of the file system that is to be replicated.
     */
    sourceFileSystemId: pulumi.Input<string>;
}

Hi Team, I am running pulumi up from github action and have started seeing this error suddenly:

-- kubernetes:apps/v1:Deployment mobile-bff-deployment deleting original (0s) error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "https:/XXXX.yl4.us-east-1.eks.amazonaws.com/openapi/v2?timeout=32s": getting credentials: exec: executable aws failed with exit code 255

could you please suggest? I am not even trying to update the cluster, I just am building the service and deployment and creating manifest files from them

locally it runs fine, and all the aws credentials are also correct in the git actions

This message was deleted.

I have a really strange error that only manifests itself in the CI container.

$ pulumi $PULUMI_ACTION --logtostderr --non-interactive --diff -s $PULUMI_STACK
Previewing update (8g-sandbox):
[resource plugin kubernetes-3.23.0] installing
[resource plugin aws-5.16.2] installing
[resource plugin aws-5.30.1] installing
  pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:8g-sandbox::cr-eks::pulumi:pulumi:Stack::cr-eks-8g-sandbox]
@ previewing update....
Error: Failed to parse kubectl version JSON output. Received: : Error: Failed to parse kubectl version JSON output. Received: 
    at Object.assertCompatibleKubectlVersionExists (/snapshot/eks/bin/dependencies.js:46:15)
    at createCore (/snapshot/eks/bin/cluster.js:211:20)
    at createCluster (/snapshot/eks/bin/cluster.js:793:18)
    at new ClusterInternal (/snapshot/eks/bin/cluster.js:872:25)
    at Object.construct (/snapshot/eks/bin/cmd/provider/cluster.js:21:29)
    at Provider.construct (/snapshot/eks/bin/cmd/provider/index.js:129:100)
    at Server.<anonymous> (/snapshot/eks/node_modules/@pulumi/pulumi/provider/server.js:315:52)
    at Generator.next (<anonymous>)
    at fulfilled (/snapshot/eks/node_modules/@pulumi/pulumi/provider/server.js:18:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
error: Program failed with an unhandled exception:
Traceback (most recent call last):
  File "/root/.pulumi/bin/pulumi-language-python-exec", line 197, in <module>
    loop.run_until_complete(coro)
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/builds/8gears/saas-factory/k8s/infra/aws/.venv/lib/python3.11/site-packages/pulumi/runtime/stack.py", line 136, in run_in_stack
    await run_pulumi_func(lambda: Stack(func))
  File "/builds/8gears/saas-factory/k8s/infra/aws/.venv/lib/python3.11/site-packages/pulumi/runtime/stack.py", line 51, in run_pulumi_func
    await wait_for_rpcs()
  File "/builds/8gears/saas-factory/k8s/infra/aws/.venv/lib/python3.11/site-packages/pulumi/runtime/stack.py", line 82, in wait_for_rpcs
    raise exn from cause
  File "/builds/8gears/saas-factory/k8s/infra/aws/.venv/lib/python3.11/site-packages/pulumi/runtime/rpc_manager.py", line 71, in rpc_wrapper
    result = await rpc
             ^^^^^^^^^
  File "/builds/8gears/saas-factory/k8s/infra/aws/.venv/lib/python3.11/site-packages/pulumi/runtime/resource.py", line 921, in do_register
    resp = await asyncio.get_event_loop().run_in_executor(None, do_rpc_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/builds/8gears/saas-factory/k8s/infra/aws/.venv/lib/python3.11/site-packages/pulumi/runtime/resource.py", line 918, in do_rpc_call
    handle_grpc_error(exn)
  File "/builds/8gears/saas-factory/k8s/infra/aws/.venv/lib/python3.11/site-packages/pulumi/runtime/settings.py", line 273, in handle_grpc_error
    raise grpc_error_to_exception(exn)
Exception: Failed to parse kubectl version JSON output. Received: 
Resources:
    31 unchanged

If I run the same container with the same args locally instead the UI, I don't get this error, so its super difficult to trace the issue.

Hey folks, I have a question regarding project structure. Imagine I want to have a repository where I want to define and manage different, unrelated resources, but all of the same resource type, say, AWS Glue Jobs. I am a bit conflicted about what structure to have, and how that would work in a CI/CD setting. I was thinking of using a structure like this, since the configs would be sufficiently generic to apply to each job. Would this even work? Or do I need to have a top level

__main__.py

necessarily?

glue-jobs-pulumi
├── job-1
│   └── __main__.py
├── job-2
│   └── __main__.py
├── job-3
│   └── __main__.py
├── Pulumi.yml
└── Pulumi.dev.yml

Hi all, I am using aws crosswalk package to create application load balancer, ECS task definitions and target groups. I want to create two container port mappings something like below.

ports:
      - "3000:3000"
      - "3001:3000"

I want to create seperate load balancer and listener for each port mapping in the above. Can anyone suggest how to create the listeners and target groups for the above requirement?

Hi Everyone, was wondering if there is a way to inject or use a different Configuration provider instead of default implementation of reading from the stack's yaml file? eg. Custom API, Databse, JSON file, Azure App Configuration or other 3rd party tools that allow you to store a key value pair with required attributes like Pulumi project, stack etc.

I had a general question I was reading up on https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/ and I am curious about proper syntax to ignore an entire nested list

var res = new MyResource("res",
    new MyResourceArgs { Prop = "new-value" },
    new CustomResourceOptions { IgnoreChanges = { "root.nested[*]" } });

^will this work to ignore everything under that nested block?

and nested is a list of key value pairs

roo.nested = [ {"name": "foo", "value": "bar"}, {"name": "wiz", "value": "bang"} ]

Quick clarification question regarding IgnoreChanges: https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/#:~:text=Pulumi%20ignores%20a%20property%20by%20using%20the%20old,the%20state%2C%20most%20importantly%20when%20creating%20the%20resource. I have a situation where I created the Azure testing env via console and I tried importing/copy paste the response into index and running into a bunch of diffs and re-create resources. I know that what was imported is correct (such as the sql db) and I don't want pulumi to try and recreate the database, firewall rules etc. Is there a way with IgnoreChanges to ignore all resources under a resource group or something like that? If not, what would that look like if I were to do this for an existing sql db off the example from the link below?

Is there a recommended/safe-way to migrate a resource from one provider to another, assuming it's the same thing? (e.g. an aws provider). Going from default to explicit provider, for example.

Hi, anyone can help?

Holy smokes I wish there was a way to throw an exception when I accidentally serialize an Output as a string…

This message was deleted.

Is there a way to get pulumi to continue on error? For example creating a whole lot of new resources in an account, or destroying them. It stops at the first error, when in fact it could have created or destroyed a lot more if it just continued on