Page Comparison

...

Control repositories

Outside of SIMP, Gitgit-based control repositories have become the dominant technology to manage and deploy Puppet code.

...

The upshot is that a control repository branch defines everything needed to recreate a specific Puppet environment. 

Image RemovedImage Added

Puppet environments as code

...

However, there are still two major problems when using SIMP 6.4.0 with multiple Puppet environments and control repositories:

Issue 1: SIMP

...

automatically interferes with files under the Puppet and SIMP environment directories 

This issue is effectively fixed in 6.4+,

1. Status
   colour Red title SIMP 5.0-6.3

    RPM updates and simp_rpm_helper could modify existing files Puppet and SIMP environment directories

2. Status
   colour Red title SIMP 5.0-6.3

    User-initiated tools like simp config could modify existing files Puppet and SIMP environment directories

3. Status
   colour Green title SIMP 6.4

    

   Status
   colour Yellow title PARTIALLY FIXED

    The user-initiated tool simp environment new can ensure that there is a corresponding secondary and writable environments
   1. This is a safety improvement from earlier releases, because it will only alter only alters environment files when the user initiates it
   2. However, the simp environment tool is only partially implemented, and the rest cannot be implemented safely.
   3. As things stand, this means SIMP 6.4.0:
      1. Safely supports SIMP extra data with the Local (Puppetfile-only) deployment scenario with a single environment (production)
      2. Does not safely support SIMP extra data with the Control Repository deployment scenarios (without additional conventions and limitations)

...