Found a bug last week, didn't find an open issue about this but I may be wrong

Minimal repro

I can open an issue but I don't know where it should belong (pulumi/pulumi ?)

Is pulumi latest version already ok to use with node v10 ?

It was merged but I don't see it in the changelog

And my last bit I promise, I've finished porting my whole serverless framework project. Pulumi is handling 79 resources in my test stack. Everything is working fine, great experience overall. Very easy to switch after I resolved my last issue last week with dynamic imports (thanks again @lemon-spoon-91807). I'm just a little bit concerned with my update time when I have no change or even a small change like updating a function.

pulumi update -y

on a stack with no changes takes approx. 1 minute 30 sec. Is this something that can/will be resolved? Honestly CloudFormation is really slow and I was hoping that pulumi could destroy it but I don't really see a difference between

sls deploy

and

pulumi update

atm.

And while porting the last bit, I had to dig a little bit to discover

pulumi.all()

. Needed it for my step function state machine definition. I think that the Step Function examples over at pulumi/examples should use

pulumi.all()

because when you're thinking about using Step Function you will often have a machine with more than one lambda. I can PR rewrite the example myself if you want.

Is it still expected with the latest pulumi that modules captured in an async lambda sometimes fail to serialize?

On a similar topic, is there a way to customise the execution role that an

aws.serverless.Function

ends up with? Right now it’s granting access to all kinds of unnecessary things by attaching the

LambdaFullAccess

policy.

A reminder to join @white-balloon-205 tomorrow at 11am PDT as he covers "What's New In Pulumi?" -- all the features and contributions from the past month.

As an FYI, the

Gopkg.lock

seems to be missing a couple of things for both

pulumi/pulumi

and

pulumi/pulumi-aws

, so running

make ensure

with

dep

0.5 is giving a diff on master.

Hi everyone! I’m an engineer at Pulumi and I’m looking into adding “workflow features” to the Pulumi.com service. For example, showing the results of

pulumi preview

ran in your CI/CD system on GitHub. Or optionally requiring another project member to review and approve infrastructure changes to a stack. If you are interested in providing feedback on the design and/or would like early access to prototypes, please send me a direct message with your contact info. I’ll schedule a call to get more information about what sorts of features would be most useful to you, and next steps for trying out the bits.

In today's PulumiTV live stream, I had a chance to show off some of What's New in Pulumi over the last few weeks - and in particular to highlight great contributions from @helpful-vegetable-35581 @tall-librarian-49374 and @stocky-spoon-28903! Topics covered: • OpenStack support (thanks @helpful-vegetable-35581) • Google Cloud Functions support (thanks @tall-librarian-49374) • AWS infrastructure packages (thanks @stocky-spoon-28903) • Simpler containers • Examples, examples, examples! (thanks @adventurous-jordan-10043 and @tall-librarian-49374) Big thanks to everyone who has contributed in all of these areas - can't wait to highlight even more new contributions in coming weeks! Check out the video at .

❤️ for whoever designed

pulumi.asset.RemoteArchive

New idea for

@pulumi/aws

- a

makeARN

to act as the opposite of

getARN

Hey everyone

Alex from OpenFaaS here - been checking out the progress on Pulumi serverless integration with our project - exciting stuff for the end users

Is it possible to improve this error message, or make single resources supported as a value for

dependsOn

in `ResourceOpts`:

error: TypeError: dependsOn.map is not a function
        at /Users/James/Code/pulumi/pulumi-lambda-cert/node_modules/@pulumi/pulumi/runtime/resource.js:160:92
        at Generator.next (<anonymous

The latter should be pretty easy. I think it's just a matter of updating a bit of code in the JS runtime libraries... cc @white-balloon-205

I’m actually not sure why it showed up as a runtime error rather than a compile time one in TypeScript

Welcome Alex! For folks interested - we've started on a new provider for using OpenFaaS with Pulumi. It's early, but you can follow along here: https://github.com/pulumi/pulumi-openfaas. This currently allows deploying to OpenFaaS (on Kubernetes or any other of the supported OpenFaaS environments) with something like:

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

const func = new openfaas.Function("hello-node", {
    service: "hello-node",
    build: "hello-node:latest",
});

In the near future, we will be extending this to support the same kind of super-simple functions that are frequently used in AWS and now Azure and GCP, like the following:

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

const f = new openfaas.serverless.Function("f", {}, (context: any, callback: any) => {
    callback(undefined, {status: "done"});
});

export let url = f.url;

This will be a great way to make it easier to deploy cloud functions onto many additional platforms!

Shameless self- (and Pulumi-) promotion: https://mikhail.io/2018/08/aws-lambda-warmer-as-pulumi-component/

@tall-librarian-49374 Love it!

Hi! I recently started playing with pulumi after following Joe for a while. Because my experience is with compiled languages i went for a TS project but I’m finding some issues when using any library inside a lambda callback. I’m trying to perform an http request inside a lambda and I keep receiving

Error serializing

with a stack trace that at the end says “it was a native code function.“. I’ve been having other issues with TS and some JS libs so at the end I wend for the standard http module but I’m still seeing this. Here is a gist in case somebody wants to take a look at the code https://gist.github.com/alexito4/84e34ce6c66aa320d361781f1ffd946e

I have some experience with lambda before but is not in my set of expertise, and the pulumi looks really awesome to simply the setup of it ^^

May be a bit late to change now, but is the TypeScript convention here to use

Arn

vs

ARN

? https://github.com/pulumi/pulumi-aws/blob/master/overlays/nodejs/arn.ts#L18

Hi 👋 I have a couple of questions regarding teams and secret configuration

mostly, I'm wondering if there is any way to keep encrypted config items from being decrypted from certain team members, or if anyone with access to the source can decrypt them?>

I have similar concerns regarding the ability for specific team members to deploy particular stacks, like locking down prod stacks to senior members