Explore the use of an external configuration file for static inputs and model specific configurations

[jpower432]

Is your feature request related to a problem? Please describe.

The command line flags have a combination of inputs that would require dynamic configuration (e.g. commit author) and input that would be relatively static (e.g. oscal-model, markdown path). This issue is a request to explore if using an external configuration file would be a better user experience. As the options for the individual models grow, this could be beneficial.

Describe the solution you'd like

• Determine which flags would have a static or model-specific input and migrate this to a configuration file

Describe alternatives you've considered

• Environment variables as a flag default instead of hard coding defaults. This may be difficult to validate or discover.

Additional context

• This may result in breaking changes to the SSP Index