Hey guys, I just recently discovered Pulumi and was instantly convinced by the idea behind it. I just got around to trying it out and noticed that there is no terraform-equivalent of a "file" or "locale/remote-exec" provisioner. So I was wondering how people are dealing with this, since getting a file on a server and then executing something seems like a pretty common use case

I'm trying to build a docker image and push it to a local private docker registry and then to Kubernetes, similar to the example here: https://blog.pulumi.com/program-kubernetes-with-11-cloud-native-pulumi-pearls#8__Build_and_Deploy_Container_Images_A_longside_Configuration_Updates_322 I got it to build and push the docker registry, but when I try to deploy it Kubernetes, I get the following error:

kubernetes:apps:Deployment lds updating warning: 1 Pods failed to run because: [ImagePullBackOff] Back-off pulling image "127.0.0.1:5000/api_gateway_go:f61cb689da..."

. I suspect it's because the credentials are not passed on. Is there some magic way to pass Docker private registry credentials to Kubernetes? Or I need to do something manually similar to what in https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

FYI - https://github.com/pulumi/eks/issues/18 I've only started seeing this recently. Wasn't a problem last week, AFAIK. I can share the entire contents of the system logs if needed

@creamy-potato-29402 re pulumi’s replacement strategy when an k8s secret / configmap has changed: Currently it seems pulumi always first deletes the old deployment completely and then creates a new one, which is very disruptive to deployments which need to be up all the time. Isn’t it possible to simply inject some hash into the deployment’s annotations to force a rolling update instead of deleting and recreating the entire thing?

hi, is "pulumi config" ablet to handle nested keys, like

foo:bar:hello: "world"

? as far as I see it can't, only simple keys, like

foo:bar: "world"

btw, I saw there's some backward compatible logic when fetching config values(removing of the ":config" part), played with it a little and it seems like a bug

what does the "doNotCapture" setting do exactly? not really clear when should I use that when working with ComponentResources, e.g. the aws-infra repo set this to true: https://github.com/pulumi/pulumi-aws-infra/blob/master/nodejs/aws-infra/cluster.ts#L340, but in the eks code, Cluster, which is a ComponentResource too, does not set this: https://github.com/pulumi/eks/blob/master/nodejs/eks/cluster.ts

I've just updated pulumi from 0.15.4 to latest... and it wants to replace all my azure resources. I assume this is the role.assignment -> role.Assignment change... is there a way to patch my state file rather than actually replacing everything?

writing onboarding docs for our team. Up until now I was always using a service account with the JSON file for passing to GOOGLE_CREDENTIALS. I'd rather in our dev environment that we can auth with our own GCP/GCloud creds. How does this work? Or is this a bad idea and we should have one or many service accounts for development work?

anyone know what might cause this?

hello all, i’m new to pulomi. I’m trying to use the getAccount function to get information about an already created service account in gcp. It looks like I’m passing the correct arguments but when I try to access the

.email

property it says it does not exist. How do I resolve this?

Trying to understand what Pulumi wants to delete:

pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:deploy-dev::deploy::pulumi:pulumi:Stack::deploy-deploy-dev]
    - docker:image:Image: (delete)
        [urn=urn:pulumi:deploy-dev::deploy::docker:image:Image::dashboard-server]

I'm using an ECR on AWS to store images. Is it going to delete the image?

Tomorrow (7th November) at 11am PST our regular live stream will resume as @white-balloon-205 talks about some of the interesting and popular conversations in this channel in recent weeks. If you'd like your issue discussed, let us know, and join here at 11am and at

Really confused by

pulumi config <key1> <value>

and

new pulumi.Config(<key2>).get(<key3>)

. What is the value of

key2

? For example, I want to set the value "foo:bar" to "baz". How would I retrieve "foo:bar" in code?

oh i c -

key2

is the namespace. So

key1

would be

foo:bar

,

key3

would be

bar

and

key2

would be

foo

.

And if no namespace is provided (

key2

is absent,

key1

is

bar

), then the project name is the namespace.

@creamy-potato-29402 create/replace on a statefulset that had a service as a child

kubernetes:apps:StatefulSet (XXXXXXX-1252):
    error: post-step event returned an error: failed to verify snapshot: child resource urn:pulumi:X-XXXXXXXXdev::XXXXXXXXXX::standard:Deploy$kubernetes:apps/v1:StatefulSet$kubernetes:core/v1:Service::XXXXXXXX-1252 refers to missing parent urn:pulumi:XXXXXXXX-dev::XXXXXXXX::standard:Deploy$kubernetes:apps/v1:StatefulSet::XXXXXXXX-1252

same thing happened to the autoscaling resource, which also had the statefulset as its parent

Hi everyone! I began to use pulumi and I have a newbie question: I need to create a s3 bucket with a fixed name (not stack dependant). How do I prevent pulumi for suffixing the bucket name with a unique identifier ?

i think i asked that like a week ago

should be the second arg in the constructor, add

name

there

@helpful-continent-74245

const bucket = new aws.s3.Bucket("my-bucket", { name: "my-bucket" });

@busy-umbrella-36067 Thanks a lot, trying that right away!

its the

args

param, https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/s3/#Bucket

Would love to see

Pulumi.all(Record<string, Input<T>>)

overloaded to a set of keys - i.e.,

Pulumi.all(Record<K, Input<T>>)

. I have a function that returns

Output<{http: Listener, https: Listener}>

. Using

Pulumi.all

as is, I had to write

pulumi.all({ https, http }).apply(({ http, https}) => ({ http, https}));

(where

http

and

https

are local variables of type

Output<Listener>

). Notice the extra

apply

.

pulumi.all({http, https})

has type

Output<Record<string, Listener>>

, but

pulumi.all(...).apply(...)

has type

Output<{http: .., https:...}>

which keeps my keys. Or maybe I want

Pick

?

Record

confuses me still.

What I really wanted was

pulumi.all({http, https}): Output<{http: ..., https: ,,,}>

CircleCI announced their 'Orbs' feature this morning (reusable CI/CD components). "Is there a Pulumi orb?", you may ask. Why yes - @square-apartment-28429 is the mail man https://blog.pulumi.com/reusable-cicd-components-with-circleci-orbs-for-pulumi

@adamant-restaurant-73893 I'm just gettign started with AWS CodePipeline/CodeBuild. CodePipeline seems to be really inflexible, but its advantage is staged pipelines where you can pause execution (for example, to do manual testing) before deploying to production. Does pulumi offer a way to do staged pipelines that I'm missing, just using codebuild? Or would CircleCI offer a better experirence?

Office Hours in 10 mins with @white-balloon-205 -- will he talk about the thread/issue you were on? Can you confuse him with new issues in real time?