Hello everyone! My team is trying to use Pulumi to create Azure Logic Apps (Standard) that have multiple workflows under one Standard Logic App. We can find details on how to create a logic app, but we want to create multiple workflows under one standard logic app. Has anyone done this before? We have looked over all Pulumi documentation and none of it is helpful in creating one standard logic app with multiple workflows under it. The documentation is only for creating the logic app in itself. Thanks in advance!

Are there limitations to the local backend? Background: I am writing "pytest-pulumi", a small library of helpers for e2e tests in Python. When using the Pulumi Service backend, everything works fine, but when using the local backend, there is a specific test that fails.

Is there a way to standup a new ECS Fargate cluster with an existing VPC using awsx?

awsx.ecs.FargateService

does not include a vpcId param, unlike other similar services and it's unclear to me based on documentation. Any advice would be very appreciated!

Hi @echoing-match-29901 I am trying to create dynamo db resource but the allowed attribute types are only [S, N, B] -- how can I create attribute of some other type (supported by Dynamodb)?

Hello team, we are moving from monolithic stacks to micro-stacks, is there any best practices for sharing config between stacks? let's say we have a monolithic infra's stack with a few environments, and we want to migrate to micro-stacks which having separated microservices + lambda + infra's stacks, and they need to re-use a lot of shared-config, for example, the directory. Thanks in advance

.
├── application
│   ├── Pulumi.dev.yaml
│   ├── Pulumi.next.yaml
│   ├── Pulumi.prod.yaml
│   ├── Pulumi.staging.yaml
│   ├── config.ts
│   ├── index.ts
├── infrastructure
│   ├── Pulumi.dev.yaml
│   ├── Pulumi.next.yaml
│   ├── Pulumi.prod.yaml
│   ├── Pulumi.staging.yaml
│   ├── config.ts
│   └── index.ts
└── lambda
    ├── Pulumi.dev.yaml
    ├── Pulumi.next.yaml
    ├── Pulumi.prod.yaml
    ├── Pulumi.staging.yaml
    ├── config.ts
    └── index.ts

Hello, I have developed a platform that allows students to access exercises (in cyber security) and initiate the creation of a new environment on AWS, including a VPC, subnets, security groups, and instances. I am using Python multiprocessing and Pulumi automation to create a new stack and use Pulumi’s

up

command to create the environment. However, when more than 10 students access the platform simultaneously, I experience issues. It seems that each Pulumi process consumes approximately 200 MB of memory, causing the server to crash or become slower. Could you provide some suggestions for optimizing the process of creating environments in a parallel manner? It is also important that the environment be created as quickly as possible. Thank you.

Hey All; Question. Can I with Pulumi - Create AND Destroy resources with Pulumi Up? For example.. Create a GKE Cluster, Create a Bastian VM, Run Commands on the VM and then Destroy the VM all as part of the Pulumi Up Command. Once the Pulumi Up has finished i would have expected my commands to have run on the VM but the VM not exist any more…

Does anyone have any sort of recipe for how to create a LogGroup for my Lambda function?

Hey All: Does Pulumi azure-native for LoadBalancer support passing Network interface as input? i can see from documentation it accepts LoadBalancerBackendAddress which takes ip-address as input. https://www.pulumi.com/registry/packages/azure-native/api-docs/network/loadbalancer/#loadbalancerbackendaddress - My use case is i want to attach network interface to backend pool of load balancer. Any quick help/reference link is appreciated.

hello, I have a question with SecurityGroupIngress. The example in the documentation shows the definition as:

ingress=[aws.ec2.SecurityGroupIngressArgs(
        description="TLS from VPC",
        from_port=443,
        to_port=443,
        protocol="tcp",
        cidr_blocks=[aws_vpc["main"]["cidr_block"]],
        ipv6_cidr_blocks=[aws_vpc["main"]["ipv6_cidr_block"]],
    )]

If I want to have different rules, for example:

ingress=[
                {
                    "description": "https inbound traffic",
                    "protocol": "tcp",
                    "from_port": 443,
                    "to_port": 443,
                    "security_groups": [securityGroup],
                },
                {
                    "description": "http inbound traffic",
                    "protocol": "tcp",
                    "from_port": 80,
                    "to_port": 80,
                    "security_groups": [securityGroup],
                },
            ],

can I pass several arguments like so many dictionaries in the SecurityGroupIngressArgs function?

ingress=[

			aws.ec2.SecurityGroupIngressArgs(
                {
                    "description": "https inbound traffic",
                    "protocol": "tcp",
                    "from_port": 443,
                    "to_port": 443,
                    "security_groups": [securityGroup],
                },
                {
                    "description": "http inbound traffic",
                    "protocol": "tcp",
                    "from_port": 80,
                    "to_port": 80,
                    "security_groups": [securityGroup],
                },
            ],
            
            )

Hi folks, I wonder if anyone can help me with this pulumi-docker issue: https://github.com/pulumi/pulumi-docker/issues/448 In a nutshell I want to deploy a RemoteImage to an azure webapp, but the deployment seems to be missing important details, such as specifying which registry (the image is just a stock dockerhub image). More generally I'm struggling a lot with getting container-based webapps to refresh when I update the container image, and I wonder if I'm doing something wrong- even in cases where I'm deploying from a new image build in a private registry the container deployment logs show no evidence of activity.

In the IaC tooling/framework workd, there is a growing/emerging trend of turning k8s cluster into an universal control plane. CNCF project Crossplane and AWS initiative of ACK (AWS Controller for K8s) are 2 examples. There is even an community effort of combing AWS CDK8s with Crossplane to provide the same benefit Pulumi/CDK which is to allow user using their family programming language for IaC tasks. I'm wondering if there is a similar initiative in pulumi world to combine pulumi with Crossplane?

Hello, I’m working on Cloudflare at https://www.pulumi.com/registry/packages/cloudflare/api-docs/teamsrule/#teamsrulerulesettingsl4override and can I bypass

TeamsRuleRuleSettingsL4override

required variable `ip, port`since it’s optional from Cloudflare? and the same for

check_session

"rule_settings": {
            "add_headers": {},
            "biso_admin_controls": {
                "dcp": false,
                "dcr": false,
                "dd": false,
                "dk": false,
                "dp": false,
                "du": false
            },
            "block_page_enabled": true,
            "block_reason": "",
            "check_session": null,
            "insecure_disable_dnssec_validation": false,
            "ip_categories": false,
            "l4override": null,
            "override_host": "",
            "override_ips": null
        },

Hi can anyone help me here with using pulumi helm release for aws ack controllers? how can I specify region for that?

new k8s.helm.v3.Release("rds-chart", {
      version: "v0.1.2",
      namespace: rdsServicesNamespace.metadata["name"],
      chart: "<oci://public.ecr.aws/aws-controllers-k8s/rds-chart>",      
      values: {
        region: "us-east-1", // use region from config
        serviceAccount: {
          name: serviceAccountName,
          create: false,
        },
        vpcId: vpcId,
        clusterName: clusterName,
        podLabels: {
          stack: stackName,
          app: "ack-rds-controller",
        },
      },
    },
    {
      provider,
      parent: provider,
    })

In my above release config, I have specified region but the pod fails to start with error saying, region not specified

Just curious @echoing-match-29901, am I asking too easy questions or am I asking it in an improper way? or am I in a wrong channel? There is no activity on my questions

May your 2023 be filled with peace, joy and health. Happy 2023!

Hi there, Is there anyway to get

id

of a Cloudflare Access Group from state file by given only

resource_name

, following documentation https://www.pulumi.com/registry/packages/cloudflare/api-docs/teamsrule/#look-up and look like

id

is required while looking for an existing resource

Hello, I'm looking for some support contact where to slove our billing related issue. Does support@pulumi.com exist? Or something like that?

Hey folks, I was wondering, now that global configs (instead of stack specific configs) are supported, is it possible to also set global secrets?

hi all, this is a bit of a random question - I came across a project about a month ago where you write your application code and the tool parses your code and automatically generates your IaC files for you (I think in terraform format). e.g. in the following application code, it would generate the files required to provision the bucket — any clues? I think it had the word “rain” in the project name:

import Bucket from 'sometool'
const bucket = new Bucket()
export const addObject(key, data) => bucket.addObject(key, data)

Having trouble compiling this for MUSL on Void Linux.

https://pulumi-community.slack.com/archives/C84L4E3N1/p1672588499418919 I need your help 😒miling_face_with_tear:

Hey everyone, I'm running into an issue when trying to

preview

a stack that has not been `up`'d before. I'm getting the following error:

pulumi:pulumi:Stack test-project *create* error: malformed header: missing HTTP content-type

. I'm using Pulumi TypeScript with AWS (versions below). Any idea why this could be happening? CLI version:

v3.50.2

@pulumi/aws:

5.25.0

@pulumi/pulumi:

3.50.2

could you open a bug report with more details of your situation? https://github.com/pulumi/service-requests

Hey all 🙂 I'm transitioning into pulumi (pretty new to it), I'm trying to create two different programs that one references the other. I want to separate it into two different programs in order to split our huge project into small building blocks with dependencies and order. In my case I want to share a

k8s.Cluster

object from the first program into the second program that creates several virtual clusters inside the cluster from the first program. My questions are: • Is it possible to share the object as it is? • Is it possible to share my own custom

ResourceComponents

? • To implement that I need to have multiple stacks?

Hi everyone, transitioning to pulumi and need a little help.. Whenever I do pulumi preview, in preview it show that it wants to delete the resources previously provisioned like a few mins back. When actually there's no change or drift in state of the resources. Any idea why this would be happening?

hi, I'm all new to

pulumi

and I have a question about javascript usage:

// 1.
const image = new docker.Image(...) // promise ?

// 2.
const service = new gcp.cloudrun.Service(, { // promise too
  ...
  image: image.imageName,
  ...
})

I guess 1.

new docker.Image

returns a promise, but how 2.

await

for it ?

Hi community, i'm relatively new using Pulumi and im having troubles trying to execute a Release if the chart link im calling is an "oci://..." stored in a Private AWS ECR (I've read that this is supported on helm.v3.Release() but not on helm.v3.Chart()) , it returns Unauthorized, the question is, How should i pass the ecr credentials into the Release function? I've tried to use the RepositoryOpts argument (with repo, username and password) but couldn't find the workaround. I've tried different variations of the following function (with or without the RepositoryOpts argument):

pulumi_kubernetes.helm.v3.Release(
    "resource_name",
    resource_args_object=pulumi_kubernetes.helm.v3.ReleaseArgs(
            chart="oci://{account}.dkr.ecr.{region}.<http://amazonaws.com/{chart_name}|amazonaws.com/{chart_name}>",
            version={chart_version},
            values=values,
            namespace=namespace,
            create_namespace=True,
            reset_values=True,
            force_update=True,
            dependency_update=True,
            ),
    opts=pulumi.ResourceOptions(provider=provider),
)

Where provider is a pulumi_kubernetes.Provider with the cluster kubeconfig. Does someone have any example of how this should be done?

Hello all (and happy new year), Question I’m asking myself and cannot find online answer. I have a single-tenant product that I want to deploy. This product can have N instances based on customer needs. Can I use one stack per tenant? My idea would be to have the same code for every customer, but manage the number and type of instance through stack-configuration. Does it look a good approach?