compliance-trestle
compliance-trestle copied to clipboard
Review prior usage of yaml header to determine if use cases still apply or can it be removed/replaced
Issue description / feature objectives
Currently we have the ability to provide a yaml_header during markdown generation - with an additional option to override values in the header of the markdown. The original need for this is unclear and it may be possible to simplify its behavior or replace it with something better.
Caveats / Assumptions
The ability for a separate path to provide content, with possible override through override-header-values, adds complexity to using and developing the code - and simplification would be valuable.
Completion Criteria
- Review the previous repo example where an ssp was generated using scripts that included a provided yaml header
- Determine the content and purpose of the yaml header in that use case and if there is evidence the functionality is important and should be preserved
- Or suggest an alternate approach with something like a configuration file