AWS CDK | Multi-repository serverless project structure

  • Hello, everyone

    I'm trying to split my huge serverless CDK project into separate repositories/services. Everything is fine except one thing: I don't understand how to deal with shared API Gateway. Those multiple separated services should be exposed via one particular API Gateway. Do I need to separate shared resources to different git repository as well or manage it manually and just pass API arn as a hard-coded value?

    If someone will choose "option #1 - separate git repo" then how can I expose CDK output (resource IDs) from one Bitbucket's pipeline to another? Or probably is there a different approach to share common info between multiple bitbucket repositories?

    Thank you all!

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply