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
  • s

    salmon-beard-79336

    07/22/2019, 11:39 AM
    what is the difference between
    diff
    and
    check
    in a custom Resource?
    b
    • 2
    • 2
  • i

    important-leather-28796

    07/22/2019, 4:04 PM
    Hey I’ve got something strange. As part of our ci, we run
    preview
    and while we have not made changes, we just had a change pop up as part of our
    infrastructure
    stack that looks pretty ominous. Am I correct in thinking this is going to update the cluster and delete/recreate all that is listed here as
    replace
    ? This seems like it would be a very bad/production downtime event…wouldn’t it?
    m
    • 2
    • 10
  • i

    incalculable-lock-7238

    07/22/2019, 4:11 PM
    so anyone try to integrate this : https://github.com/atomita/fluent-plugin-aws-elasticsearch-service
    s
    • 2
    • 1
  • v

    victorious-ambulance-28127

    07/22/2019, 5:42 PM
    Hi. I was hoping you might be able to help me. I am experiencing the issue that I am unable to delete/destroy an AWS SSM Document. It appears the issue was raised in a ticket. It appears the issue was fixed and the ticket has been closed https://github.com/pulumi/pulumi-aws/issues/649. I tried upgrading to the latest version of Pulumi but I guess this fix is not part of this version. Is it possible to provide any details when how/when I can see this fix? Thanks for your help.
    b
    • 2
    • 33
  • g

    glamorous-printer-66548

    07/22/2019, 8:04 PM
    We're facing an issue with dynamic kubernetes provider instances when upgrading pulumi versions. I can't precisely say which version this started to occur, but I believe it first occured when upgrading CLI from 0.17.16 > 0.17.24 and "@pulumi/kubernetes": "0.22.0", > "@pulumi/kubernetes": "0.25.2", . Basically what happens is the after the upgrade pulumi attempts to replace all our dynamic kubernetes provider instances incl. all resources that have been created using it, even though we made no changes to the stack resources. After a bit debugging I found the issue is that previously our stack state only contained this:
    {
                    "urn": "urn:pulumi:my-stack::my-stack::pulumi:providers:kubernetes::my-cluster",
                    ...
                    "inputs": {
                        "kubeconfig": "...",
                        "namespace": "my-namespace"
                    }
                    ...
                }
    and after the upgrade pulumi wants to converge to this state:
    {
                      "urn": "urn:pulumi:my-stack::my-stack::pulumi:providers:kubernetes::my-cluster",
                    ...
                    "inputs": {
                        "kubeconfig": "...",
                        "namespace": "my-namespace"
                    },
                    "outputs": {
                        "kubeconfig": "...",
                        "namespace": "my-namespace"
                    }
                    ...
                },
    As you can see after the upgrade suddenly an "outputs" section that wasn't there before is being added. Because it didn't exist before pulumi attempts to do a replacement. I can workaround the issue by copying the "inputs" and pasting them as "outputs" and importing the fixed state.json which I did for a few stacks but since we have almost 100 stacks this is not a scalable solution. Is this a known issue and is there a better solution to the problem? I can btw reproduce this problem quite consistently (my machine, other machines, CI).
  • b

    broad-dog-22463

    07/22/2019, 8:06 PM
    @glamorous-printer-66548 this has been reported by another user - we are talking about this
    g
    m
    • 3
    • 4
  • b

    broad-dog-22463

    07/22/2019, 8:06 PM
    give us a little while
  • b

    broad-dog-22463

    07/22/2019, 8:06 PM
    or, a similar issue has been mentioned
  • a

    adamant-dress-73325

    07/22/2019, 9:19 PM
    Hi all, I am trying to use the following to reference a VPC created on another stack:
    const qaVpc = awsx.ec2.Vpc.fromExistingIds("blah-api-docs-qa-vpc", {
        vpcId: qaVpcId,
        privateSubnetIds: vpcPrivateSubnetIds
    });
    But this gives me a type error. I have a
    pulumi.Output<string[]>
    but the input args want a
    pulumi.Input<string>[]
    , how can I get the types to line up?
  • s

    stocky-spoon-28903

    07/22/2019, 9:21 PM
    What are you trying to use it as the input to?
  • a

    adamant-dress-73325

    07/22/2019, 9:22 PM
    @stocky-spoon-28903 This will be passed to awsx.elasticloadbalancingv2.ApplicationLoadBalancer
  • s

    stocky-spoon-28903

    07/22/2019, 9:23 PM
    Ah - that should probably be a
    pulumi.Input<pulumi.Input<string>[]>
    there
  • s

    stocky-spoon-28903

    07/22/2019, 9:23 PM
    That way either the array or the elements can be Outputs
  • s

    stocky-spoon-28903

    07/22/2019, 9:23 PM
    cc @lemon-spoon-91807 (though I know he is out of the office at the moment, so may be a while before he responds)
  • a

    adamant-dress-73325

    07/22/2019, 9:23 PM
    I see, would be good, because the stack exports just Output<string[]>
    l
    e
    • 3
    • 13
  • m

    modern-bear-85657

    07/22/2019, 10:30 PM
    How should I lookup the endpoint of an existing ElasticSearch cluster?
    b
    • 2
    • 4
  • i

    incalculable-lock-7238

    07/22/2019, 10:45 PM
    How do we share a stack amongst team members in an organization aka how do we pull each other’s projects
    g
    • 2
    • 22
  • g

    glamorous-waitress-51149

    07/23/2019, 8:09 AM
    is there a way to send custom arguments to the puluim binary eg/`pulumi preview -- foo=bar`
    c
    m
    • 3
    • 3
  • b

    bored-river-53178

    07/23/2019, 12:40 PM
    how can I change a passphrase for a pulumi stack?
    c
    m
    • 3
    • 7
  • a

    adamant-dress-73325

    07/23/2019, 3:40 PM
    Hi, I recently upgraded to the team starter edition, is it possible to migrate an existing stack under my user, to my organization?
    c
    • 2
    • 2
  • m

    millions-judge-24978

    07/23/2019, 6:30 PM
    Is there a way to grab the kubernetes server version of a cluster with the pulumi module?
    g
    • 2
    • 5
  • s

    swift-painter-31084

    07/23/2019, 8:04 PM
    I have a fargate image that keeps getting rebuilt on every update even if its completely unchanged. Is there anything I can do to suppress that? Its a minor annoyance, but increases update times significantly.
    b
    m
    +2
    • 5
    • 7
  • d

    damp-book-35965

    07/23/2019, 10:05 PM
    Hello..I noticed that
    pulumi preview --config
    is missing but
    pulumi up --config
    exists..I'm on pulumi version
    v0.17.17
    Has this been fixed in the more recent versions ? Is this intentional ?
    c
    g
    • 3
    • 4
  • b

    bitter-island-28909

    07/24/2019, 2:24 PM
    Does anyone have any tips or tools on how to properly determine the permissions required to deploy a Pulumi stack? I’ve been using full admin when deploying just because it’s guaranteed to work, but it feels like it violates the principle of least privilege. Obviously Pulumi needs the ability to create resources of (potentially) any type, and delete resources which it created. But it would be nice to find a role that prevented it from doing other potentially nefarious things, like destroying backups or logs.
  • c

    cool-egg-852

    07/24/2019, 4:42 PM
    Running into an issue. Pulumi is creating a resource and then deleting it right after thinking it’s doing the replacement right. This is for a gcp.compute.NetworkPeering resource.
    b
    • 2
    • 9
  • e

    early-musician-41645

    07/24/2019, 5:19 PM
    Anyone have experience you can share with creating SSH keypairs via Pulumi? I'm not interested in the ec2.keypair, but rather generating SSH public & private keys that I'll store in secretmanager, and then later use for EC2, as well.
    b
    • 2
    • 6
  • i

    incalculable-angle-91273

    07/24/2019, 5:38 PM
    Does anyone know of a clean way to delete a kubernetes resource that wasn’t created with pulumi? My use case is this: EKS spins up with a default PodSecurityPolicy that is completely permissive. My goal is to create a custom PSP and then delete the autogenerated one, in that order. Is this a good use case for a dynamic provider?
  • l

    loud-nest-15724

    07/24/2019, 6:12 PM
    hey all, hope this is the right place to ask this question. I'm trying to use the s3 website sample from the examples repo, but I'm getting an error when trying to preview or deploy a stack
    Previewing update (testing):
    
         Type                 Name                      Plan     Info
         pulumi:pulumi:Stack  aws-js-s3-folder-testing           1 error; 13 messages
    
    Diagnostics:
      pulumi:pulumi:Stack (aws-js-s3-folder-testing):
        error: Unrecognized flag --query-mode
        usage: RUN <flags> [program] <[arg]...>
            where [flags] may include
                --project=p         set the project name to p
                --stack=s           set the stack name to s
                --config.k=v...     set runtime config key k to value v
                --parallel=p        run up to p resource operations in parallel (default is serial)
                --dry-run           true to simulate resource changes, but without making them
                --pwd=pwd           change the working directory before running the program
                --monitor=addr      [required] the RPC address for a resource monitor to connect to
                --engine=addr       the RPC address for a resource engine to connect to
                --tracing=url       a Zipkin-compatible endpoint to send tracing data to
            and [program] is a JavaScript program to run in Node.js, and [arg]... optional args to it.
    
        error: an unhandled error occurred: Program exited with non-zero exit code: 255
    the version of the pulumi cli is v0.17.25 and the node version is v10.16.0
    b
    • 2
    • 20
  • n

    nice-airport-15607

    07/24/2019, 6:48 PM
    Is there a way to view resources via cli?
    w
    • 2
    • 3
  • m

    modern-bear-85657

    07/24/2019, 7:12 PM
    Why is this AMI lookup so slow? Can it be optimized?
    const ami = await getAmi({
            mostRecent: true,
            nameRegex: `amzn2-ami-hvm-.*-x86_64-ebs`,
            owners: ['amazon']
        })
    s
    • 2
    • 1
Powered by Linen
Title
m

modern-bear-85657

07/24/2019, 7:12 PM
Why is this AMI lookup so slow? Can it be optimized?
const ami = await getAmi({
        mostRecent: true,
        nameRegex: `amzn2-ami-hvm-.*-x86_64-ebs`,
        owners: ['amazon']
    })
s

salmon-account-74572

07/24/2019, 7:13 PM
I haven't tried this in Pulumi yet, but in the AWS CLI you can submit filters that are processed server-side (via the
--filters
command line option). Maybe there's something similar for this function?
View count: 2