amigen7
amigen7 copied to clipboard
plus3it
Set of tools to provide automation of tasks for creating STIG-partitioned EL7 AMIs
**Nature of documentation error** - [ ] Typographical or Grammar Errors - [ ] Vague - [x] Misleading/Counter-intuitive - [ ] Wholly Incorrect - [ ] Missing Document (e.g., broken...
**Is your feature request related to a problem? Please describe.** When creating non-AWS build-types – particularly those that don't typically include execution of userData, it will be necessary for the...
**Describe the bug** When using to generate VMware and other image-types, `/var/run` does not get created as a symlink to `/run` **Severity** - [x] Completely Broken (No work-around evident) -...
Lines 82-83 have a silent failure if named EPEL repository is already present in CHROOT. Probably want to implement a pre-flight so that anything invoking script with stop-on-error doesn't abort.
**Is your feature request related to a problem? Please describe.** By default, `cloud-init` creates the provisioning-user with the first available `uid` value higher than the `SYS_UID_MAX` value declared in `/etc/login.defs`....
### Problem Description: On instances launched RHEL 7 AMIs `/var/run` is not a link to `/run`. This breaks DBUS upgrades ### Expected Behavior: `/var/run` is a link to `/run` in...
### Problem Description: When generating new "recovery" AMIs, the `GrubSetup.sh` currently sets the `root=` token to the chroot-built device's real devnode rather than properly referencing its `LABEL` value ### Expected...
### Problem Description: Due to NVMe devices using different naming conventions for disks/partition (`/dev/nvmeXnYpN` vice `/dev/xvdXN`), script fails when using `${CHROOTDEV}N` as targeting-method. See: * [Line 56](https://github.com/plus3it/AMIgen7/blob/master/DiskSetup.sh#L56) * [Line 84](https://github.com/plus3it/AMIgen7/blob/master/DiskSetup.sh#L84)...