Make it so that each version of boulder is fully self-documenting in terms of supported macros (actions and definitions), by ensuring that:
- macros have fields where they are defined that contain a non-empty "description" and "example" field (description being empty to should be a build-time error, example should be a warning).
boulder recipe macros can output a human readable and a JSON formatted output of the above.
Some refactoring may be needed, but will ultimately make it so that the canonical documentation for what boulder supports is single-sourced from the boulder version itself.
The relevant source files for this are:
Related to #202
Make it so that each version of boulder is fully self-documenting in terms of supported macros (actions and definitions), by ensuring that:
boulder recipe macroscan output a human readable and a JSON formatted output of the above.Some refactoring may be needed, but will ultimately make it so that the canonical documentation for what boulder supports is single-sourced from the boulder version itself.
The relevant source files for this are:
Related to #202