You can mis-deploy a heritage into the wrong district

[davidsiaw]

If you have district A and district B, it is possible to go

bcn create -e prod -d A

and then go

bcn create -e prod -d B

This is due to the fact that names are global but they can only be in one district. Deleting the heritage in B leaves the heritage in A still running but in barcelona its considered deleted. You can salvage this by creating the heritage in A again.

This does not cause trouble however until you use secret keys. If you create the heritage A and then set a secret key, creating the heritage in B will make the container fail to deploy. It will also cause you to not be able to run bcn run and instead get this error: AccessDenied: Access Denied

This problem is related to #616. We need to create a new API that requires both heritage and district names and deprecate the old one. This also means we need to modify the Barcelona CLI to provide both names.

Possible fix

For now we need to prevent heritages of the same name created from being created.

The next thing we need to do is make barcelona handle heritages keyed by district. This means barcelona needs to complain if it is asked to perform operations on a heritage name which is shared by two heritages in different districts.

[davidsiaw]

Reopening because merged PR does not fix the problem.