I eventually found the

Dockerfile

source (https://github.com/pulumi/pulumi/blob/master/dist/docker/Dockerfile) Always good to know how it was built, so it would be nice if it was linked to from https://hub.docker.com/r/pulumi/pulumi.

Another suggestion after first contact, change

<http://get.pulumi.com|get.pulumi.com>

to curl silently. 😛

...
Step 4/5 : RUN curl -fsSL <https://get.pulumi.com> | bash -s -- --version $PULUMI_VERSION     && mv ~/.pulumi/bin/* /usr/local/bin     && pulumi version
 ---> Running in 8435a5532c49
=== Installing Pulumi v1.0.0 ===
+ Downloading <https://get.pulumi.com/releases/sdk/pulumi-v1.0.0-linux-x64.tar.gz>...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 46.3M  100 46.3M    0     0  29.2M      0  0:00:01  0:00:01 --:--:-- 29.2M
+ Extracting to /root/.pulumi/bin
...

Specifically to squash the "downloading" noise.

I've created a docker image, with Pulumi and node, and am trying out the remote editing features of Visual Studio Code. Excuse the stupid question, but is there a way to "step debug" the code, starting from

index.ts

and following along?

Hi 🙂 I have an EKS cluster created with pulumi, with some services / helm charts applied, I'm seeing the follow weirdness: When a helm chart is applied fresh, it creates an ELB and adds its security group to the node security group, and all works as expected. On a subsequent pulumu run, it says it want to update the node security group, and removes the rule so that the ELB can no longer reach the cluster. This also happens with a

Service

created without helm. I've recently upgraded pulumi to 1.0 - This cluster has been running for some time, and updates have been ok till now - although we did experience a similar thing when pulumi updated the AMI for the EKS cluster. Has anyone else observed something similar?

I dont know if it is GCP specific as we dont use other providers, but

new gcp.Provider("name", {project: "another-project"})

leaks ambient provider credentials into stack unencrypted

interface NodePoolNodeConfig {
        ...
        oauthScopes?: pulumi.Input<pulumi.Input<string>[]>;

nested

Input<>

, is it a problem with code generation or like that by design?

Is it possible to set Pulumi config variables via the command line tool? sort of like how the -var option is used in terraform

Hey all. Has anyone used GCP's KMS for secret storage? I'm not sure I'm configuring it correctly, as it keeps asking me for an encryption password; which I don't expect (and no provider information stored in stack yml)

Is the usage of Proximity Placement Groups for Azure Scale Sets in Pulumi dependent on the Terraform provider implementation?

Tried with AWS KMS too, same failure 😞

I'll create an issue

this error is pretty vague, anyone have an idea of what's going on here or how I can debug?

Created stack 'dev'
Previewing update (dev):
     Type                 Name              Plan     Info
     pulumi:pulumi:Stack  azurenetwork-dev           1 message
 
Diagnostics:
  pulumi:pulumi:Stack (azurenetwork-dev):
    error: It looks like the Pulumi SDK has not been installed. Have you run npm install or yarn install?
 
error: failed to load language plugin nodejs: could not read plugin [/Users/jonbrwn/.pulumi/bin/pulumi-language-nodejs] stdout: EOF

the above is from running

pulumi up

Have you run npm install or yarn install?

Doesn't seem that vague 🙂

should customTimeouts propagate from parent resource down? seems that it doesn't, at least not for the helm chart

Anyone seen this before:

Resources:
    ~ 1 updated
    1 unchanged

Duration: 7s

error: Could not get signed url for stack location: blob (code=Unknown): to use SignedURL, you must call OpenBucket with a valid Options.GoogleAccessID and exactly one of Options.PrivateKey or Options.SignBytes

Is there support for files other than

values.yml

for helm? As in, can Pulumi read from

values.prod.yml

for example?

I've got a deployment, that contains a container spec, that contains an

envFrom

with a reference to a secret's name. and it seems that makes the entire container spec secret, which means i get an empty output for the diff, so i can't see the image change. any way around that? where's the demarcation of what's marked secret? if i were to pass a

new k8stypes.core.v1.EnvFromSource

to

envFrom

instead of an array of hashes, would that work?

When creating an FSx windows fileshare is this code expected? https://github.com/pulumi/pulumi-aws/blob/12e670b7058a95d189b26e09a2864e3d7c210466/sdk/nodejs/fsx/windowsFileSystem.ts#L343 Currently it's:

/**
     * A list of IDs for the subnets that the file system will be accessible from. File systems support only one subnet. The file server is also launched in that subnet's Availability Zone.
     */
    readonly subnetIds: pulumi.Input<string>;

Shouldn't the type be

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

?

Why does dependsOn not work for depending upon the completion of a helm chart?

is there something I'm doing wrong for this

const vmss = azure.compute.ScaleSet.get("id-of-my-resource")

to fail with this error:

Error: Missing required property 'networkProfiles'
        at new ScaleSet (/Users/jonbrwn/code/other/pulumi-azure-import-test/node_modules/@pulumi/compute/scaleSet.ts:424:23)
        at Function.get (/Users/jonbrwn/code/other/pulumi-azure-import-test/node_modules/@pulumi/compute/scaleSet.ts:259:16)

when running

pulumi up

?

hey all, I’m trying to adopt an existing AWS CloudFormation Stack resource into Pulumi, along the lines of https://www.pulumi.com/blog/adopting-existing-cloud-resources-into-pulumi/ - I wasn’t sure what ID I should use. I started with the

arn:aws:cloudformation:...

ID from the AWS console but that gives me a “resource does not exist” error. is there a different ID I should be using? how can I find this?

Hi, I'm trying to create a lambda function that needs to execute a binary file. How do I make sure that pulumi packages that binary file into my lambda function?

I'm playing around with porting some code from Ansible to Pulumi. Am I missing something or is Pulumi config flat only? It would be great to have a config hierarchy with top-level defaults but allow for overrides per environment; otherwise I'll have to repeat the default config for every environment.

Looks like some config changes are coming soon (https://github.com/pulumi/pulumi/wiki/Roadmap#m27-september-2019) and hopefully some hierarchy changes will be considered too (https://github.com/pulumi/pulumi/issues/2307)

Hi! Is anyone out there building an Elastic Beanstalk stack with a Network Load Balancer? Is there away to get the load balancer that is automatically created via Elastic Beanstalk to be managed by Pulumi? Ultimately, what I need to do is to pass the load balancer URN to a VPCLink, but I don’t actually have the auto-created load balancer URN at runtime.