New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(AWS API Gateway): Add HttpApiId to httpApi CF Outputs #8664
Conversation
Codecov Report
@@ Coverage Diff @@
## master #8664 +/- ##
==========================================
- Coverage 87.08% 87.08% -0.01%
==========================================
Files 253 253
Lines 9511 9547 +36
==========================================
+ Hits 8283 8314 +31
- Misses 1228 1233 +5
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @captainsano, looks great 🙌
@@ -148,6 +148,10 @@ class HttpApiEvents { | |||
}; | |||
resource.DependsOn = this.provider.naming.getHttpApiLogGroupLogicalId(); | |||
} | |||
this.cfTemplate.Outputs.HttpApi = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for confusion, after a second thought, I think it will be better to keep the same convention as for Url
and output it as HttpApiId
instead of HttpApi
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that makes sense, I'll change it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @captainsano 🙌
Link to the issue: #8650
This tiny PR adds HttpApi output to the cloudformation template when using AWS ApiGateway's httpApi, in addition to the existing HttpApiUrl output.
Closes: #8650