Write new text for control input help.

[craigbox]

PR Type:

Documentation

---

PR Description:

This PR updates the descriptions in various metadata files to improve clarity and provide more detailed information. The changes mainly involve rephrasing existing descriptions and correcting grammar where necessary.

---

PR Main Files Walkthrough:

files:

README.md: Updated the description for the "cpu_request_max" control input.
rules/K8s common labels usage/rule.metadata.json: Updated the description for the "Kubernetes Recommended Labels" control input.
rules/container-image-repository-v1/rule.metadata.json: Updated the description for the "Allowed image repositories" control input.
rules/excessive_amount_of_vulnerabilities_pods/rule.metadata.json: Updated the descriptions for the "Max critical vulnerabilities" and "Max high vulnerabilities" control inputs.
rules/exposed-sensitive-interfaces-v1/rule.metadata.json: Updated the description for the "Sensitive interfaces" control input.
rules/insecure-capabilities/rule.metadata.json: Updated the description for the "Insecure capabilities" control input.
rules/label-usage-for-resources/rule.metadata.json: Updated the description for the "Recommended Labels" control input.
rules/resources-cpu-limit-and-request/rule.metadata.json: Updated the descriptions for the "cpu_request_max", "cpu_request_min", "cpu_limit_max", and "cpu_limit_min" control inputs.
rules/rule-credentials-configmap/rule.metadata.json: Updated the descriptions for the "Values", "Keys", and "AllowedValues" control inputs.
rules/verify-image-signature/rule.metadata.json: Updated the description for the "Trusted Cosign public keys" control input.

---

User Description:

Signed-off-by: Craig Box [email protected]

[codiumai-pr-agent-free]

PR Analysis

• 🎯 Main theme: Updating descriptions in metadata files for clarity and detail
• 📝 PR summary: This PR focuses on improving the descriptions in various metadata files. The changes mainly involve rephrasing existing descriptions and correcting grammar where necessary. The updates are aimed at providing more detailed information and improving clarity.
• 📌 Type of PR: Documentation
• 🧪 Relevant tests added: No
• ⏱️ Estimated effort to review [1-5]: 1
  The PR is straightforward, involving only changes to text descriptions in metadata files. No code or logic changes are involved, making it easy to review.
• 🔒 Security concerns: No
  This PR only involves changes to text descriptions and does not introduce any code changes or potential security issues.

PR Feedback

• 💡 General suggestions: The changes made in this PR are clear and improve the quality of the documentation. The descriptions are more detailed and provide better information. Good job on focusing on clarity and detail.

• 🤖 Code feedback:

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

[github-actions]

Summary:

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