Update Guidance for v8 - spack v1 Migration
#37
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-project-automation
bot
moved this to New Issues 🌅
in Spack `0.22` to `1.0` Migration
CodeGat
force-pushed
the
infra-update-v8
branch
from
80272b5 to
8082fe6
Compare
CodeGat
force-pushed
the
infra-update-v8
branch
from
8082fe6 to
c43ecea
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
References ACCESS-NRI/build-cd#326
Closes #36
Background
This PR updates
model-deployment-templateguidance forbuild-cd v8- thespack v1.Xmigration. It includes:spack.yamlreserved definitions.spack.definitions[].{_name|_version}config/versions.jsonfield.custom-scopes, to pass in high-precendence spack configurationspack.specsThe PR