pulumi-community #general

stocky-spoon-28903

08/07/2018, 6:15 PM

It’s a minor usability detail in the scheme of things but one that just cost me 15 minutes of looking at a type error

microscopic-florist-22719

08/07/2018, 6:16 PM

Ah, interesting. There's no support for this today, but I can't imagine that it would be too terribly difficult to add.

stocky-spoon-28903

08/07/2018, 6:18 PM

Ultimately I guess the different SDKs would have to treat it differently - I don’t know of a way to represent it in Go for example

microscopic-florist-22719

08/07/2018, 6:21 PM

That's right.

stocky-spoon-28903

08/07/2018, 6:23 PM

Actually breaking out the healthcheck argument into a custom type would make the error a lot better. I’ll do that later today.

stocky-spoon-28903

08/07/2018, 6:23 PM

As it is I got an error about the entire arguments struct

purple-appointment-43233

08/07/2018, 6:40 PM

Hey, so I have an (I think) interesting problem: I use Pulumi to construct a SpotFleetRequest, and if I change the contents of the request, pulumi will destroy the old one and create a new one. This will leave a period of time where I have zero spot instances running. I’d like to have some way to specify an orderly transition, ideally have the old spot instances drain out slowly while the new ones take their place.

white-balloon-205

08/07/2018, 6:59 PM

Pulumi will always create a replacement before it deletes the old resource. So if you are directly managing resources like Instances or Functions or Containers, you will get this orderly transition. However, I'm not off the top of my head sure what guarantees Spot Fleet makes around availability of instances at the time the fleet creation "succeeds". If it has not been designed to support this, it may require some extra work to handle this via Pulumi (or really via any system that coordinates Spot Fleets).

white-balloon-205

08/07/2018, 7:01 PM

Ahh - it looks like there is a

waitForFullfillment

which can be used to not register the creation as successful until the request has completed. That should ensure that the delete doesn't happen until the create suceeded in bringing up the new instances. https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/ec2/#property-waitforfulfillment

stocky-spoon-28903

08/07/2018, 7:02 PM

Something else I’ve seen people do in this specific case is have lambda manage effectively blue-green deployment of spot requests, and have {Terraform,Pulumi} adjust the lambda instead

stocky-spoon-28903

08/07/2018, 7:13 PM

Huh… Pulumi just handled my moving a bunch of resources between various components.

stocky-spoon-28903

08/07/2018, 7:13 PM

Without having to destroy and recreate them.

stocky-spoon-28903

08/07/2018, 8:59 PM

Fun little component that creates a bastion host in a fairly customizable manner: https://gist.github.com/jen20/730e392f8d8361f02f494b294f62d66c

💥 1

stocky-spoon-28903

08/07/2018, 9:38 PM

Just ran into a new (to me) panic that doesn’t really give any description of where things are: https://gist.github.com/jen20/8cd9ce3b7687a22ad2a0f7f0331601dd

stocky-spoon-28903

08/07/2018, 9:41 PM

Working to find a minimal repro at the moment

adamant-restaurant-73893

08/07/2018, 10:18 PM

For those of you who signed up for tshirts, looks like the inventory is finally ready and they're shipping. 🎉 and thanks for your patience. If you still want a tshirt, just write some nice things here and we'll send one to you too. http://info.pulumi.com/community/give-me-a-tshirt

adamant-restaurant-73893

08/07/2018, 10:19 PM

Also, if you're speaking at local meetups or similar, let me know, and I'll hook you up with stickers.

strong-helicopter-19655

08/08/2018, 1:19 PM

Are there size/fit options?

adventurous-jordan-10043

08/08/2018, 2:35 PM

yes 🙂

stocky-spoon-28903

08/08/2018, 2:56 PM

Is there a complelling reason not to set

--parallel

to a higher default at the moment?

stocky-spoon-28903

08/08/2018, 3:13 PM

Although interestingly it doesn’t make the difference I would have expected set to 5

incalculable-sundown-82514

08/08/2018, 3:18 PM

That’s interesting - what did you see?

stocky-spoon-28903

08/08/2018, 3:19 PM

Basically serial operation on update, preview seemed faster

stocky-spoon-28903

08/08/2018, 3:20 PM

Not sure if the structure of my program is making that happen though

incalculable-sundown-82514

08/08/2018, 3:22 PM

ah, OK. You can use

pulumi stack graph

to see your program’s dependency graph - if we’re failing to parallelize independent nodes in the graph, that would be a bug for us

stocky-spoon-28903

08/08/2018, 3:57 PM

I’ll try to get a better idea of that shortly. I’m running the latest released version rather than from source now

white-balloon-205

08/08/2018, 3:58 PM

@stocky-spoon-28903 Note that - although there has been a

—parallel

flag since launch, it has not actually been fully wired through to run deployments in parallel. We just landed the first support for full deployment parallelism in master on Monday, and expect this to be enabled in the next release.

purple-appointment-43233

08/08/2018, 5:45 PM

Hey folks, so I did a

pulumi update

and it hung forever, so I double-ctrl-c and now I’m in an inconsistent state.

purple-appointment-43233

08/08/2018, 5:45 PM

What do I do? The provided link has no information

stocky-spoon-28903

08/08/2018, 6:38 PM

Is the idiomatic thing to do for unmet pre-conditions in a ComponentResource’s inputs to throw an exception?