AlmaLinux-Deploy Migration: Uncertain Handling of Custom SELinux Policies

Goal

The objective is to validate the behavior of the AlmaLinux-Deploy migration tool in a non‑production environment, ensuring that critical security configurations are preserved without exposing real credentials.

Constraints

Because the test system lacks valid Red Hat subscription data, the migration must rely solely on community repositories and local policy modules. The environment also contains several custom SELinux policy modules that were compiled against a previous RHEL release.

Uncertainty

It is unclear whether AlmaLinux-Deploy automatically updates or rebuilds these custom SELinux modules to match the target RHEL 9 kernel, or if it simply copies the existing binaries unchanged. Additionally, the tool’s documentation does not specify if there is an explicit flag to force a rebuild of policy modules.

Questions

1. Which options does AlmaLinux-Deploy provide to preserve custom SELinux policies during migration, and does it automatically update the policy modules to match the target RHEL version?
2. If no such option exists, what is the recommended workflow to ensure policy compatibility post‑migration?