Testing and State Transition

[sempervictus]

For workflows which recycle machines - HPC and the like, it's handy to create, run, and operate based on the return values of both commissioning and test scripts. Defining scripts as resources and then assigning those to a machine resource for execution when its state goes to commissioning or testing would permit the next iteration using a selector of ready/tested machines to do one thing while the cohort of test/script failures would be run through a different branch of logic.

Rough requirements:

1. script resource with commissioning/test type and contents (preferably validating MaaS' markup syntax in the header comments)
2. a field assigning scripts to machine resources
3. either a resource similar to instance or a state mechanism of some kind for machine to permit testing/commissioning/marking-broken (presumably to end an autonomous workflow and make a human handle it)

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.