You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the excellent custom construct. I am considering using this construct but have noticed a concerning issue, hence this bug report.
In aws-apigateway-sqs, if the DELETE /message path is not used, it can be disabled by setting allowDeleteOperation to false in the properties.
However, in the current implementation, although setting it to false prevents the creation of the DELETE Method, the /message path, which is not supposed to be used, is still added to the API Gateway.
Having a path added to the API Gateway that is not intended to be used does not seem to be the expected behavior.
Thank you for the excellent custom construct. I am considering using this construct but have noticed a concerning issue, hence this bug report.
In aws-apigateway-sqs, if the DELETE /message path is not used, it can be disabled by setting allowDeleteOperation to false in the properties.
However, in the current implementation, although setting it to false prevents the creation of the DELETE Method, the /message path, which is not supposed to be used, is still added to the API Gateway.
Having a path added to the API Gateway that is not intended to be used does not seem to be the expected behavior.
Reproduction Steps
Error Log
Generated template
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: