Versioned deployments

[AlexeyBarabash]

From the conversation with @bridiver and @darkdh.

brianjohnson

We need versioned deployments. Each server update uses a different url/lamda function and then those updated urls will just ride the release train. So when we change the server code it gets a new deployment and the old deployments don't change. The only time we'd change an existing deployment is for a bug fix.

About different channels of browser. They all point to the same s3 buckets except for maybe a dedicated test env, but the server code (auth and lambda) will have versioned deployments.

[bridiver]

so for instance we might have something like https://brave.sync.com/v1, https://brave.syn.com/v2 and whatever corresponding identifier we would need for different lambda deployments. That way we can coordinate the client changes with any server changes and not risk breaking things for users on release channel