librarian-puppet with modules in git
So, if you're using librarian-puppet it's recommended to not track your modules in git, but I'm creating a workflow with the opposite. Why would that be a bad idea?
To elaborate, we currently have one git repo with just a few modules, profile, role, and a couple of app specific ones that are still in their infancy. We also use several forge modules. Our repo has three branches mapped to the equivalent puppet environments. So my idea for a workflow is this.
Create this structure:
puppet |- manifests/ |- modules/ # Forge modules |- site/ # Our internal modules |- Puppetfile
Put it ... (more)