give us a little while

or, a similar issue has been mentioned

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?

What are you trying to use it as the input to?

@stocky-spoon-28903 This will be passed to awsx.elasticloadbalancingv2.ApplicationLoadBalancer

Ah - that should probably be a

pulumi.Input<pulumi.Input<string>[]>

there

That way either the array or the elements can be Outputs

cc @lemon-spoon-91807 (though I know he is out of the office at the moment, so may be a while before he responds)

I see, would be good, because the stack exports just Output<string[]>

How should I lookup the endpoint of an existing ElasticSearch cluster?

How do we share a stack amongst team members in an organization aka how do we pull each other’s projects

is there a way to send custom arguments to the puluim binary eg/`pulumi preview -- foo=bar`

how can I change a passphrase for a pulumi stack?

Hi, I recently upgraded to the team starter edition, is it possible to migrate an existing stack under my user, to my organization?

Is there a way to grab the kubernetes server version of a cluster with the pulumi module?

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.

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 ?

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.

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.

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.

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?

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

Is there a way to view resources via cli?

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']
    })

x-posting from a thread in case anyone has experience with this: https://pulumi-community.slack.com/archives/C84L4E3N1/p1563995505114100?thread_ts=1563577662.042800&amp;cid=C84L4E3N1

How do I compare

Output<string>

with

string

? Here is the example

const clusterName = xyz
                .getOutput('cluster')
                .apply(cluster => cluster.ClusterName) as Output<string>;

The code has to compare the

clusterName

. I have tried with something like this and it failed.

switch (clusterName) {
            case Output.create('alpha'):{

Another secrets question: how can I test to see if a secret exists with a specific name? Should I use

aws.secretsmanager.getSecret({name: "foo"});

with a try-catch?

I’ve got an infrastructure diff between osx and linux on our infrastructure stack running the same code, same cli version. The linux execution (ci node) wants to replace our

provider

- making this a bad situation. We

pulumi refresh

on osx yesterday, my understanding is that would affect osx identical to our linux ci node. Who can help with this production issue?

Hi. Has anyone ever tried to remove an resource from a helm chart? I’m trying to install the

stable/grafana

chart but it is installing the tests too. I’d like to exclude them, but I can’t find a way to do it. Any suggestions?

I'm having a compile-time error that just started happening after I destroyed my stack and tried to recreate:

Invoke of 'aws:sqs/getQueue:getQueue' failed: undefined (undefined)

const queue = new aws.sqs.Queue( `${ config.namespace }_${ resourceName }` );

// get the queue's url
const queueUrl = pulumi.output( aws.sqs.getQueue( {
    name: queue.name,
} ) ).apply( v => v.url );

// get the queue's arn
const queueArn = pulumi.output( aws.sqs.getQueue( {
    name: queue.name,
} ) ).apply( v => v.arn );

module.exports = () => queue;
module.exports.arn = queueArn;
module.exports.url = queueUrl;