fix fixpath for controls C-0077 and C-0076

[YiscahLevySilas1]

PR Type:

Bug fix

---

PR Description:

This PR addresses an issue with the formatting of label paths in Rego rules. The previous format used a dot notation which has been replaced with a bracket notation to correctly reference labels in the metadata. This change affects both the rules and their corresponding test files.

---

PR Main Files Walkthrough:

files:

rules/k8s-common-labels-usage/raw.rego: Changed the label path format from dot notation to bracket notation in the 'no_K8s_label_or_no_K8s_label_usage' functions.
rules/k8s-common-labels-usage/test/cronjob/expected.json: Updated the expected output to reflect the new label path format.
rules/k8s-common-labels-usage/test/pod/expected.json: Updated the expected output to reflect the new label path format.
rules/k8s-common-labels-usage/test/workload-fail/expected.json: Updated the expected output to reflect the new label path format.
rules/label-usage-for-resources/raw.rego: Changed the label path format from dot notation to bracket notation in the 'no_label_or_no_label_usage' functions.
rules/label-usage-for-resources/test/cronjob/expected.json: Updated the expected output to reflect the new label path format.
rules/label-usage-for-resources/test/workload-fail/expected.json: Updated the expected output to reflect the new label path format.

---

User Description:

Overview

[codiumai-pr-agent-free]

PR Analysis

• 🎯 Main theme: Fixing label path formatting in Rego rules
• 📝 PR summary: This PR addresses an issue with the formatting of label paths in Rego rules. The previous format used a dot notation which has been replaced with a bracket notation to correctly reference labels in the metadata. This change affects both the rules and their corresponding test files.
• 📌 Type of PR: Bug fix
• 🧪 Relevant tests added: Yes
• ⏱️ Estimated effort to review [1-5]: 2, because the PR is straightforward and involves only changes in the formatting of label paths in Rego rules and their corresponding test files.
• 🔒 Security concerns: No security concerns found

PR Feedback

• 💡 General suggestions: The PR seems to be well-structured and the changes made are clear and concise. The switch from dot notation to bracket notation for label paths in Rego rules is a good improvement for better referencing labels in the metadata. The corresponding changes in the test files are also well done.

• 🤖 Code feedback:

  • relevant file: rules/k8s-common-labels-usage/raw.rego
    suggestion: Ensure that the new bracket notation for label paths does not introduce any unexpected behavior or bugs in the Rego rules. [important]
    relevant line: path = [{"path": sprintf("%vmetadata.labels[%v]", [start_of_path, label_key]), "value": "YOUR_VALUE"}]

  • relevant file: rules/label-usage-for-resources/raw.rego
    suggestion: Validate that the change in the label path format does not affect the functionality of the 'no_label_or_no_label_usage' functions. [important]
    relevant line: path = [{"path": sprintf("%vmetadata.labels[%v]", [start_of_path, label_key]), "value": "YOUR_VALUE"}]

How to use

To invoke the PR-Agent, add a comment using one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

[github-actions]

Summary:

• License scan: failure
• Credentials scan: success
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success