-
Notifications
You must be signed in to change notification settings - Fork 706
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
AlmaLinux OS 9 as a new product #12810
base: master
Are you sure you want to change the base?
Conversation
Hi @sej7278. 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 Once the patch is verified, the new status will be reflected by the 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. |
Moving my questions from the last PR. Again, thanks for the PR and working with us! Do you have plans for expanding the standard profile? If you are planning on expanding it, I would recommend setting the |
Thanks @Mab879, yes I've set standard to false (it was just based on the new product template script) and will update it later. My priority for this release is a new product with CIS benchmarks. Standard, STIG and other profiles like PCI-DSS and HIPAA to follow later for sure. |
Code Climate has analyzed commit 2a5d381 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 61.8% (0.0% change). View more on Code Climate. |
There was a problem hiding this 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 just have one minor suggestion.
I'm going to leave this PR open a few days for the other distro maintainers to approve due CODEOWNERs requirements.
Absolutely, as by the nature of adding a new product, I did have to edit other products and support scripts e.g. to exclude gpgkey or oval checks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the CI caught something.
Seems that "!ensure_almalinux_gpgkey_installed" is needed in products/rhel10/profiles/hipaa.profile
.
Fixed. I did wonder why we have a bunch of negative tests for every distro instead of just a single positive e.g. P.S. linkchecker seems to report a 404 for at least the rhel9 and rhel10 profiles for https://www.nerc.com/pa/Stand/Standard%20Purpose%20Statement%20DL/US_Standard_One-Stop-Shop.xlsx |
/packit build |
I will take look at the link issue. The failing CI should be fixed if you rebase your PR on the latest master. |
ok i'll give it a go, hopefully won't nuke the PR like last time! |
Fixed pep8 blank line between function definitions issue from codeclimate
Description:
Adds AlmaLinux OS 9 as a new product - flattened merge requests and "disabled" standard profile.
Would appreciate a review to see if this is sufficient to add the new product or to identify any remaining work that may be needed. It certainly builds the standard+CIS guides just fine.
Accidentally nuked #12808
Rationale:
As discussed on #12757 it would be good to add AlmaLinux OS 9 as a new product rather than a RHEL 9 derivative, as they do differ - most notably their STIG's.
As the FIPS/STIG stuff for AlmaLinux is commercial via TuxCare and only support specific minor versions, it makes sense to have a base product for community-compatible major version profiles like CIS benchmarks, that we can add control files to for use with the commercial profiles.