feat: updating restApi to be union of RestApi and IRestApi #99
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
Large RestAPI collections can exceed AWS's cap on 500 resources per stack. In order to support large RestAPI collections the WatchApiGateway construct may not be defined in the same stack as the RestAPI resource. In these cases the existing WatchApiGateway construct cannot watch the created API gateway because it only accepts an
apigw.RestApi
object and notapigw.IRestApi
object.What
Support multistack RestAPI collections by allow restApi to be either a
apigw.RestApi
orapigw.IRestApi
resource