Currently any type of route created via teh apigateway function is attaching an additional resource /{proxy+} to the created path, regardless of integration type.
Vote on this issue by adding a π reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
What happened?
Currently any type of route created via teh apigateway function is attaching an additional resource
/{proxy+}
to the created path, regardless of integration type.Steps to reproduce
Create an api gateway endpoint:
Deploy the specified resource.
Expected Behavior
A single route
/
is created with teh specified integration type.Actual Behavior
Both
/
and/{proxy+}
are created.Versions used
"@pulumi/aws": "^4.38.1", "@pulumi/awsx": "^0.40.0", "@pulumi/pulumi": "^3.26.1", "@pulumi/random": "^4.4.2",
Additional context
No response
Contributing
Vote on this issue by adding a π reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).