This message was deleted.

This might be an awsx / automation api thing (although I've not seen this yet). I'm just trying something else to see if it's an apigateway thing or not. (I did try running your code outside of automation api and that worked) Another thing to try is to move the pulumi program part of the code to outside the automation api code (something like this)

Thanks, @brave-planet-10645. It does run successfully outside of the automation API script - yes. I'll try moving the Pulumi program part out of the automation code and see how that goes

You can still run integration tests (the github link above has an example where the pulumi code is outside of the automation api code) and it gives an example of how you can test it

Cool. So you're basically doing the same things, but just not using the

pulumiProgram

to do it. Instead you're referencing the stack inside the

infrastructure

folder and then standing up the infra. Am I following?

yes

Awesome - trying now. Thank you!

that's correct... it's running it as a

LocalProgram

rather than an

InlineProgram

To circle back on this - it does work using that structure you provided. Thanks for that! That let's us move forward at least until the automation api bug is addressed.

Great to hear. Do you mind updating the issue you created with these details (as in how it worked when you used a LocalProgram rather than an InlineProgram) as that'll help my colleagues get to the bottom of this a lot quicker

Absolutely - will do!

Thank you

Responded on the issue but I believe this is a known bug with a workaround: https://github.com/pulumi/pulumi/issues/6162#issuecomment-764787396 Would you mind giving that a go? We do have work planned to address this in the near future.

Thanks Evan

@lemon-agent-27707 Thanks, Evan -- we'll give that a go and let you know how it goes.