Dynamic deployment to regions

[abdulloooh]

Stated from serverless-compose FAQs that multi-region deployment is not supported in parallel which is understood.

However, What we are trying to do however is an equivalent of sls deploy --r us-east-1 then sls deploy --r us-east-2 i.e deploying all the services to different regions one after the other with the flag -r, not in parallel which is already stated as not currently supported.

Is this possible in serverless-compose please? as our whole stack runs on 2 regions. Thanks.

[mnapoli]

Hi @abdulloooh, in theory this would indeed work. Because if the deployments happen one after the other, then they won't write in parallel to .serverless/ and there will be no conflicts.

However in Compose it's tricky to detect that the deployment will work or not. Let me show an example:

# A
services:
  api-1:
    path: api
    params:
      region: us-east-1
  api-2:
    path: api
    params:
      region: us-east-2

# B
services:
  api-1:
    path: api
    params:
      region: us-east-1
  api-2:
    path: api
    params:
      region: us-east-2
    dependsOn: api-1

Configuration A will not work, because deployment happens in parallel. Configuration B will work.

But in Compose, how to properly detect and validate that? That's our challenge. Because we want to detect "A" and show an error to users (to avoid hidden surprises).

[pgrzesik]

I think this would be the best approach 👍

[abdulloooh]

That'd be great 🙌. Seems there might not be a way around for now. How soon can we get the new feature if fully approved?

[pgrzesik]

Hey @abdulloooh - I cannot give you exact timeline as we're currently focused on development of new features, but I'll try to find some time for it in the coming days.

[mnapoli]

@abdulloooh just in case you missed it, v1.1.0 supports the region option now: https://github.com/serverless/compose/releases/tag/v1.1.0

[abdulloooh]

Oh... Beautiful, thanks for the tap on that. I'll check it out.
Great work and support 🙏 @mnapoli @pgrzesik