When configuring multi-site setup, we can do:

ezpublish:     system:         site:             content:                 tree_root:                     location_id: 123

In case of deployment via Migrations this is error prone, as there's no guarantee that the id will remain the same, because this depends on a database (and gets quite complicated when talking about clusters and replication systems).

What should be possible is:

ezpublish:     system:         site:             content:                 tree_root:                     location_remote_id: 'a848bf9a709cd33a1a588b6e6f93b34c'

Note: I need to check if it's possible to specify that value via Migrations, PAPI allows it via LocationCreateStruct