Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds an oscal directory and GitHub Actions workflow for upstream OSCAL content #11286

Merged
merged 5 commits into from
Dec 6, 2023

Conversation

jpower432
Copy link
Contributor

Description:

Adds initial vendor directory for OSCAL content with REV4 and REV5 NIST 800-53 catalogs and FedRAMP High profiles. Adds update-vendor.yaml for automated updates of content

Rationale:

Allow upstream OSCAL content to be updated, reviewed, and stored to aid to generating OSCAL component definitions.
Partially address issue #11106

Review Hints:

This is part one to a two part feature add. The update-vendor.yaml was tested/verified locally using act.

Adds initial vendor directory for OSCAL content with REV4 and
REV5 NIST 800-53 catalogs and FedRAMP High profiles.
Adds update-vendor.yaml for automated updates of content

Signed-off-by: Jennifer Power <[email protected]>
@openshift-ci openshift-ci bot added the needs-ok-to-test Used by openshift-ci bot. label Nov 17, 2023
Copy link

openshift-ci bot commented Nov 17, 2023

Hi @jpower432. Thanks for your PR.

I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment
Open in Gitpod

Oracle Linux 8 Environment
Open in Gitpod

@Mab879
Copy link
Member

Mab879 commented Nov 17, 2023

We store other vendor files (such as the STIG XML files) in shared/references that might be a better place for these files.

Copy link
Member

@Mab879 Mab879 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR.

I have a few minor points mainly around style.

delete-branch: true
commit-message: "Update vendored OSCAL content"
add-paths: |
vendor/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a new line at the end of the file.

- name: Update content
uses: peter-evans/[email protected]
with:
base: master
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a useful title for these PRs.

https://github.com/peter-evans/create-pull-request#action-inputs

@@ -0,0 +1,55 @@
name: Update vendored OSCAL content
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the project style gude please use 4 space indention.

uses: peter-evans/[email protected]
with:
base: master
branch: "vendor-update-${{ github.run_id }}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A body on the PR might be useful as well.

@Mab879 Mab879 added the Infrastructure Our content build system label Nov 17, 2023
…tion

Moves vendor to shared/references/oscal
Updates update-vendor.yml to update-oscal.yml
Updates formatting on update-oscal.yml to meet styling requirements
Adds PR title and body to PR step in update-oscal.yml

Signed-off-by: Jennifer Power <[email protected]>
@jpower432
Copy link
Contributor Author

Thanks for the feedback @Mab879. I moved the directory to shared/references/oscal. Also changed some of the names to be more OSCAL specific since OSCAL is just one type of vendored file. Styling fixes also added in the last commit. Please let me know if any other changes are needed.

@jpower432 jpower432 requested a review from Mab879 November 17, 2023 23:44
@jpower432 jpower432 changed the title feat(action): adds directory and action for vendor dir Adds an oscal directory and GitHub Actions workflow for upstream OSCAL conent Nov 20, 2023
@vojtapolasek vojtapolasek added this to the 0.1.72 milestone Nov 29, 2023
This updates the NIST references to the latest supported version for
trestle. Instead of updating it in multiple places, this adds environment
variables to store that information.

Signed-off-by: Jennifer Power <[email protected]>
@jpower432
Copy link
Contributor Author

Adding information on the last change. The workflow was originally pointing to the to the oscal-content v1.0.0 release, but there are newer version of the catalog. Added environment variables so the references are easier to change and updated to the latest commit on the repository before the update to OSCAL version 1.1.1. compliance-trestle does not support this version yet.

@Mab879
Copy link
Member

Mab879 commented Dec 1, 2023

/packit retest-failed

- usnistgov NIST 800-53 from "${{ matrix.variables.catalog-source }}"
- GSA FedRAMP OSCAL profiles from "${{ matrix.variables.profile-source }}"

Auto-generated by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also provide the path to this GitHub Actions file as well?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the style guide please use Markdown unless there is a compelling reason.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed that detail in the guide. I will convert to Markdown.

Updates the "auto-generated message" to point to the actions worflow
file and updates the environment variable reference in the matrix
variables to ensure the correct values are used when
referencing the content sources.

Signed-off-by: Jennifer Power <[email protected]>
Copy link

codeclimate bot commented Dec 1, 2023

Code Climate has analyzed commit 8e0b2ae and detected 0 issues on this pull request.

Too many changed lines in diff

View more on Code Climate.

@jpower432 jpower432 requested a review from Mab879 December 1, 2023 22:34
@Mab879 Mab879 self-assigned this Dec 4, 2023
@Mab879
Copy link
Member

Mab879 commented Dec 5, 2023

/packit retest-failed

@jpower432 jpower432 changed the title Adds an oscal directory and GitHub Actions workflow for upstream OSCAL conent Adds an oscal directory and GitHub Actions workflow for upstream OSCAL content Dec 6, 2023
Copy link
Member

@Mab879 Mab879 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Thanks for the PR!

@Mab879 Mab879 merged commit 1a50ebd into ComplianceAsCode:master Dec 6, 2023
34 checks passed
@vojtapolasek vojtapolasek added Highlight This PR/Issue should make it to the featured changelog. and removed Highlight This PR/Issue should make it to the featured changelog. labels Feb 9, 2024
@marcusburghardt marcusburghardt added the OSCAL PRs and Issues releated to OSCAL label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infrastructure Our content build system needs-ok-to-test Used by openshift-ci bot. OSCAL PRs and Issues releated to OSCAL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants