Is there a "gratuitous destroy" like, just delete everything you know about, ignore the pending actions?

I got this error when doing a pulumi up

error: failed to load checkpoint: blob (code=Unknown): MissingRegion: could not find region configuration
error: could not create stack: An IO error occurred during the current operation: blob (code=Unknown): MissingRegion: could not find region configuration

Any thought?

Another issue highlighted with the prometheus operator helm chart... The test that fails specifies

restartPolicy: Never

but pulumi times out after waiting > 10m for it to become ready, which is both pointless and painful.

I've been told that community / open-source version of pulumi is only single user... Can someone explain that?

Am I looking at the wrong tool if all I want to do is templatize my kubernetes manifests?

hey guys, I have a question about the github-actions bot

hey peps trying to deploy a private cluster can’t find anything related to

-no-enable-master-authorized-networks

inside the typescript GKE configs

Hi, Is there any example of capturing using pulumi logs for helm chart deployment on eks? The one mentioned in the blog is helpful (https://www.pulumi.com/blog/unified-logs-with-pulumi-logs/) as there are methods like onObjectCreated on bucket object. I am really looking for basic logging on eks (https://www.pulumi.com/docs/guides/crosswalk/aws/eks/) . I have deployment of several charts and it takes 15-20 min to bring up the cluster. So, i would like to track the progress using logs.

One question about the verbiage on the website for the "Team Starter" plan: It says "_Up to 20 project stacks_." Does that mean you're allowed 20 stacks per project, with unlimited projects? Or is it 20 stacks, distributed however you want among n projects? For example, 5 projects each with 4 stacks.

Hi guys, I am looking for resources on how to manage Google Cloud Run with Pulumi. So far I am able to create my runner but I can’t find how to set the

allow-unauthenticated

arg so that I can make it public. Any lead is welcome 🙂

question regarding: https://github.com/pulumi/pulumi-kubernetes/blob/master/sdk/nodejs/helm/v2/helm.ts#L246

installOrder is missing some 'kinds' that exist in helm master: https://github.com/helm/helm/blob/master/pkg/tiller/kind_sorter.go#L29

also helm kind_sorter has an uninstall list that is NOT a reverse of the install list: https://github.com/helm/helm/blob/master/pkg/tiller/kind_sorter.go#L68

how do i use pulumi outputs in a lambda callback?

did 1.2.0 break upgrading via helm again? (e.g. upgrading the nginx ingress controller)

Has anyone made flame graphs for a pulumi stack? We're managing around 8 eks clusters with multiple helm charts on each of them in one stack and the `preview`/`update` takes a long time to get to the confirmation prompt

@busy-umbrella-36067 I don’t think anyone has but that would pretty cool!

I'll make an issue, it would be really helpful to pinpoint which part of the IaC is hanging up the preview

Some additional tracing support was added just last week I think... let me find it.

a bug fix i'm interested in was merged into pulumi-azure 2 weeks ago but no release as yet - are they scheduled in any way?

Tracing changes were in https://github.com/pulumi/pulumi/pull/3238. You can write tracing data to a file with

pulumi up --tracing=file:./out.trace

and then view the data with

PULUMI_DEBUG_COMMANDS=true pulumi view-trace out.trace

.

Interesting, seems that

pulumirpc.ResourceMonitor/RegisterResource

takes up 85% of the preview time

Any reason

<http://pulumi.com/timeoutSeconds|pulumi.com/timeoutSeconds>

is an annotation instead of an option to the pulumi resource? Seems weird to be modifying the resource in order to change the behavior of pulumi. Same goes for

skipAwait

.

Is there any information on when the kubernetes provider 1.2 version will be released? Asking because we’re running into an issue with the hack done for waiting on jobs, and it would be cool to not need to fix the hack further.

I'm trying to do an import on an s3 bucket, and it wants to change the name of the resource, which causes a warning.

aws:s3:Bucket (bucketName):
  warning: inputs to import do not match the existing resource; importing this resource will fail

This is the change: 
~ bucket: "bucketName" => "bucketName-8c54a03"

code

const config = new pulumi.Config();
const sb: string = config.require("sourceBucket")

const sourceBucket = new aws.s3.Bucket(sb,
                                      {},
                                      { import: sb });

This is a support request for Pulumi. I have a stack that deploys the helm chart 'aws-alb-ingress-controller', then creates an Ingress k8s resource. The combination of those two items results in the creation of an AWS ALB (the controller monitors Ingress resource CRUD and mirrors those changes in an ALB). The works perfectly when doing a 'pulumi up'. Here's the problem point. when doing a 'pulumi destroy', the controller is either destroyed before the Ingress deletion is noticed or the Ingress is deleted after the controller. How do I prevent this from happening? Is it possible to add a delay or hook or anything that will alter this processing? Thanks in advance.

I’m curious what people would recommend here: We have a project (CI). We have 4 environments (dev, staging, prod, support). CI runs in support. We need to create a GCP service account in the support stack (we have one stack per env), but then reuse that stack in the other 3 envs so that we can grant it a role in GCP. Given that TypeScript doesn’t allow exporting inside of a conditional, what’s the best way to reference that service account? The issue is due to TS and the way Pulumi requires things to be `export`ed for it to be used in a stack reference.

@lemon-spoon-91807 Do you know if the stack ref OutputSync bug was fixed? We are doing this in a lot of places, wondering if it was still needed?

const vpcPrivateSubnetIds = (stackRef.requireOutputSync("vpcPrivateSubnetIds") as unknown) as Array<
  pulumi.Output<string>
  >;

If I wanted to pre-process a function (say, webpack or babel), would I just do a normal webpack build process and

require

the output in a

CallbackFunction

?

I cannot get aliases to work to migrate my resources when I move them inside component resources. I have a bunch of resources that didn't have an explicit parent. I created a component resource and moved all existing resource inside. Then I exported the stack and took the `urn`s to use in the

aliases

argument of each existing resource. When I

pulumi up

, all resources are to be recreated. I am pretty sure the urn is correct, as I am taking it from the exported stack file. Here is an example resource:

const logGroup = new aws.cloudwatch.LogGroup(`${name}_cloudwatchLogGroup`, {}, { provider, parent: this, aliases: ["urn:pulumi:edith-lookup-feat::edith::aws:cloudwatch/logGroup:LogGroup::cloudwatchLogGroup_edith-lookup-service"] });

What am I doing wrong?