Add Content Generation for Develop Branch

[aj-stein-nist]

Committer Notes

This will close #132. I wanted to ensure we share resolved profiles and other content following review and merge of work for #97 and lower burden for our own devs and outside contributors to see the result.

Also related notionally to dev feedback in #120 .

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Do all automated CI/CD checks pass?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you included examples of how to use your new feature(s)?

[aj-stein-nist]

During weekly status review, I agreed to add some more debugging steps to collect state in the workspace for debugging in the event the build breaks or fails. Will do that ASAP for Dave to quickly review today.

[aj-stein-nist]

During weekly status review, I agreed to add some more debugging steps to collect state in the workspace for debugging in the event the build breaks or fails. Will do that ASAP for Dave to quickly review today.

Note to AJ for posterity: going to splice content in from aj-stein-nist/oscal-content@b5b1bd9 into the content-artifacts.yaml workflow.

[aj-stein-nist]

Alright @david-waltermire-nist, code added and ready for prompt review. Below is a sample workflow run (it failed, but that is good for this reason) to show the debugging content collected and attached to the run. This shows always() working with sad path, not just happy path.

https://github.com/usnistgov/oscal-content/actions/runs/3024676041

[david-waltermire]

LGTM. Thanks!