-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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(apprunner): support VpcConnectors #19372
Conversation
0740683
to
a7e6ed4
Compare
Considering how App Runner treats VPC Connectors, there's an argument that VPC Connector should it's own construct that's passed in (and therefore sharable) between App Runner services. Maybe still with the option for a service to implicitly create one for you. |
7893f4f
to
a5b603b
Compare
@RichiCoder1 makes sense. I have added the new construct accordingly. |
a5b603b
to
592d9a3
Compare
592d9a3
to
3dc362a
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
This PR has been in the MERGE CONFLICTS state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week. |
This PR has been deemed to be abandoned, and will be automatically closed. Please create a new PR for these changes if you think this decision has been made in error. |
@DDynamic Will this PR be revived? |
@yamatatsu I'll take a look shortly! |
New PR opened here: #20471 |
closes #18887
VpcConnector
construct.vpcConnector
property. When present, associate the service with the connector.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license