From 50a5dc0ae8c7e402b2c724634076f25727358d78 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org>
Date: Mon, 2 Nov 2020 16:16:33 -0500
Subject: [PATCH] another possible control-repo implementation

---
 howto/puppet.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/howto/puppet.md b/howto/puppet.md
index 2cf3c581..82f9f8e8 100644
--- a/howto/puppet.md
+++ b/howto/puppet.md
@@ -1491,7 +1491,8 @@ What follows is an explanation and justification of each step.
 
 ### Use a control repository
 
-The base of the infrastructure is a [control-repo](https://puppet.com/docs/pe/latest/control_repo.html) ([example](https://github.com/puppetlabs/control-repo))
+The base of the infrastructure is a [control-repo](https://puppet.com/docs/pe/latest/control_repo.html) ([example](https://github.com/puppetlabs/control-repo),
+[another more complex example](https://github.com/example42/psick))
 which chain-loads all the other modules. This implies turning all our
 "modules" into "profiles" and moving "real" modules (which are fit for
 public consumption) "outside", into public repositories (see also
-- 
GitLab