Has anyone else experienced a bug with attaching an Authoriz Pulumi Community #general

Has anyone else experienced a bug with attaching a...

elegant-pager-5412

10/28/2021, 5:05 AM

Has anyone else experienced a bug with attaching an Authorizer to routes in HTTP API Gateway? I’m creating a JWT authorizer and then attaching it to several routes using the

authorizerId

property on the route. Pulumi detects it and says it’s going to update it, however, it does nothing on AWS. In fact, when I try to re-deploy, it shows me again that it’s going to update the routes but once again, it does nothing

little-cartoon-10569

10/28/2021, 5:31 AM

Are you adding it from inside a Promise.then() or Output.apply()?

little-cartoon-10569

10/28/2021, 5:31 AM

I see that sort of behaviour mostly in those cases.

elegant-pager-5412

10/28/2021, 7:30 AM

let me check

elegant-pager-5412

10/28/2021, 7:32 AM

I synchronously create the Authorizer and pass the

authorizer.id

to the

authorizerId

property. so I guess I’m passing a Pulumi’s

Output

elegant-pager-5412

10/28/2021, 7:32 AM

the context in which I’m building the route is

async

(due to lambda compilation with

esbuild

)

elegant-pager-5412

10/28/2021, 9:33 AM

However, if I export the stack, I can see that the right

authorizerId

is there under

inputs

. In the

outputs

key, the

authorizerId

is an empty string. Something went wrong in between

little-cartoon-10569

10/28/2021, 7:32 PM

If you have the time, you could try to reproduce the issue in Terraform.. that would tell you whether or not Pulumi is at fault.

3 Views

Open in Slack

Previous Next