Enable overriding seLinux type for custom type tags

[slashben]

Type

enhancement

---

Description

This PR introduces the ability for users to override the most common SELinux type scp_t with a custom tag that fits their specific environment. This enhancement was prompted by an issue encountered in the Bottlerocket OS environment in AWS.

---

PR changes walkthrough

	Relevant files
Configuration changes	1 files                                                                                                   The changes in this file enable the overriding of the SELinux type for custom type tags.

---

User description

Overview

In different environments, privileged SELinux type tags can differ. In this PR we add capability for the user to override the most common type scp_t with custom tag that fits the give environment.

Additional Information

This issue came around in Bottlerocket OS environment in AWS.

Related issues/PRs:

bottlerocket-os/bottlerocket#3677

[codiumai-pr-agent-free]

PR Description updated to latest commit (b3945be)

[codiumai-pr-agent-free]

PR Analysis

• 🎯 Main theme: Enabling the overriding of SELinux type for custom type tags
• 📝 PR summary: This PR introduces a feature that allows users to override the default SELinux type with a custom tag that fits their specific environment. This enhancement was prompted by an issue encountered in the Bottlerocket OS environment in AWS.
• 📌 Type of PR: Enhancement
• 🧪 Relevant tests added: No
• ⏱️ Estimated effort to review [1-5]: 2, because the PR seems to be straightforward and only involves configuration changes. However, without the actual code diff, it's hard to accurately estimate the effort required.
• 🔒 Security concerns: No

PR Feedback

• 💡 General suggestions: It would be beneficial to include some tests that validate the new functionality. Also, providing more context in the PR description about the specific issue encountered in the Bottlerocket OS environment would help reviewers understand the motivation behind this change.

• 🤖 Code feedback:

How to use

Instructions

To invoke the PR-Agent, add a comment using one of the following commands:
/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs: Generate docstring for new components introduced in the PR.
/generate_labels: Generate labels for the PR based on the PR's contents.
see the tools guide for more details.

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