Make the compliance-trestle workflows reusable

[jpower432]

Issue description / feature objectives

Many of the workflows from compliance-trestle are duplicated in compliance-trestle-fedramp. To reduce workflow maintenance, the workflows should be centralized and allow customization through inputs.

Caveats / Assumptions

• This repository may not be the best place to store the workflows

Completion Criteria

• Create composite actions or reusable workflow that can be used throughout the org

Needs oscal-compass/compliance-trestle#1608

[jpower432]

@butler54 Wanted to check before there was any movement on this issue - do you see duplication or conflict with oscal-compass/compliance-trestle#1608?

[butler54]

I think really

@butler54 Wanted to check before there was any movement on this issue - do you see duplication or conflict with oscal-compass/compliance-trestle#1608?

I think really oscal-compass/compliance-trestle#1608 is just steps on the way to doing this. There was a distinct lack of reusability when the pipelines were first created.

based on this: https://docs.github.com/en/actions/using-workflows/reusing-workflows we might want to establish a workflows repo or similar.

[jpower432]

Thanks for the reply. Sounds like it would be simpler to start this after oscal-compass/compliance-trestle#1608 is completed to take advantage of the changes.

based on this: https://docs.github.com/en/actions/using-workflows/reusing-workflows we might want to establish a workflows repo or similar.

Agree. I will create a new repo for this.

[jpower432]

Transferring this issue to the new repo where this will be worked.