pulumi-community #general

Docs

Join the conversation Join Slack

general

red-football-97286

10/09/2019, 10:02 AM

Done some googling and looked like a bug a year ago.

red-football-97286

10/09/2019, 10:02 AM

I've done all the steps to install.

red-football-97286

10/09/2019, 10:03 AM

I'm on Windows

red-football-97286

10/09/2019, 10:29 AM

Sorted it now. I was using the wrong virtual environment for python.

nice-cat-91582

10/09/2019, 10:35 AM

https://pulumi-community.slack.com/archives/C84L4E3N1/p1570579979425900?thread_ts=1570568724.411700&cid=C84L4E3N1 Anyone have advice on how they're structuring lambda projects that use AssetArchives instead of magic functions? It seems like the only reasonable way to do it is having multiple

package.json

files - one for each function. I'm imagining this will get really messy on deploy, as I would need to

npm install

in every folder on every deploy

better-rainbow-14549

10/09/2019, 11:35 AM

I've just updated kubernetes from 1.1.0 to 1.2.1 and it wants to redeploy every configmap (from using binaryData property to data) and thus redeploy everything that uses those config maps. is that expected? will it actually redeploy things?

incalculable-engineer-92975

10/09/2019, 1:42 PM

Suggestion: add a 'clear' or 'reset' command for 'pulumi stack'. This would be equivalent to exporting the stack, removing all the resources and re-importing the stack. This should do a 'are you sure?' prompt. I need this on a semi-regular basis when someone destroys a sandbox cluster but forgets to do an istio destroy (or something else running on the cluster).

brief-yacht-31759

10/09/2019, 3:23 PM

Hey, keen to POC Pulumi. Have some best practice questions if that is ok. In general, how are people mapping git repos/branches to pulumi stacks to logical infrastructure environments (environments)? I suppose an initial approach could be to have a git repo, with a branch per environment, then have a pulumi stack per environment. Where I am working now, an environment is basically AWS components, helm/kubernetes components, and then ansible/bash for some glue, so I am keen to automate straight away and think about the CI pipeline for progressing changes through multiple environments straight away.

rhythmic-finland-36256

10/09/2019, 5:55 PM

Using

ComponentResource

with shared

ComponentResourceOptions

passed down to the child resources seems to mutate the options - which leads to confusing error messages of duplicate resource aliases. Do I need to construct a new options object for each child resource?

calm-greece-42329

10/09/2019, 7:37 PM

is there any tips on debugging this stall? i can run a refresh just fine, but

up

hangs at this point and i don’t know what is actually trying to do

calm-greece-42329

10/09/2019, 7:37 PM

this code used to run fine but its been a few weeks since i have run a command in here

calm-greece-42329

10/09/2019, 7:38 PM

or i can blame macos catalina 🙂

breezy-kangaroo-52717

10/09/2019, 11:48 PM

Is the CLI the only interface for pulumi engine? I am hoping to find an API I could use in my web application to call pulumi engine to execute my pulumi programs. How are people implementing such architectures currently if there's no API and CLI is the only way to interact with the pulumi engine?

acceptable-army-69872

10/10/2019, 5:15 PM

I've been playing with the client VPN stuff, and it seems like the features aren't really flushed out. You can create a client vpn, and associate it with a subnet, but you can't assign the security groups, manage the routes, or the authorization. Does that sound right? If so, it's better than nothing, but could be better.

worried-city-86458

10/10/2019, 8:55 PM

pulumi:pulumi:Stack (k8s-infra-dev):
    Error: The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
    Original error: Cannot find module '/workspaces/devops-gemini-pulumi/k8s-infra/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc/grpc_node.node'
    Require stack:
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/grpc/src/grpc_extension.js
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/grpc/src/client_interceptors.js
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/grpc/src/client.js
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/grpc/index.js
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/@pulumi/pulumi/runtime/settings.js
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/@pulumi/pulumi/log/index.js
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/@pulumi/pulumi/cmd/run/run.js
    - /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/@pulumi/pulumi/cmd/run/index.js
        at Object.<anonymous> (/workspaces/devops-gemini-pulumi/k8s-infra/node_modules/grpc/src/grpc_extension.js:43:17)
        at Module._compile (internal/modules/cjs/loader.js:936:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:947:10)
        at Module.load (internal/modules/cjs/loader.js:790:32)
        at Function.Module._load (internal/modules/cjs/loader.js:703:12)
        at Module.require (internal/modules/cjs/loader.js:830:19)
        at require (internal/modules/cjs/helpers.js:68:18)
        at Object.<anonymous> (/workspaces/devops-gemini-pulumi/k8s-infra/node_modules/grpc/src/client_interceptors.js:144:12)
        at Module._compile (internal/modules/cjs/loader.js:936:30)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:947:10)
 
    error: an unhandled error occurred: Program exited with non-zero exit code: 1

handsome-actor-1155

10/10/2019, 8:58 PM

One thing I keep forgetting to bring up is to ask if anyone has run into a bug(?) where the entry of the VPC exists but the name of vpc is empty in the aws console when creating a VPC from Pulumi? Code:

const vpc = new awsx.ec2.Vpc("demo-vpc", {numberOfAvailabilityZones: 3});

worried-city-86458

10/10/2019, 9:26 PM

message has been deleted

🎉 5

❤️ 3

worried-city-86458

10/10/2019, 10:18 PM

I'm trying to update the prometheus operator helm chart:

pulumi:pulumi:Stack (k8s-infra-dev):
    error: Error: Command failed: helm fetch stable/prometheus-operator --untar --version 6.16.0 --destination /tmp/tmp-333MmxKBHLF631a
    Error: chart "prometheus-operator" matching version "6.16.0" not found in stable index. (try 'helm repo update'). No chart version found for prometheus-operator-6.16.0
 
    Error: chart "prometheus-operator" matching version "6.16.0" not found in stable index. (try 'helm repo update'). No chart version found for prometheus-operator-6.16.0
    Error: Error: Command failed: helm fetch stable/prometheus-operator --untar --version 6.16.0 --destination /tmp/tmp-333MmxKBHLF631a
    Error: chart "prometheus-operator" matching version "6.16.0" not found in stable index. (try 'helm repo update'). No chart version found for prometheus-operator-6.16.0
        at /workspaces/devops-gemini-pulumi/k8s-infra/node_modules/@pulumi/kubernetes/helm/v2/helm.js:112:23
        at OutputImpl.<anonymous> (/workspaces/devops-gemini-pulumi/k8s-infra/node_modules/@pulumi/pulumi/output.js:110:47)
        at Generator.next (<anonymous>)
        at fulfilled (/workspaces/devops-gemini-pulumi/k8s-infra/node_modules/@pulumi/pulumi/output.js:18:58)

early-intern-90238

10/10/2019, 11:10 PM

Why does my GitHub have these status checks but only for one stack? Shouldn't it have a Status check for each stack? I am very confused...

breezy-butcher-78604

10/11/2019, 3:39 AM

hi all, i've run in to an issue trying to create an AWS VPC via AWS Crosswalk. I'm not doing anything complex, just trying to create a VPC with all the defaults:

import * as awsx from "@pulumi/awsx";

const vpc = new awsx.ec2.Vpc("my-vpc");

export const vpcId = vpc.id;

When I run

pulumi preview

I get the following error:

Previewing update (dev):

     Type                                    Name                Plan       Info
 +   pulumi:pulumi:Stack                     pulumi-vpc-test  create
 +   ├─ awsx:x:ec2:Vpc                       my-vpc              create
 +   │  ├─ awsx:x:ec2:NatGateway             my-vpc-0            create
 +   │  │  └─ aws:ec2:Eip                    my-vpc-0            create
 +   │  ├─ awsx:x:ec2:NatGateway             my-vpc-1            create
 +   │  │  └─ aws:ec2:Eip                    my-vpc-1            create
 +   │  ├─ awsx:x:ec2:InternetGateway        my-vpc              create
 +   │  │  └─ aws:ec2:InternetGateway        my-vpc              create
 +   │  ├─ awsx:x:ec2:Subnet                 my-vpc-public-0     create
 +   │  │  ├─ aws:ec2:RouteTable             my-vpc-public-0     create
 +   │  │  ├─ aws:ec2:Subnet                 my-vpc-public-0     create
 +   │  │  ├─ aws:ec2:Route                  my-vpc-public-0-ig  create
 +   │  │  └─ aws:ec2:RouteTableAssociation  my-vpc-public-0     create
 +   │  ├─ awsx:x:ec2:Subnet                 my-vpc-public-1     create
 +   │  │  ├─ aws:ec2:Subnet                 my-vpc-public-1     create
 +   │  │  ├─ aws:ec2:RouteTable             my-vpc-public-1     create
 +   │  │  ├─ aws:ec2:Route                  my-vpc-public-1-ig  create
 +   │  │  └─ aws:ec2:RouteTableAssociation  my-vpc-public-1     create
 +   │  ├─ aws:ec2:Vpc                       my-vpc              create
 +   │  ├─ awsx:x:ec2:Subnet                 my-vpc-private-1    create
 +   │  │  ├─ aws:ec2:RouteTable             my-vpc-private-1    create
 +   │  │  ├─ aws:ec2:Subnet                 my-vpc-private-1    create
 +   │  │  └─ aws:ec2:RouteTableAssociation  my-vpc-private-1    create
 +   │  └─ awsx:x:ec2:Subnet                 my-vpc-private-0    create
 +   │     ├─ aws:ec2:Subnet                 my-vpc-private-0    create
 +   │     ├─ aws:ec2:RouteTable             my-vpc-private-0    create
 +   │     └─ aws:ec2:RouteTableAssociation  my-vpc-private-0    create
     └─ aws:ec2:NatGateway                   my-vpc-1                       1 error

Diagnostics:
  aws:ec2:NatGateway (my-vpc-1):
    error: aws:ec2/natGateway:NatGateway resource 'my-vpc-1' has a problem: Missing required property 'subnetId'

if I downgrade to v1.2.0 (from 1.3.1) of the pulumi npm module with

npm install @pulumi/pulumi@1.2.0

everything works as expected, the preview completes fine and I can create the VPC without issues. I've had a brief look over the changes between the two versions (https://github.com/pulumi/pulumi-aws/compare/81eb5b...09758c) but there doesn't appear to be any changes to the nodejs code that could explain this. The only thing that seems likely is the change of the terraform provider version used. Has anyone else ran into this issue?

salmon-account-74572

10/11/2019, 5:43 AM

Are there specific words or values that should not be used as the name of a Pulumi project or stack?

cold-coat-35200

10/11/2019, 12:48 PM

hi, is it possible to define a deletion order for kubernetes resources, created from a helm chart? I'm facing a problem with the etcd-operator when using periodic backups. In this case, after the EtcdBackup CR created by pulumi, based on the helm chart, the etcd backup operator adds a finalizer to the EtcdBackup CR (there is no finalizer in the helm chart template). When trying to destroy the stack with pulumi, it's unable to delete the EtcdBackup CR, because the etcd backup operator already deleted(pulumi deletes the resources parallel), so the finalizer never be removed by the operator, therefore kubernetes unable to delete the resource If I destroy the EtcdBackup first with the new

--target

option, then the whole stack, it works fine

salmon-account-74572

10/11/2019, 3:53 PM

When using S3 to store the checkpoint files for Pulumi, it would appear that stack names must be unique across all projects. (I say this because I see stack names listed in

<bucket>/.pulumi/stacks

that aren't differentiated across projects.) Or is the recommendation to use a different S3 bucket for each project?

billions-lock-80282

10/11/2019, 3:54 PM

Hi, I have an issue when running pulumi preview, the stack just sits at 'create' and doesn't move past this. Is there any way of finding out whats happening behind the scenes?

busy-umbrella-36067

10/11/2019, 4:05 PM

Helm chart previews are now fast with the new Pulumi version 👏

🚀 1

🍺 1

early-intern-90238

10/11/2019, 4:06 PM

I actually can't stand Helm, I only use it if I don't have a choice...Way too unreliable...and the authors of the Helms don't seem to give two craps about breaking changes between revisions...

👆 1

early-intern-90238

10/11/2019, 4:07 PM

But having the support is obviously a nice thing to have when they are needed.

busy-umbrella-36067

10/11/2019, 4:08 PM

@early-intern-90238 Same boat here, but I get to avoid managing manifests for

external-dns

kiam

cert-manager

datadog

traefik

, etc...

early-intern-90238

10/11/2019, 4:12 PM

traefik is a good example of unavoidable

damp-pillow-67781

10/11/2019, 5:26 PM

Hi, I've run into the issue that pulumi up is hanging forever until I ctrl+c and stop it. It's on my newly provisioned centos7 machine. Any idea on why that's happenning? It runs fine on my mac.

➜  eks-cluster git:(develop) ✗ pulumi up --logtostderr -v=7 --debug 2> out.txt
Previewing update (tableau/online-sandbox-yding):

     Type                 Name                              Plan       Info
 +   pulumi:pulumi:Stack  eks-cluster-online-sandbox-yding  create...  debug: RegisterResource RPC finished: resource:eks-cluster-online-sandbox-yd

Title

damp-pillow-67781

10/11/2019, 5:26 PM

Hi, I've run into the issue that pulumi up is hanging forever until I ctrl+c and stop it. It's on my newly provisioned centos7 machine. Any idea on why that's happenning? It runs fine on my mac.

➜  eks-cluster git:(develop) ✗ pulumi up --logtostderr -v=7 --debug 2> out.txt
Previewing update (tableau/online-sandbox-yding):

     Type                 Name                              Plan       Info
 +   pulumi:pulumi:Stack  eks-cluster-online-sandbox-yding  create...  debug: RegisterResource RPC finished: resource:eks-cluster-online-sandbox-yd

gentle-diamond-70147

10/11/2019, 5:30 PM

Hi, what version of node are you running?

If you're on Node 12, can you try downgrading to Node 10 (the current LTS version) and see if you get the same issue?

damp-pillow-67781

10/11/2019, 5:30 PM

v12.11.1

Sure, will try

damp-book-35965

10/11/2019, 5:42 PM

I do think that the docs on the pulumi install page should recommend downloading the LTS version

It just says 8+ for now..

gentle-diamond-70147

10/11/2019, 5:43 PM

@damp-book-35965, agreed. I'll open an issue to update.

👍 2

damp-pillow-67781

10/11/2019, 5:47 PM

yeah downgrading to node 10 fixes it, thanks!

gentle-diamond-70147

10/11/2019, 5:47 PM

@damp-pillow-67781 thanks for confirming!

lemon-spoon-91807

10/11/2019, 6:05 PM

Thanks for the report. I'm working on a fix for this now

it's pri0 for us

should hopefully have build you can try out by monday

white-balloon-205

10/11/2019, 8:24 PM

Just to cross-reference - we are tracking this in https://github.com/pulumi/pulumi/issues/3309.

worried-city-86458

10/12/2019, 9:33 PM

v12 will be active LTS in just over a week

lemon-spoon-91807

10/12/2019, 9:39 PM

hi @worried-city-86458 We're working hard on a fix here.

I've got a PR for this here https://github.com/pulumi/pulumi/pull/3325 which should solve the issue entirely for most users.

worried-city-86458

10/12/2019, 9:40 PM

I’m sure you are. Much appreciated too!

lemon-spoon-91807

10/12/2019, 9:40 PM

This is top pri for us, and we hope to have the fix out asap.

We just want to make totally sure it's really the right approach and best thing for short/medium/long-term health for us and the community 🙂

worried-city-86458

10/12/2019, 9:43 PM

I’d be happy with async everywhere if / when top-level async (TLA) becomes available

lemon-spoon-91807

10/12/2019, 9:43 PM

Understood

Note: i have a PR to make things nicer in Pulumi prior to that happening

Specifically: https://github.com/pulumi/pulumi/pull/3321

This would allow for near top-level

await

with minimal syntactic cruft you need to add.

worried-city-86458

10/12/2019, 9:44 PM

Just hoping the door will stay open for TLA as deasync seemed to be about hiding those details

lemon-spoon-91807

10/12/2019, 9:45 PM

i love that TLA is itself a TLA (three letter acronym) 😄

worried-city-86458

10/12/2019, 9:47 PM

If C# support ever happens then I’d be really happy and expect use of async everywhere

lemon-spoon-91807

10/12/2019, 9:47 PM

It looks like V8, Nodejs and TypeScript are all working toward TLA. V8: https://v8.dev/features/top-level-await

i talked to the TS PM. They wanted it in the latest release, but it slipped slightly. Should be in the next one.

If C# support ever happens then I’d be really happy and expect use of async everywhere

Yup, that's on my plate. And that's my expectation for what would be happening.

worried-city-86458

10/12/2019, 9:49 PM

Cool. Fingers crossed for both TS and C# in future.

Just needs a library so these envs support launching outside Pulumi CLI so step debugging works.

lemon-spoon-91807

10/12/2019, 9:51 PM

Good point!

worried-city-86458

10/12/2019, 9:53 PM

Support for that would be very useful as you can learn a system much faster by debugging into it

lemon-spoon-91807

10/12/2019, 9:53 PM

note: i'm a personal fan of programs that you pass a debug flag to, and htey basically break at some point and allow you to attach a debuger then

then you don't have to worry "is this running differently depending on lib form versus cli form"

but thanks for all the feedback!

worried-city-86458

10/12/2019, 10:02 PM

No worries. Thanks for listening.

Re debug flag, that’s what Cake build (C# Make) does.

View count: 1