Hrm getting an error running

pulumi update

, anybody know what the problem could be?

@microscopic-florist-85263 uploaded a file: Untitled

Ahh disregard the above, i bootstrapped a new pulumi project and it worked

I think the only difference i made was explicitly set a

pulumi config set cloud:provider aws

and for some reason it spit out an error

@microscopic-florist-85263 Definitely a bug - sorry about that. I've opened https://github.com/pulumi/pulumi-terraform/issues/211 so we can investigate. Curious if you can share the results of

pulumi update --logtostderr -v 9

in DM?

Ah thanks!

Ah crap, deleted the project folder

Will do it the next time i encounter bugs though.

Let me see if i can reproduce the bug

Okay - no worries. I'll leave the issue open so we can see if we can reproduce ourselves as well.

cool thanks!

Great product you folks have btw 🙂

Thanks! 😄

hrmmm can’t repro.. dont know what it could be 😮

When it was broken, it did prompt me for a cloud:provider config though.

These are all taken following the instructions for the tutorial deploying containers onto Fargate.

Might have been a tiny little typo or something followign the entire flow.

Is it possible to declare a javascript based lambda with it;s functionality inline? All the examples of this that I find seem to be creating HTTP/API based lambdas and I want to create one that doesn’t have a trigger that I can attach to a cloudfront lambda edge property.

@early-napkin-64960 you can! https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/serverless/#Function

Hi, I've found something quite disturbing

I have this very simple serverless API deployed

@adventurous-jordan-10043 uploaded a file: Simple API

The deployment is working correctly but when I try to manually trigger the ressource on API Gateway console, it fails with the error

Execution failed due to configuration error: Invalid permissions on Lambda function

I still can trigger the deployed endpoint btw

@adventurous-jordan-10043 This is indeed surprising, the serverless API abstraction is supposed to create the adequate IAM policies. @white-balloon-205 @lemon-spoon-91807 Any idea what might be happening here?

To make things more clear I can hit this URL https://q8liyzmzn1.execute-api.eu-west-1.amazonaws.com/stage/a but manual testing from the console (see screenshot) is failing.

I'm trying to port an existing project using serverless to pulumi and I'm hitting a few walls

https://github.com/pulumi/pulumi/issues/463 is a very interesting and important issue I think. It helped me solved a few of my problems but I'm still stuck on something. In

index.ts

I declare a Dynamo table. I then export it's name

export const slotsTableName = slotsTable.name

. I have an

aws/dynamo.ts

file containing some functions to interact with my Table. I also have a

lambda.ts

file.

lambda.ts

is imported in

index.ts

as a Lambda handler for my API.

const api = new serverless.apigateway.API('api', {
    routes: [
        {method: 'GET', path: '/events', handler: lambda} // imported from `lambda.ts`
    ]
})

Internally,

lambda.ts

references

aws/dynamo.ts

and

aws/dynamo.ts

references `index.ts to import the Dynamo table name. Pulumi can successfully deploy this infra but the dynamo table name import from 'index.ts' to

aws/dynamo.ts

is failing because index.ts is not serialized in the final Lambda. I realize that my architecture is a bit complex and I think that I will have to fallback to lambda env variables and use the lower level package for my Lambdas.

Morning/Evening/Afternoon all. @white-balloon-205 and @bitter-oil-46081 will be live streaming at 11am PDT this morning. Join us if you can.