I agree lol

are stack configs not uploaded along with the stack to app.pulumi.com? i.e. should we be adding the stack specific yaml to git

New blog from @lemon-spoon-91807 on

cloud.HttpServer

https://blog.pulumi.com/running-a-serverles-nodejs-http-server-on-aws-and-azure

Why would one call a function to do serverless web app Http Server. Great post btw!

This is awesome!

On the front of converting callbacks to lambda/functions. AFAIK one has to

require

any modules inside the callback. How do I make instances reusable between requests then, e.g. a request with a static agent?

AFAIK one has to

require

any modules inside the callback.

This is no longer true actually (as of a couple releases ago).

How do I make instances reusable between requests then, e.g. a request with a static agent?

What do you have in mind here exactly? Code that only runs once per warm-up, not once per request?

BTW - I added an example showing this

cloud.HttpServer

at https://github.com/pulumi/examples/tree/master/cloud-js-httpserver.

How would I go about installing the CLI that includes this PR https://github.com/pulumi/pulumi/pull/2000?

anyone know why circleci wont display ANSI colors for pulumi? 😢

More on the CLI automation front: I'd like a way to list stacks in a JSON format. i.e.

pulumi stack ls --json

.

@creamy-potato-29402 @white-balloon-205 opened an issue for something we had earlier a conversation in slack: https://github.com/pulumi/pulumi/issues/2014

@glamorous-printer-66548 thanks, I really appreciate the follow-up.

Why does

pulumi stack ls

return a stack name with a

*

appended to the stack name? i.e.

NAME                                             LAST UPDATE              RESOURCE COUNT     URL
ComputeSoftware/datomic-prod*                    n/a                      n/a                <https://api.pulumi.com/ComputeSoftware/datomic-prod>

It is the currently selected stack.

Ah. I'd suggest a more explicit way than that. Perhaps

ComputeSoftware/datomic-prod (selected)

.

It also makes parsers slightly more complicated...

Should this really be considered an error?

$ pulumi stack output --stack ComputeSoftware/datomic-prod
error: current stack has no output properties

Ran this on CircleCI and got an error. Any ideas?

$ pulumi stack output --stack ComputeSoftware/datomic-prod
error: inappropriate ioctl for device

@microscopic-florist-22719 @big-piano-35669 little reminder about https://github.com/pulumi/pulumi-gcp/issues/49 🙂 . On that note I think it would be cool if you could automate pulling in changes from upstream terraform providers a bit. Maybe some kind of bot which creates PRs with the upstream changes and that just needs to be accepted by a pulumi member?

Found an interesting race condition wrt to resource creation / deletion in pulumi gcp. Wondering if this part of a bigger pulumi core issue that is tracked somewhere else? https://github.com/pulumi/pulumi-gcp/issues/50

any hacks to simulate

terraform state mv

? (I’m using pulumi cloud for state management) I moved my app resources inside a Pulumi Component, it looks nice with the nesting in the previews but I’d rather not have to delete the underlying resources it wants to recreate

Enjoying

kubespy

? Keen to know how

Deployment

works in Kubernetes? More importantly, would you like some awesome GIFs? Part 3 of @creamy-potato-29402’s series on observing Kubernetes resources is here: https://blog.pulumi.com/how-do-kubernetes-deployments-work-an-adversarial-perspective

OK... @big-piano-35669 fixed the router 🔌, @white-balloon-205 is all fired up 💪 , I figured out how to use YouTube properly 📺, and so we're totally confident we'll get this week's live stream out at 11am PDT - 44 minutes time to talk Serverless programming. Join us then:

We'll be live in 2 minutes ^^

Let's see how @white-balloon-205 copes with the incoming FEMA test alert at 11:18. Worth tuning in just for that. Ssssshhh.

@white-balloon-205 is australian, maybe they didn’t send it to him

any idea why my nesting is off? I’m expecting the ecr repos to be children of

standard:Build

class Build extends pulumi.ComponentResource {
  constructor(name, opts) {
    super("standard:Build", name, {}, opts)

    let repository = new getEcrRepository(name, this)
    let ecrRepoPolicy = repository.repositoryPolicy
    let ecrLifecyclePolicy = repository.lifecyclePolicy
  }
}

getEcrRepository = function(name, parent) {
  repository = new aws.ecr.Repository(name, { parent: parent })
...

i’m seeing some weird behavior with route 53 creating a TXT record on an apex domain. non-apex domain txt records seem to work fine, but when i create an apex record, like for SPF or similar, the creation succeeds, i get a valid resource id, but the domain doesn’t appear in route 53 & doesn’t get returned when i

dig TXT

the server

any idea what might be going wrong? thanks!