Hmmm... It's hanging even despite a pulumi destroy. This seems like some kind of problem with my stack itself? Edit: It's definitely due to there being something hanging in my code itself... I take out part of it and it successfully applies. Edit: node-redis is the most horrible library I've ever encountered and doesn't document this behavior, or pulumi is doing some sort of weird teardown stuff that makes it so that you have to client.Quit() in order for your program to stop running, or I'm an idiot and blind and can't see where it's stated that this is the case

How do I delete a stack in using automation?

destroy

doesn't seem to delete the stack, just the resources so I still see the empty stack in the UI.

Can't delete a child state due to a missing parent state (tried refreshing, and deleting resources out of band..., also tried recreating the missing namespace and

pulumi refresh

ing, but the same error pops up(!))

$ pulumi up -fy
[...]
  kubernetes:<http://helm.sh/v3:Chart|helm.sh/v3:Chart> (in):
    error: resource complete event returned an error: failed to verify snapshot: child resource urn:pulumi:omega::haze::kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:<http://helm.sh/v3:Chart::mesh-viz|helm.sh/v3:Chart::mesh-viz> refers to missing parent urn:pulumi:omega::haze::kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace::linkerd-viz

so it claims

mesh-viz

chart URN exists, yet it doesn't...

$ pulumi state delete urn:pulumi:omega::haze::kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:core/v1:Namespace$kubernetes:<http://helm.sh/v3:Chart::mesh-viz|helm.sh/v3:Chart::mesh-viz>
 warning: This command will edit your stack's state directly. Confirm? Yes
error: No such resource "urn:pulumi:omega::haze::kubernetes:core/v1:Namespace:core/v1:Namespace:core/v1:Namespace:core/v1:Namespace:<http://helm.sh/v3:Chart::mesh-viz|helm.sh/v3:Chart::mesh-viz>" exists in the current state

Not able to escape this race conditions. I also can't delete the inexistent parent either 😂

i’m trying to destroy resources in my stack, but i get the error that I cant remove a protected resource. How can I bypass this and force delete? Or how can I get a list of all URNs that I can pass to the

--target

option of

pulumi destroy

?

Hi! anyone know how to configure permissions of a private ECR registry? https://docs.aws.amazon.com/AmazonECR/latest/userguide/registry-permissions-create.html

For a self-hosted backend (azure blob in this scenario), is it possible for a stack reference to access a different blob container and/or storage account for it's state? I'm thinking of "container" as "project" in comparison to the pulumi hosted state scenario, but obviously the syntax doesn't map across.

does a stack need to be init'd before it can be used? For context... If we have a storage container created in Azure, will I need to connect with the CLI in order to

init

a new stack in that solution I'm deploying?

HI! I'm deploying our Dockerfile in AWS ECS. I have the credentials configured in ~/.aws/credentials and everything is working 🙂 Now I want to add my AWS credentials to the Dockerfile, as ARGs, because I want to download secrets during the build or the deployment. How can I get the key and the secret from the Pulumi config? Maybe something like this?

new pulumi.Config("aws").require("aws-key")

This is how I'm building my image now.

image: awsx.ecs.Image.fromDockerBuild(stackName, {
   context: './..',
   dockerfile: './app/Dockerfile',
   args: {
     'APP_ENV': environment
   }
}),

anyone know how to debug

error: Duplicate resource URN 'urn:pulumi:my-infrastructure::go::pulumi:pulumi:Stack::go-my-infrastructure'; try giving it a unique name

It doesn't give me what resource is colliding... I think I narrowed it down to

ec2.NewVPC

but this block was directly grabbed from a

pulumi import ...

so it should be in the state

Hey guys! We just wrote our first serious dynamic provider in TypeScript, and we’re excited about it. I noticed that when you compile the TypeScript into JS and run it, you get this error:

'() => provider': index.js(19,37): captured
      variable 'provider' which indirectly referenced
        function 'DatabaseChangeLogResourceProvider': DatabaseChangeLogResourceProvider.js(28,15): which referenced
          function 'generateChangeLogFile': DatabaseChangeLogResourceProvider.js(32,25): which captured
            variable 'fs' which indirectly referenced
              function 'writeFileSync': which referenced
                function 'getOptions': which captured
                  'ERR_INVALID_ARG_TYPE', a function defined at
                    function 'NodeError': which referenced
                      function 'getMessage': which captured
                        variable 'messages' which indirectly referenced
                          function 'get': which could not be serialized because
                            it was a native code function.

It works perfectly fine if you reference it in TypeScript. I care about this because I’d like to put it in an NPM package and use it in many applications. Any ideas?

After talking with a few people, they suggested it might just be my compilation process

The Pulumi UI (https://app.pulumi.com/) is a bit shaky today. Navigating to a project site results in 404.

hey @busy-honey-73811 - please can you open an issue in the pulumi/pulumi repo?

Did anyone manage to successfully use pnpm for a Pulumi app? I'm facing several ``Could not include required dependency '<...someModuleName...>'`...

Hey guys, I am trying to use Pulumi in Azure Dev Ops release pipeline and I am receiving this

error: no resource plugin 'pulumi-nodejs' found in the workspace or on your $PATH

every time I try to run

pulumi preview

. In this pipeline I am using the installation script but I can’t change the PATH. Therefore, I am adding the path of the installation to

PULUMI_HOME

as

C:/<path>/.pulumi

. I am running pulumi as

<path>/.pulumi/bin/pulumi.exe

. Even after all that, the error about not finding the plugin is still happening. Any idea?

A meta question. Is there any plans to provide a provider for pulumi? It would be nice to be able to configure pulumi just the same way as with all the other things pulumi supports 🙂.

you mean like the Automation API?

i.e. programmatically run pulumi, and configure stuff

Or do you mean a provider for the API that powers the saas? So teams / users / organisations?

Hey folks, anyone have any idea how to create an s3 bucket within a certain region, which isn't the default region for the stack that i'm standing up

Can that be done ?

Maybe via https://www.pulumi.com/docs/reference/pkg/aws/provider/? Adding that as an argument via CustomResourceOptions

ah cool cheers

what would be the equivalent in pulumi to the local-exec terraform provisioner?

We are evaluating pulumi and I’m trying to run through the quick start. I’m not able to login with the website or an access token and I can’t figure out what the problem is. Everything I do results in a timeout. Any suggestions?

~/Code/quickstart $ pulumi login
Manage your Pulumi stacks by logging in.
Run `pulumi login --help` for alternative login options.
Enter your access token from <https://app.pulumi.com/account/tokens>
    or hit <ENTER> to log in using your browser                   : 
We've launched your web browser to complete the login process.

Waiting for login to complete...
error: problem logging in: performing HTTP request: Get "<https://api.pulumi.com/api/user>": net/http: TLS handshake timeout

~/Code/quickstart $ pulumi login
Logging in using access token from PULUMI_ACCESS_TOKEN
error: problem logging in: getting user info from <https://api.pulumi.com>: performing HTTP request: Get "<https://api.pulumi.com/api/user>": net/http: TLS handshake timeout

OSX Big Sur, pulumi installed with homebrew, v2.220.

Has anyone done anything like drift detection with Pulumi?

Is anyone here using spinnaker with pulumi? and specially to deploy in ECS? I'm just getting started on spinnaker, still checking options, but I'm having a hard time wrapping my head around how spinnaker and pulumi will work together. I'm setting up, a ecs cluster, that will have various microservices. Pulumi sets all the infra needed for it. And was checking spinnaker to manage the deployments and pipelines, but from what i understand, seems like spinnaker also wants to manage some infra, to be able to control de deployments in detail. so here is where i get lost. Also open to other suggestion for CD systems that integrate nicely with pulumi.

Friendly unsolicited advice: You guys should really consider slowly replacing the entirety of Gitlab's CI/CD offering. I already see a bit of it with the docker provider, and someone really needs to do to them what you're doing to terraform. Gitlab-ci.yaml files are just not powerful enough.

Q: From my understanding, users could set tag for a stack by using CLI

pulumi stack tag set

. I would like to ask is there any way to set the tag via a config file? For example setting some property in

Pulumi.yaml

or

Pulumi.<stackName>yaml

?