Description | Provide a simp command for users to generate a Puppetfile to o load the current RPM-installed Puppet modules from their tagged local git repositories: 
The reference Puppetfile loads a separate SIMP-specific Puppetfile.simp that can be easily replaced with the output of later simp gen_puppetfile runs: ./ # Puppet environment directory
│
├── Puppetfile # Environment's Puppetfile
| # (maintained by site admin, includes Puppetfile.simp)
└── Puppetfile.simp # Puppetfile of tagged modules from local SIMP git repos
# (generated by `simp gen_puppetfile` |
| Info |
|---|
This is currently no longer considered a viable option for SIMP 6.4.0. It is included here to documentation the fact that we considered it. |
The decision log "How to restructure the RPM installation sequence to be more r10k/Code Manager friendly" assumed that we would automatically provide a local bare git control repository. The intent was to provide a simple and safe experience for inexperienced Puppet administrators by automatically providing a local repository on their behalf.
However, after exploring different implementation options, it's not clear that this strategy would be simpler or safer. What has become clear is that most implementations are likely to add more trouble and complexity for site admins and SIMP developers than the idea is worth. |
| Related Issues | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 45e63be1-2551-37a6-b050-86a38172f71d |
|---|
| key | SIMP-6197 |
|---|
|
| N/A |
Pros and cons |  Less elaborate and magical than Option 2
Immediately provides a working Puppetfile that can deploy tagged modules using r10k puppetfile install Site admins decide when/if/how to update their Puppetfiles, and in which environments Reference Puppetfiles always deploys the current RPM-delivered versions of each module The Puppetfiles/simp/ directory provides a simple place to drop updated SIMP Puppetfiles.  This option encourages, but does not require (or provide) a git Control Repository.
This option expects site admins to use r10k/Code Manager to deploy modules (if not environments)  Puppet environments (and their modules) are no longer directly updated after SIMP RPM module upgrades
Existing SIMP users that are not fluent on r10k will need documentation/support to allow them to take advantage of the Puppetfiles | Sounds convenient when described at a high level Likely to make too many assumptions Requires the creation and maintenance of original tooling and logic. Nullifies the advantages of switching to community-supported deployment tools by adding a layer on top of them. Makes control repo management complicated and brittle for both admins and SIMP development. (Re-)confuses the separation between RPM-delivered files, SCM, control repositories, and local SIMP configurations. Proposals so far have tended to unwittingly re-engineer similar problems to the temporarily-obsoleted module upgrade dilemma that afflicts the original design of SIMP's simp-rpm-helper + module RPMs. No matter what we build, it will be wrong for someone. |