You’re calling a method on an object that is null.

Having trouble trying to create a

regional

gke cluster with a separate node pool. It seems that the

node-locations

is missing from the cluster creation. Here is the equivalent gcloud command - https://cloud.google.com/kubernetes-engine/docs/how-to/creating-a-cluster#regional. Is the

gcp.container.Cluster

api behind?

Hi, i am trying to mount a volume in a kubernetes deployment, but i am unable to get the deployment to start in the following configuration. i have tried removing the volume mounts, and the container starts without any issue. can someone advise on where i am going wrong?

const name = `${defaultName}-nextcloud`;

    // Create a nextcloud Deployment
    const appLabels = { appClass: name };

    const volume = new aws.ebs.Volume(name, {
        availabilityZone: "us-west-2a",
        size: 3,
        encrypted: true,
        tags: {
            name: name,
        }
    });

    const deployment = new k8s.apps.v1.Deployment(name,
        {
            metadata: {
                namespace: namespaceName,
                labels: appLabels,
            },
            spec: {
                replicas: 1,
                selector: { matchLabels: appLabels },
                template: {
                    metadata: {
                        labels: appLabels,
                    },
                    spec: {
                        containers: [
                            {
                                name: name,
                                image: "nextcloud:latest",
                                ports: [{ name: "http", containerPort: 80 }],
                                volumeMounts: [{
                                    name: "nextcloud-volume",
                                    mountPath: "/var/www/html"
                                }]
                            }
                        ],
                        volumes: [
                            {
                                name: "nextcloud-volume",
                                awsElasticBlockStore: {
                                    volumeID: volume.id
                                }
                            }
                        ]
                    }
                }
            },
        },
        {
            provider: cluster.provider,
        }
    );

with dynamic providers has anyone seen issues where __awaiter was not being captured? I can create one provider where I can see the __awaiter is captured, then I add a second provider to that library, the first one stops capturing __awaiter, not sure if these libs have stuff in common causing the serialization to happen differently. Working on creating a before/after repro, but was wondering if this rang any bells to anyone as i work on that

I see the eks package was released at

v0.17.0

but I'm seeing this error on `npm install`:

]$ npm install
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @pulumi/eks@0.17.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'eks-cluster'
npm ERR! notarget

Hey so we ran pulumi up here, and it was a newer version (maybe not important) and it caused a bunch of roles to get dropped from super important service accounts

(This is on GCP)

What is the right way tofile a ‘not sure how this happened, but this seems super bad’ bug that has some data in it that i’d prefer not to expose?

@microscopic-florist-22719 @white-balloon-205 I’m hitting the issue you described here https://github.com/pulumi/pulumi/issues/2310 using pulumi 0.16.8 (both CLI and nodejs sdk version). I thought this was fixed using https://github.com/pulumi/pulumi/pull/2332? I can describe the problem I’m facing in more detail if necessary but in short: I have a Stackreference which gets “old” / stale outputs from the referenced stack.

Hey all! As part of our latest milestone, we improved several core pieces of the Pulumi JavaScript/TypeScript SDK. As part of this we have released the

0.17.1

version of `@pulumi/pulumi. This change brings two nice improvements (which we will also document and blog about soon).

The first is that we have made is so that `dependsOn`ing a

ComponentResource

will now end up causing you dependOn all the child resources of that

ComponentResource

. This is useful when a component represents an aggregation of many real resources, and you don't want some dependent resource to be created until that entire aggregation finishes being created.

The second is that we now 'lift' members of a POJO object when you have an

Output

wrapping that object. i.e. instead of neeing to write code like:

certificate.domainValidationOptions.apply(d => d[0].resourceRecordName) // you can now just write 
certificate.domainValidationOptions[0].resourceRecordName

This works for array-accesses, and property member lookups.

However, as part of this work, some changes we made to the

@pulumi/pulumi

package are of the sort that will not necessarily play well if prior versions of that same package are loaded into an app. For example, if you reference this new

0.17.x

version of

@pulumi/pulumi

it won't necessarily work properly if you have a library that ends up pulling in an

0.16.x

version. This is because hte 0.16.x version won't properly keep track of things like the component-dependencies. Nor will it properly allow you to lift those members. Because of the problems and confusion this could cause, we have updated

pulumi

to warn if you run an app that mixes/matches across these versions.

To ensure that you can move forward, we've rev'ed all our

@pulumi/...

packages so that they refer to

@pulumi/pulumi

v0.17.x. If you'd like to try any of this out, please go ahead and let us know if you run into any problems. We tried to extensively test these changes across every library and use case we have ourselves. But it might be the case that we missed something that occurs in the wild.

We hope these changes will help improve the development experience when using Pulumi. Thanks much!

I am having issues instantiating a

new aws.ec2.NatGateway

, receiving the error:

error: aws:ec2/natGateway:NatGateway resource 'us-east-1c' has a problem: "allocation_id": required field is not set

I am providing to the input

allocationId

, a

pulumi.Output<string>

that is coming directly from a `new aws.ec2.Eip`'s

allocationId

output. I can't tell if this is a pulumi issue or not.

@lemon-spoon-91807 I have a problem with the simplification of outputs, or perhaps I am misunderstanding usage

Hey folks. I'm test-driving pulumi for robustness, and I got myself wedged. Used

pulumi init

to set up a gcp-typescript example dir, then deleted

~/.pulumi

(using local store). Now when I try to

pulumi up

after logging back into the local store, I get a plugin failure:

How do I unwedge things? The config directory still has a node_modules subdir that seems to contain the right pulumi modules, so I'm a bit lost.

am I able to use the New Relic TF provider with pulumi?

Okay, next problem. Having deleted the local store, I was expecting pulumi to notice the existing resources (e.g. VMs in GCP) and reconstruct the current state of the world, but

pulumi up

just blindly applied the recorded state diff (and then fails because some things exist already). Am I right that there's no way to read the true state of prod into a pulumi state and pick up from there?

ah, found an issue about adopting resources. Looks like slated for ~0.21.

Hi, is there a way to check if a k9s resource exists? Eg. if namespace exists, don't create it, but if it does not exist, create. I tried using Namespace.get, but it always returns a value

Hey is there a way to upload some code to an ec2 instance? I’m using userData but it’s throwing a gRPC error specifying that my file is larger than max

Hello, how to show the resources used by some stack?

$ pulumi  stack ls
NAME       LAST UPDATE  RESOURCE COUNT
demo-dev*  2 weeks ago  2
$ pulumi  stack rm demo-dev
This will permanently remove the 'demo-dev' stack!
Please confirm that this is what you'd like to do by typing ("demo-dev"): demo-dev
error: 'demo-dev' still has resources; removal rejected; pass --force to override

has typescript changed how it optimises away unused imports or something along those lines? i've just had pulumi delete a load of resources with the only changes being updating package versions. i've imported them more specifically and they're getting rebuilt.

Why does the kind-of-official installer script still the old 0.16.16 release? Output from a Dockerfile build run:

: RUN curl -fsSL <https://get.pulumi.com> | sh
 ---> Running in a5a1a92cdca4
=== Installing Pulumi v0.16.16 ===

Whereas homebrew updated to 0.17.1 a few days ago. You forgot to update the release in the https://pulumi.io/latest-version link.