more OE variants

[sarnold]

Description:

• add common/useful OE distribution variants
• add missing table transforms

Rationale:

• distribution is a common customization

Review Hints:

• each commit is small/logically distinct

[openshift-ci]

Hi @sarnold. 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-sigs/prow repository.

[github-actions]

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

Fedora Environment

Oracle Linux 8 Environment

[github-actions]

🤖 A k8s content image for this PR is available at:
ghcr.io/complianceascode/k8scontent:12026
This image was built from commit: 0026e11

Click here to see how to deploy it

If you alread have Compliance Operator deployed:
utils/build_ds_container.py -i ghcr.io/complianceascode/k8scontent:12026

Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and:
CONTENT_IMAGE=ghcr.io/complianceascode/k8scontent:12026 make deploy-local

[codeclimate]

Code Climate has analyzed commit 0026e11 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 59.4% (0.0% change).

View more on Code Climate.

[marcusburghardt]

LGTM but I am not familiar with these distros. I will keep it here a little more so others can also take a look.

[sarnold]

• "petalinux" is a custom distro used in the xilinx/zynq SDK
• "harden" is the name of an example distro layer provided by meta-security called meta-hardening

The first one is used for pretty much all zynq boards, and it seemed like a good thing if the second one was recognized by the scanner. Thanks!

[Mab879]

LGTM.