Skip to content

Updates for new spack-config#368

Merged
CodeGat merged 10 commits intov8from
new-spack-config
Apr 16, 2026
Merged

Updates for new spack-config#368
CodeGat merged 10 commits intov8from
new-spack-config

Conversation

@CodeGat
Copy link
Copy Markdown
Member

@CodeGat CodeGat commented Apr 9, 2026

References ACCESS-NRI/spack-config#41
Closes #349

Background

There is an update to spack-config (see ACCESS-NRI/spack-config#110), which makes use of the includes.yaml, and a move away from the spack-enable.bash. This PR updates the workflow to use setup-env.sh, and adds a new script to set up service users.

Furthermore, we revert to essentially pre-v8 behavior in which instead of builtin-spack-packages being a lever to pull in config/settings.json, it is informed solely by spack-config.

The PR

  • Swap from spack-enable.bash to setup-env.sh
  • Add tools/service-user for setup of service users, update README
  • Remove updating of builtin via settings.json, now informed by spack-config

Testing

Tested in Prerelease via ACCESS-NRI/ACCESS-TEST#65

@CodeGat CodeGat added type:enhancement Improvements to existing features priority:medium version:MINOR Doesn't require update to Model Deployment Repositories for:v8 Applies to v8 labels Apr 9, 2026
@CodeGat CodeGat self-assigned this Apr 9, 2026
Comment thread .github/workflows/deploy-2-start.yml Outdated
@CodeGat CodeGat requested a review from harshula as a code owner April 14, 2026 00:44
@CodeGat
Copy link
Copy Markdown
Member Author

CodeGat commented Apr 14, 2026

@CodeGat don't forget to update the hash of spack in config/settings.json post-merge of ACCESS-NRI/spack-config#110 !

EDIT: Done in f0e4d61

Copy link
Copy Markdown
Contributor

@harshula harshula left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed via Zoom VC

@CodeGat CodeGat merged commit f7632a2 into v8 Apr 16, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

for:v8 Applies to v8 priority:medium type:enhancement Improvements to existing features version:MINOR Doesn't require update to Model Deployment Repositories

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can builtin-spack-packages/access-spack-packages be informed solely by spack-config?

3 participants