Feature: Multi computer and code export/import via YAML files #7007
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.
[wip]
Why
verdi comptuer setup-many
instead of modifyingsetup
A separate
verdi computer setup-many
command was added rather than extending the existingsetup
command due to architectural constraints in AiiDA's CLI framework:Key difficulties with modifying
setup
:--label
,--hostname
, etc.) before the function executes, making it impossible to bypass validation when using config filesConfigFileOption
automatically merges single YAML files into CLI parameters but doesn't support multiple filesI attempted to retrofit the batch functionality onto the interactive single-computer setup command, but that either resulted in parameter validation errors, prompting conflicts, or complex workarounds that would compromise the existing user experience. In the end, adding a new
setup-many
command instead seemed like a better option, and provides a clean, purpose-built solution for batch operations without affecting the existing functionality.