Duplicate
Details
Labels
Story Points
NoneComponents
Sprint
NonePriority
MediumReporter
Lucas YamanishiLucas YamanishiWho's Looking?
Open Who's Looking?
Details
Details
Labels
Story Points
None
Components
Sprint
None
Priority
Reporter
Lucas Yamanishi
Lucas YamanishiWho's Looking?
Open Who's Looking?
More fields
More fields
More fields
Created October 30, 2017 at 5:21 PM
Updated December 2, 2019 at 6:56 PM
Resolved January 30, 2019 at 7:18 PM
Currently Puppet module RPMs contain a simple directory of files for each module, but this requires a lot of extra work to install them to to new Puppet environments, i.e., custom copy or synchronization scripts, or manual commands. Instead, I suggest that we package the bare Git repositories (as in `git clone --bare`) into the RPMs, installing them to `/usr/share/simp/repos`, or if they are not bare, `/usr/share/simp/modules`. This way a Puppetfile can reference them as Git repos using the `file://`.
This should make a lot of things easier, including, but not limited to, the following:
r10k dynamic environments
Pushing repos up to a private Git server
Modifying the Puppetfile to use a Git server, private or public
Code-signing verification of active, working Puppet environments via `git tag --verify`
Additionally, this would remove disparity between installation methods, since the Puppetfile would be nearly identical regardless of installation method.