- Newest
- Most votes
- Most comments
This appears to be fixed in the console, and you can delete with AWS CLI using
aws apigateway delete-base-path-mapping --domain-name foo.com --base-path "(none)"
However, it still appears to be completely broken in CloudFormation and causing us issues, too.
Any word on this? Our base path mappings won't delete either.
(edit) when I click the trashcan this is in the javascript console:
Uncaught TypeError: Cannot read property 'delete' of undefined
at t.n.handleDeleteButtonClick (BasePathMappingTableDetail.jsx:44)
at onClick (BasePathMappingTableDetail.jsx:93)
at HTMLElement.wrappedCb (createClass.js:47)
at o (components.js:173)
at Object.t [as __fireEvent] (components.js:153)
at Object.click (components.js:2521)
at HTMLButtonElement.r (components.js:2592)
at HTMLButtonElement.<anonymous> (components.js:1316)
Edited by: m_ohrt on May 5, 2017 12:21 PM
I have the same problem, can't delete base path mappings in the console, with AWS CLI or with CloudFormation. It's bad because it gets CloudFormation stacks stuck.
Relevant content
- asked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago