Multiple top level specs can't be added to the build database #333
Description
Background
There has been some work done to support multiple builds of ACCESS-OM2 in the one environment, for ease of deployment and testing. In a future version of build-cd, we are also looking to move deployment naming and versioning to reserved defintions in the manifest, see #330. This means that eventually, we may look into mutli-spec environments for release, too.
The Issue
Unfortunately, the release database's model only supports a single root spec as part of a deployment, and when getting the metadata for a given deployment, we only get the first one.
See if we can support an update to the build database and metadata collection that gets all root specs. Possibly, inform which to get based on the deployment name, under .spack.definitions[]._name[0] in future.