(apigatewayv2): ApiMapping
does not add a dependency on DomainName
#15464
Labels
@aws-cdk/aws-apigatewayv2
Related to Amazon API Gateway v2
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
p2
ApiMapping
does not declare a dependency on theDomainName
it maps to an API. So, when both are created in the same stack, CloudFormation may fail to create the mapping with an error like this:Invalid domain name identifier specified (Service: AmazonApiGatewayV2; Status Code: 404; Error Code: NotFoundException; Re quest ID: <removed>; Proxy: null)
Reproduction Steps
What did you expect to happen?
I expected the stack to deploy.
What actually happened?
The stack failed to deploy with an error:
Invalid domain name identifier specified (Service: AmazonApiGatewayV2; Status Code: 404; Error Code: NotFoundException; Re quest ID: <removed>; Proxy: null)
Environment
Other
I can work around this by manually adding a dependency between the
ApiMapping
and theDomainName
, but I would have expected the L2 constructs to do this for me.This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: