Remove remediations for security_patches_up_to_date

[Mab879]

Description:

Remove remediations for security_patches_up_to_date

Rationale:

Part of removing this rule from various profiles.

[github-actions[bot]]

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

Fedora Environment

Oracle Linux 8 Environment

[github-actions[bot]]

:robot: A k8s content image for this PR is available at: ghcr.io/complianceascode/k8scontent:11992 This image was built from commit: f01dffa5f14b314d56884148e9d47e40a7e4bf83

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:11992

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

[qlty-cloud-legacy[bot]]

Code Climate has analyzed commit f01dffa5 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.

[jan-cerny]

@Mab879 This isn't the right fix, there are products that still actively use the rule security_patches_up_to_date, for example Oracle, SLES, Ubuntu. You can find them by looking for oval_feed_url variable. I think we shouldn't change them. Try to change the platform key in the remediations

[Mab879]

There is another PR that is better, closing.