Issue 2185 - Migrate Rieveld superuser creation to fixture

modules/private-stub/hiera/roles/codereviewserver.yaml

Index: modules/private-stub/hiera/roles/codereviewserver.yaml
diff --git a/modules/private-stub/hiera/roles/codereviewserver.yaml b/modules/private-stub/hiera/roles/codereviewserver.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..2462c0e04ed13e7f7109cd211d942bd3b31bccf7
--- /dev/null
+++ b/modules/private-stub/hiera/roles/codereviewserver.yaml
@@ -0,0 +1,5 @@
+rietveld::fixtures:
+  development:
+    ensure: "present"
+    source: "puppet:///modules/private/rietveld-auth-users.json"

[Felix Dahlke, 2015/03/21 20:53:06]

Can't we set this outisde private-stub? Seems a lot like this would be the same
file/path for both develompent and production, the file contents make the
difference.

[mathias, 2015/03/21 23:47:26]

Not only the contents of the file are specific to the development environment -
the very requirement for this fixture is specific as well. In other words:
Outside private-stub, this snippet would introduce a non-required new
requirement for any future use of the rietveld module. 

Sure, we'll probably do something similar in production, but that is only
circumstantial anyway. It's quite possible, for example, that we decide to
always have some test data set up in development (but of course not in
production). That could be in another fixture. Or the same. It just does not
matter when handled in private, and does not interfere with any requirement from
any other environment.

PS: One should think of module "private" as "environment", because that's
actually what it is - environment-specific setup. The fact that we maintain our
production environment data in a confidential repo is just unimporant for the
Puppet logic. Also, one would not feel the need to justify the existence of the
module if named slightly different.. ;-)

+