How might I set the log group parameters on a pulumi lambda function resource? i would like my lambda logs to only persist for a week instead of default never

👋 Hello everyone!

Hello @future-cartoon-6373

Is there any way to backup the state locally from the Pulumi Service Backend?

Anyone know a way to check if the current stack has a lock and wait a specified amount of time for it to clear? I’m trying to deal with parallel CI/CD builds

Hi everyone! 🙂 I read the FAQ on error-handling (I like that this is the first question!) but I’m still left wondering: Can you define custom deploy-time error-handling logic in Pulumi? For example, if I hit some CloudFront API rate-limit with a

pulumi up

, can I define error handling that says “Wait thirty seconds if you get this error code and retry only once” in a way that I can unit-test with something like

jest

?

Hi. I took a Typescript project that ran under Pulumi 2.x and when I try to run it under Pulumi 3.x I get this error:

import * as pulumi from "@pulumi/pulumi";
    ^^^^^^
    
    SyntaxError: Cannot use import statement outside a module

If I change back to Pulumi 2.x the code runs.

Good afternoon, I am trying to create a NEW custom VM Extension, but this seems to only try and reference a previously created artifact. Is there a way to do what I want and I've just made an error or...? #Create Custom VM Extension extension = compute.VirtualMachineExtension( "extensiontest", resource_group_name=resource_group.name, auto_upgrade_minor_version=False, enable_automatic_upgrade=False, type="CustomScriptExtension", type_handler_version="2.0", force_update_tag=False, publisher="KBC", settings={ "commandToExecute" : "mkdir c:\eric" }, vm_name=vm_TestVM.name ) error: Code="ArtifactNotFound" Message="The VM extension with publisher 'KBC' and type 'CustomScriptExtension' could not be found."

This message was deleted.

Hi all! I have some issues when configuring AWS Pub sub concept. So what I have configured is that SNS Topic can have multiple queues subscribed to it. However, we can add later on queues that already exist to the SNS Topic and there begins my issue. What we want to achieve is that in case given queue does not exist, it should assign newly created one otherwise just get queue by name. Some of the code is as following: entries.forEach(entry => { const topic = createTopic(entry.topicName); entry.subscriptions.forEach( sub => const queue = getOrCreateQueue(sub.queueName); setupSubscription(topic, queue); ) getOrCreateQueue part is problematic as I can not get it right with aws.sqs.getQueue and new aws.sqs.Queue calls. Any suggestion ? Thx!

Is there a way to ignore output such as this?:

Diagnostics:
  docker:image:Image (docker-image):
    warning: #1 [internal] load build definition from Dockerfile
    #1 sha256:9a53212ce7383ff2e916b04be035bc67ab1898011a36579250c675eb4226f868
    #1 transferring dockerfile: 37B done
    #1 DONE 0.0s>
...

The docker image that is built throws out a lot of output and it is hard to see other more important information and I haven't yet found a way to suppress this diagnostics output

Does anyone knows how to specify and specific helm chart from a helm repo in kubernetes helm chart ?

Hi 👋 Does Pulumi offer 2FA login for individual accounts? Is it offered for team accounts? I’d like to secure my pulumi account.

Hello. Can anyone tell me what framework is used to build app.pulumi.com? I've seen the same framework in other saas products and would like to consider using it to build our own developer portal.

Good afternoon, I am trying to create a NEW custom VM Extension, but this seems to only try and reference a previously created artifact. Is there a way to do what I want and I've just made an error or...? #Create Custom VM Extension extension = compute.VirtualMachineExtension(     "extensiontest",     resource_group_name=resource_group.name,     auto_upgrade_minor_version=False,     enable_automatic_upgrade=False,     type="CustomScriptExtension",     type_handler_version="2.0",     force_update_tag=False,     publisher="KBC",     settings={         "commandToExecute" : "mkdir c:\eric"         },     vm_name=vm_TestVM.name     ) error: Code="ArtifactNotFound" Message="The VM extension with publisher 'KBC' and type 'CustomScriptExtension' could not be found."

Hello folks, is there an way to have multiple backend states? Lets say I have a single repository, and want to manage QA and PROD envs there. The "problem" arrives when I want to have different buckets for each env. I've had success in migrating from pulumi service to my GCP storage, but now i am looking for a way to actually have this, lets say a var or config for the project? Right now I have to keep running

pulumi login

for changing the bucket where the state is saved

this kind of helps: https://github.com/pulumi/pulumi/pull/5789

Hi, How do I ensure that the variables in .env are properly loaded before I read them (I write to .env during runtime)? As of now, I get undefined.

Questions about the

CrossGuard

policy enforcement in CI-CD... The docs talk about organization-wide enforcement of policy packs requiring an Enterprise subscription. However, it seems like a CI-CI pipeline could simply checkout the policy pack code into a folder in the checked-out Pulumi program and enforce the policies as one would when running locally. 1. Are there any restrictions from doing what I described in CI-CD with less-than Enterprise subscription? 2. Has any consideration been given to making the CrossGuard org-wide auto-enforcement feature an option for the other subscription tiers, perhaps with limits (e.g. no more than 100 policies at Team level) or for additional cost (e.g. US$1.00 per month per 100 policies) I’m going to be talking about and demoing CrossGuard at some conferences and honestly, it’s slightly annoying I can’t demo the full feature from a lower tier subscription (i.e. Team), even if it cost a little to do so. Instead, I’ll just have to hand wave around it and call out it’s only available with an Enterprise subscription at an unpublished-price.

hi, does the Pulumi Company team also hang out here ?

Hi, is there nobody from the Pulumi Company here

Hi, i'm trying to create aws vpc, and i got these errors, i don't understand where is my mistake

Hello All, has anyone else problems with WSL2 and Pulumi? I'am running pulumi as a docker image from WSL2 and try to create an Azure Postgres Flex Server. I get a "cannot unmarshal DNS message error". This seems to be a go problem (https://github.com/golang/go/issues/51127). Is there anything, the Pulumi team could do about it?

Is there a way to ensure that a resource does not exist? I’d like to delete the AWS default VPC for new accounts.

Is there a supported way of moving a stack to a different project? I've not found anything other than export stack -> edit urn to new project -> import stack, then redo all the config secrets which is a huge pain to do. Surely there must be an easier way?

Hi, I am trying to run the following code:

monitoring = kubernetes.helm.v3.Release(
    "monitoring",
    name="monitoring",
    chart="kube-prometheus-stack",
    namespace="monitoring",
    repository_opts=kubernetes.helm.v3.RepositoryOptsArgs(
        repo="<https://prometheus-community.github.io/helm-charts>",
    ),
    values={
        "grafana": {
            "ingress": {
                "enabled": True,
            },
        },
    },
)

grafana_ingress = kubernetes.networking.v1.Ingress.get(
    "grafana-ingress",
    Output.concat("monitoring/monitoring-grafana"),
)
grafana_ip = grafana_ingress.status.load_balancer.ingress[0].ip

But it errors as

status.loadBalancer

does not have the

ip

value. If I rerun multiple times

pulumi up

it will register and continue. Is there a why to define a sort of

timeout

for the

kubernetes.networking.v1.Ingress.get

? Thanks

Hi Pulumi Helpers (Urgent) I get the following error ...

pulumi:providers:eks (default_4_37_5):
    error: no resource plugin 'eks-v4.37.5' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource eks v4.37.5`

The latest

eks

plugin version is

v0.37.1

What do I do?

Hey Guys, If I am consuming output values from my current stack in a project, how would this behave when I am redeploying this to a brand new environment where the output will be only created during the same execution? Will pulumi wait for that output to be available and use that or will it fail?

The page on the Pulumi operator is quite light on justification of 'why this it is a good thing': https://www.pulumi.com/blog/pulumi-kubernetes-operator/ From https://github.com/pulumi/pulumi-kubernetes-operator it seems like it is purely CI/CD convenience - i.e. providing no additional functionality compared with deploying from say GitHub actions. Are there any specific advantages outside of CI integration that using the operator permits?

can we deploy the same pulumi stack with same state to different aws regions in the same aws account? or do we need to create a seprate stack and state backend for each region?