Open jpower432 opened 3 months ago
@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
@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.
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.
Transferring this issue to the new repo where this will be worked.
Issue description / feature objectives
Many of the workflows from
compliance-trestle
are duplicated incompliance-trestle-fedramp
. To reduce workflow maintenance, the workflows should be centralized and allow customization through inputs.Caveats / Assumptions
Completion Criteria
Needs oscal-compass/compliance-trestle#1608