desired state / parsing of generated scripts or separate config

[vbondzio]

Problem description

Based on a custom generated script, it seems hard to identify the associated meta data (comments) and roll back routines. I.e. when I first saw the UI, I was assuming that my chosen items would be retained in some sort of static configuration (or I could import / parse the generated script) so, in case of issues, I could individually roll back. Unless I'm mistaken or too stupid (very high likelihood), there is no way of "importing" the generated script into the app to see the original selection.

Proposed solution

The implementation is beyond my pay grade ... e.g. should the yaml include "check" routines to establish current state? Should there be versioning? Windows version dependencies? On update of definition, rollback of old version and re-apply of new? Not sure more complexity would require a breakup of the 20k+ line yaml into sub-categories? (probably not attempted yet for a reason?)

I'd love to see solution ID's and versions including UI highlights of "what's new", e.g. two columns, applied and updated since last script / config version.

Alternatives considered

If the generated script is the (only) source of truth, include (if desired by user) the revert routines (commented out) below where applicable. The revert UI toggle doesn't make too much sense outside of the predefined templates.

P.S. Still the best tool out there, great initial UX and most of the descriptions are very "offline friendly", i.e. if applying before connecting the machine to the internet.