[Feature Request] Ensure use of NetworkManager Key-files instead of ifcfg files
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
While writing security-automation for the watchmaker project (see: ash-linux-formula PR #506), a security-finding came up for the network configuration files. This led me to find a vendor-article on the deprecation of ifcfg files in RHEL 9 and later (see the "NetworkManager connection profiles in ifcfg format are deprecated" section of the linked-document for specific verbiage). The AMIgen automation needs to be updated to account for this change
Describe the solution you'd like
AMIgen bakes in the cloud-init service. Instances launched from AMIgen-created images already leverage cloud-init for boot-time automation-tasks. The ifcfg to NM-keyfile operation could be included by way of a per once stage script.
Describe alternatives you've considered
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AMIgen automation that bakes in cloud-init and review the linked RHEL documentation on NetworkManager key-files and cloud-init execution stages. Implement the requested per-once conversion from ifcfg files to NetworkManager key-files, then verify that AMIgen-created images use the key-file format for network configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cloud, devops, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100