Hi there. Does anybody know if it's possible to store a

RemoteArchive

on an

S3

bucket? I'm trying to use it as the source code for a

Lambda

function. The docs say that the URI should be http/https/file and it doesn't accept s3:// - https://www.pulumi.com/docs/intro/concepts/assets-archives/ - Any ideas for a viable workaround? Opening up the bucket to http access wouldn't work in this case.

Hi everyone! I'm trying to create a FargateService with a load balancer. Does anyone have any tips on how I can map port 80 on the listener to the containers port on 3000?

if I understand this correct - CustomResourceOptions to specify ImportId - I cant depend on any previous outputs since it takes string and not Input<string> ?

Hi Pulumi team, thanks for the great tool! I'm glad to be here! 🙌

When I try to create a lambda function with a local code path, like:

const helloWorldFn = new lambda.Function('hello-world', {
  code: new asset.FileArchive(`${__dirname}/../../build`),
  handler: 'build/src/index.telemetryClassifierHandler',
  name: 'pulumiTestFn',
  publish: true,
  role: role.arn,
  runtime: 'nodejs14.x',
  tracingConfig: {
    mode: 'ACTIVE',
  },
});

I am seeing a

ValidationError

like in the attached image, however I can upload a zip file of that directory in the AWS console (or via serverless and/or terraform) and all of them seem to be okay with the contents of the

build

dir. I have tried creating a zip file separately and using that file as the

FileArchive

, as well as changing the handler to include the

build/

prefix or not I don't see any useful logs on what is failing to validate when using

--debug

or

--verbose 4

. Has anyone seen this before, or know how to debug what is wrong?

Is there any way to get an explicit reference to a default provider instance inside a Pulumi program?

Hi folks! I’m currently working on pulumi CI/CD pipeline. When using monolithic repository scheme (multiple projects in a repo), what would be the best way to preview & deploy when the MR changes multiple projects at a time? I think that pulumi stack well corresponds to git branch, but I’m having a trouble how to conduct gitops on multiple projects

I am deploying a Fargate service and using

awsx.ecs.Image.fromDockerBuild

to create my docker image that gets deployed but it seems that it will always attempt to build and deploy a new docker image even if the image is unchanged. I often find myself changing other parts of the infrastructure but would prefer not to have to do an entire build. Is there any way to avoid this?

Hi Team, i'm using https://www.pulumi.com/docs/reference/pkg/rancher2/ for my cluster creation/provisioning in rancher, and i'm trying to find the resource which can create service account, is it possible to create it?.

Does anyone know how to add new secrets to a stack without having to actually deploy them? We deploy through gitlab CI so those hosts will need to be able to access the secrets via pulumi config, but creating a secret on my machine with

pulumi config set --secret

seems to be purely a local modification until I were to deploy from my machine I guess. But I obviously don't want to deploy to production from my laptop just to update the config.

There’s currently no established way to setup general config key/value pairs which would apply to all stacks, right? kind of like a default config: key

Hi, I'm pretty new with pulumi trying to figure out few things, especially with reading outputs of one resource and re-using them in another. I have deployed rancher2.Cluster resource and trying to read its outputs and passing it to rancher2.AppV2

rancher_ci_cluster = rancher2.Cluster()

chart = rancher2.AppV2("cluster-autoscaler",
    cluster_id=rancher_ci_cluster.id,
    namespace="kube-system",
    repo_name=catalog.name.apply(lambda name: name),
    chart_name="cluster-autoscaler",
    chart_version="9.10.7",
    values=f"""
awsRegion: {config.require("rancherAwsCiRegion")}
autoDiscovery:
  clusterName: {rancher_ci_cluster.name.apply(lambda name: name)}
extraArgs:
  balance-similar-node-groups: true
priorityClassName: system-cluster-critical
""",
    opts=ResourceOptions(depends_on=catalog)
    )

so in the above snippet i could read the rancher_ci_cluster.id without any apply() or all() . but for looking up name even though i used

rancher_ci_cluster.name.apply(lambda name: name)

i still see it as an object instead of raw data

<pulumi.output.Output object at 0x103a73e20>

. so can anyone help me understand what is that im missing here and how the behavior works?

Having an issue getting ApplicationLoadBalancers to point to a fargate service. Pulumi up runs and the fargate service deploys, but the ALB has no targets

const lb = new awsx.lb.ApplicationLoadBalancer(`hasura-${env}`);

const listener = lb.createListener(`hasura-listener-${env}`, {
  protocol: "HTTPS",
  certificateArn: sslCertificateValidation.certificateArn,
});

const hasuraService = new awsx.ecs.FargateService(
  `hasura-${env}`,
  {
    cluster,
    desiredCount: 1,
    taskDefinitionArgs: {
      logGroup: logGroup,
      cpu: "1024",
      memory: "2048",
      containers: {
        service: {
          // logConfiguration: {
          //   logDriver: "awslogs",
          //   options: {
          //     "awslogs-group": logGroup.id,
          //     "awslogs-region": awsRegion!,
          //     "awslogs-stream-prefix": `hasura-${env}`,
          //   },
          // },
          image: hasuraImage,
          portMappings: [listener], ....

Really need an answer for this. 🙏 My current workaround is to create Pulumi.stack-name.yml for the new stack dynamically in the ci and then discard it which is super hacky. Use case is automated branch deployment on pull requests.

Hi everyone! When running

pulumi up

I use the -C parameter like this:

pulumi up -y -C pulumi

, since I use a subdirectory in our project for everything pulumi related. Sadly this doesnt pick up tsconfig.json, which is defined at root level of the project (the directory in which I run the mentioned command). Is there anyway to tell pulumi where to look for tsconfig.json? It works to just copy tsconfig into the /pulumi directory, but id greatly prefer to not have it twice in our project.

Hi, is there any way to set values to a helm chart using a url of the file of values?

Hi Team, does pulumi kubernetes provider allows us to do

exec

as we can do in terraform provider? https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#exec-plugins #general

With the new aws-native provider, is there an AWS quota I can increase that would reduce the rate of these rate limit errors?

Howdy, I was hoping for a quick double check on this before I filed an issue with the docs site on github, it looks like this AWS resource has an issue where the property description of a child resource is bubbling up to the parent's attribute? <https://www.pulumi.com/docs/reference/pkg/aws/cloudtrail/trail/#properties> The description for

name

on

Trail

resource properties looks like it erroneously has the description for

TrailAdvancedEventSelector

's

name

Pulumi slack webhooks, any idea what this means?

missing_text_or_fallback_or_attachments

is there a way to use pulumi to execute HCL code without converting it ?

Hello Everyone, I've stuck working with Pulumi Input. Can't make it through. If someone has time, please check my attached screenshot in the thread.

Is there any way to list the resources (URN) within a stack or get a parsed state file using the automation APIs?

Hey guys, I have a stack with many different resources, that include GCP and Kuberenetes (most for kubernetes) and it so slow, I can’t edit the stack for pending_operations because all time I got

500

when tried to import, someone know any solution?

🙏 are there plans to add this as a provider any time soon? https://github.com/elastic/terraform-provider-ec

Has anyone ever had pulumi up hang in preview mode when creating a stack and reading a Stack Reference? I have a stack that has a stack reference to a Network Stack and it hangs every time upon preview. Never seen this before and wondering if anyone else has and has any tips on how to handle?

basically is stuck on Create...

I worked out the cause of the issue above. Looks like the application stack was referencing a later version of Pulumi.Aws then the Network stack that it was referencing as a stack reference. Changing the reference to the same Pulumi.Aws version fixed the issue.

Hello everyone, question regarding Dynamic Resource Providers. With typical resource providers like AWS, at least in the case of Terraform and according to my understanding, the provider itself merely handles auth and general configuration that is applicable to all downstream API calls while the resources themselves seem to handle the details of how to CRUD which kinda makes sense as the provider would otherwise be a massive switch statement. In Pulumi and with dynamic resource providers, it seems the right usage pattern is to have a one to one mapping between the dynamic provider and the resource it manages Am I understanding this correctly? For example, if I were to build a resource provider to support provisioning a Database and a User in fictitious database server then I would end up with two dynamic providers for each kind of resource and not one provider that can handle both resources?