Refactor mache.deploy for E3SM-Unified deployment support#374
Merged
xylar merged 8 commits intoE3SM-Project:mainfrom Apr 2, 2026
Merged
Refactor mache.deploy for E3SM-Unified deployment support#374xylar merged 8 commits intoE3SM-Project:mainfrom
xylar merged 8 commits intoE3SM-Project:mainfrom
Conversation
Add the deploy changes needed to support the E3SM-Unified migration without baking E3SM-specific behavior into generic downstream workflows. - add platform default machine configs in mache.machines - support separate login and compute pixi environments in deploy run/load - allow hooks to override pixi prefix, channels, MPI, and software version - pass spack deployment results and generated load scripts through runtime - treat the hpc pixi variant correctly when rendering package build strings - preserve generic mache behavior by keeping e3sm_unified-specific fallback logic out of mache core - update deploy documentation and templates to match the new workflow
Cover the deploy runtime changes added for the E3SM-Unified workflow. - test runtime pixi prefix and channel overrides - test login/compute environment load-script generation - test platform default machine config loading - test known-machine handling for new default cfg files - test that machine metadata remains scoped correctly after the deploy changes text
Make `--pixi-path` the canonical deploy CLI flag for the pixi environment location, while keeping `--prefix` as a deprecated alias for backward compatibility. Update the generated CLI spec, bootstrap parser, deploy-time argument resolution, and focused tests for both the new and legacy spellings.
xylar
added
enhancement
Collaborator
Author
TestingI did a test deployment on Chrysalis with this branch and E3SM-Project/e3sm-unified#145. Pixi (login and compute) and spack environments were successfully deployed. Permissions appear to have been updated as desired. The I tested both with |
2 tasks
When we are installing a mache release candidate into a bootstrap environment, we need to get it from the `label/mache_dev` label on conda-forge.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add the deploy changes needed to support the E3SM-Unified migration
without baking E3SM-specific behavior into generic downstream workflows.
mache.machineslogic out of mache core
Checklist
Testingcomment, if appropriate, in the PR documents testing used to verify the changes