References ACCESS-NRI/access-spack-packages#295

Background

Spack has split out their builtin package repo from spack core to it's own spack/spack-packages repository. We want a fork of this repository for our own modifications if required, and are thinking of calling it access-nri/upstream-spack-packages.

This means that we have to change the name of our access-nri/spack-packages repository to something like access-nri/access-spack-packages for consistency.

What This Means

• All references/inputs to spack-packages must be renamed to access-spack-packages.
• New inputs must be created to capture the state of upstream-spack-packages, since we now require a version of spack, upstream-spack-packages, access-spack-packages and spack-config to capture provenance.
• This means that we may have steps specific to spack 0.22 and spack 1.0 in the same pipeline.

Furthermore:

• MDR config/versions.json must now support potential .access-spack-packages and .upstream-spack-packages fields in the schema.
• Deployment config/settings.json must now support potential .deployment.TARGET.VERSION.access-spack-packages and .deployment.TARGET.VERSION.upstream-spack-packages fields in the schema.
• Uploads to the provenance database must be able to support versions for access-spack-packages and upstream-spack-packages. (Might also need to update access-nri/tracking_services)