https://pulumi.com logo
Docs
Join the conversationJoin Slack
Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-cdk
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumi-service
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by Linen
general
  • c

    creamy-potato-29402

    03/06/2019, 7:28 PM
    You’re calling a method on an object that is null.
    c
    • 2
    • 6
  • i

    important-leather-28796

    03/06/2019, 8:25 PM
    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?
    w
    s
    • 3
    • 7
  • l

    lemon-greece-30910

    03/06/2019, 9:28 PM
    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,
            }
        );
    c
    • 2
    • 30
  • a

    adventurous-night-54654

    03/06/2019, 10:03 PM
    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
    • 1
    • 2
  • e

    early-musician-41645

    03/06/2019, 10:26 PM
    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
    g
    • 2
    • 7
  • h

    helpful-advantage-49286

    03/06/2019, 11:38 PM
    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
  • h

    helpful-advantage-49286

    03/06/2019, 11:38 PM
    (This is on GCP)
  • h

    helpful-advantage-49286

    03/06/2019, 11:38 PM
    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?
    c
    s
    • 3
    • 32
  • g

    glamorous-printer-66548

    03/07/2019, 2:36 AM
    @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.
    g
    • 2
    • 2
  • l

    lemon-spoon-91807

    03/07/2019, 8:00 AM
    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).
  • l

    lemon-spoon-91807

    03/07/2019, 8:01 AM
    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.
    🤩 4
  • l

    lemon-spoon-91807

    03/07/2019, 8:03 AM
    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
    👍 5
    👏 3
  • l

    lemon-spoon-91807

    03/07/2019, 8:03 AM
    This works for array-accesses, and property member lookups.
  • l

    lemon-spoon-91807

    03/07/2019, 8:04 AM
    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.
  • l

    lemon-spoon-91807

    03/07/2019, 8:07 AM
    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.
  • l

    lemon-spoon-91807

    03/07/2019, 8:08 AM
    We hope these changes will help improve the development experience when using Pulumi. Thanks much!
    😛ulumipus-8bit: 2
    💯 4
    ❤️ 3
  • m

    millions-judge-24978

    03/07/2019, 3:30 PM
    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.
    l
    • 2
    • 5
  • i

    important-leather-28796

    03/07/2019, 9:21 PM
    @lemon-spoon-91807 I have a problem with the simplification of outputs, or perhaps I am misunderstanding usage
    l
    • 2
    • 47
  • a

    alert-fish-36749

    03/07/2019, 9:43 PM
    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:
  • a

    alert-fish-36749

    03/07/2019, 9:44 PM
    -.txt
  • a

    alert-fish-36749

    03/07/2019, 9:44 PM
    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.
    c
    • 2
    • 6
  • q

    quaint-queen-45003

    03/07/2019, 9:53 PM
    am I able to use the New Relic TF provider with pulumi?
    c
    g
    +2
    • 5
    • 21
  • a

    alert-fish-36749

    03/07/2019, 10:03 PM
    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?
  • a

    alert-fish-36749

    03/07/2019, 10:07 PM
    ah, found an issue about adopting resources. Looks like slated for ~0.21.
    • 1
    • 1
  • f

    faint-vegetable-61837

    03/07/2019, 10:07 PM
    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
    c
    • 2
    • 3
  • h

    hallowed-king-98702

    03/07/2019, 10:50 PM
    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
    c
    l
    b
    • 4
    • 94
  • f

    fresh-chef-62390

    03/08/2019, 12:55 AM
    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
    g
    • 2
    • 3
  • b

    better-rainbow-14549

    03/08/2019, 9:27 AM
    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.
    w
    s
    • 3
    • 4
  • s

    sticky-bear-14421

    03/08/2019, 1:12 PM
    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.
  • s

    sticky-bear-14421

    03/08/2019, 1:16 PM
    That link still provides the 0.16.16 version
Powered by Linen
Title
s

sticky-bear-14421

03/08/2019, 1:16 PM
That link still provides the 0.16.16 version
View count: 1