My serverless infra is split between multiple functional stacks, each one of them has it's own resources (dynamo, topics, queues, etc).
For some stack A, I need to define a lambda which listens to another stack B queue events.
Assuming a deployment from scratch, it works well if B is deployed first, because the queue will be created when deploying A. But my ci is currently :
sls deploy A
sls deploy B
And adding, for instance, a SQS resource in B and reference it in A will cause the deployment to fail, because during A deployment the B SQS resource doesn't exist yet.
How can I handle this kind of cross stack dependency properly ?
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…