THANKS!

sup

Am I missing something obvious, or is there not a way to set environment variables for an

aws.serverless.Function

?

I do not think you are missing something obvious, @stocky-spoon-28903, while

aws.lambda.Function

exposes an environment property, we do not expose a similar property on

aws.serverless.Function

. I believe it would be as simple as adding

environment?: string[]

to

aws,serverless.FunctionOptions

and threading it down. Does that sound right @white-balloon-205 or I am missing something subtle here?

We've released Pulumi 0.14.1! More details in #announcements. Happy weekend hacking to all! 🙂

Is there an equivalent term for "chart" in pulumi? For example if I were making a contained component for Nginx-Ingress or something? "pulumi-module-nginxingress"?

I noticed today that when pulumi serializes a function it doesn't ignore commented out lines and tries to actually work with them

Also I worked out that serializing lodash appears to fail because in lodash they often do things like

var isArray = Array.isArray

and then pulumi can't work with that because isArray serializes as

function isArray() { [native code] }

I'm not 100% sure, but I think if they had just kept it as

Array.isArray

a serialization wouldn't be attempted (correct me if I'm wrong)

I'm not a javascript guru enough to know a solution around this

note: this doesn't affect code that uses

require('lodash')

within the actual function closure because pulumi interprets that differently and doesn't try to serialize anything. It's only if you use

import

or

require

outside of the function closure and then use that imported library within the closure

I found a couple of related issues so I'll watch progress on those. https://github.com/pulumi/pulumi-aws/issues/249

Thanks @big-soccer-75859, please do let us know if you see anything not captured by that bug. Generally speaking, importing on the inside of a function should work around most (all?) of these issues. I realize, however, that this isn't idiomatic and what we would all write by default, so we will be spending some time next week discussing what to do here. Earlier on, we serialized modules differently -- so they led to actual requires during deserialization -- and it feels like this would address all of the issues we are seeing. Stay tuned and thanks for the great feedback!

Given this post: https://medium.com/@serverpunch/why-you-should-not-use-google-cloud-75ea2aec00de How would this manifest with Pulumi?

Is that not independent of provisioning mechanism?

If I’m understanding correctly, this is the machinery of gcloud threatening to deactivate people’s infrastructure. This is orthogonal to pulumi.

Does anyone know if the Terraform TLS provider or similar has been integrated into Pulumi?

@important-jackal-88836 I don’t believe anything like that has been done yet. Some folks have done a little work around pulimifying some other existing terraform providers and if it’s something you’re interested in trying, we can point you at some examples.

For an existing Terraform Resource Provider (like TLS); you can also use Terraform Bridge; see https://github.com/pulumi/pulumi-terraform/blob/master/README.md for a description of the overall structure and process of adding a new provider using the bridge and https://github.com/pulumi/pulumi-aws/blob/master/resources.go for a specific example.

😞 I'm like 45 minutes into trying to get this building in a container. Does anyone have a Dockerfile that builds from source reliably? Even with

make ensure

I'm getting missing go dependencies when I run

make

.

huh weird.

I don’t.

by “this” you mean pulumi/pulumi

?

yeah, looks like

make ensure

doesn't call

dep ensure

.

weird, my understanding is that it shoudl.

just added

dep ensure &&

in front of

make ensure && make

and it definitely got farther. I was going to look at source but I don't want to dig into common.mk for now if I can help it

I'm losing track of every thing I'm having to add though, maybe it was when I was still

go get ...dep

instead of

...dep/cmd/dep

can you share your dockerfile?