Ben Greenberg

This may be addressed now by #512 and/or #514?

As tested in #12942 this is no longer an issue with the latest versions of Pulumi. Crucially I had to ensure nested depedencies of `@pulumi/aws` on `@pulumi/pulumi` weren't still resolved...

Thanks for both of these links as they are useful links - however I what I mean by my description is having metadata about the instance provided by App Runner...

I had come here to check if Pulumi action did this out-the-box. My use case is that I thought this would fit very nicely with the branch-deploy model described[^1] and...

Cross-posting [my comment](https://github.com/aws/apprunner-roadmap/issues/13#issuecomment-1528730138) from the [_Support web sockets_ issue](https://github.com/aws/apprunner-roadmap/issues/13), as I think it's relevant to the same underlying problem about request timeout. > > App Runner currently supports 2 mins...

This has been resolved with https://github.com/pulumi/actions/pull/755

> App Runner currently supports 2 mins of maximum request timeout Is this the case even with data actively being transmitted? Heroku's approach[^1] is: _"An application has an initial 30...