simp config should be able to create a puppet environment in a user-specified location (namely, somewhere outside of /etc/puppetlabs/code/environments)
Currently, simp config does not provide a way to create the Hieradata files or site manifest that would be populated in the production Puppet environment without overriding what's there. Please review the relevant discussion from https://simp-project.atlassian.net/browse/SIMP-6938 for additional details. The tl;dr of the proposed change is as follows:
create a new SIMP Omni-environment for a named environment from SIMP skeleton dirs and allow specification of the puppet environment directory ( which may be outside of /etc/puppetlabs/code/environments)
restrict the subset of actions to those that modify the Puppet environment files and secondary files
fail if the SIMP Omni-environment (with alt Puppet dir) already exists
Status | Not started |
|---|---|
Impact | MEDIUM |
Driver | @Kendall Moore |
Approver | |
Contributors | @Liz Nemsick @TrevorV @Chris Tessmer |
Informed | |
Due date | |
Outcome |
Background
Relevant data
Options considered
Option 1: | Option 2: | |
|---|---|---|
Description | Add an option to | Undefined as of yet - open to suggestions |
Pros and cons | Would allow users with an existing Puppet infrastructure managed by r10k/Code Manager to generate SIMP data outside of Puppet environment Adds additional complexity to | |
Estimated cost | MEDIUM | MEDIUM |