Commit d95e13021727f5ecfe539ec46a4431747453d564 introduced another realm to our puppet repository, "labtest". I find this a very unfortunate construct — labtest hosts are not, by any definition of $realm, a separate realm. This is a dangerous pattern to follow, as these hosts are production hosts with production-level network and authentication access, for which $realm != production.
More practically speaking, it's a very ugly and non-DRY way of writing code and has resulted, among other things, to duplication of structures and code in a number of places — and in many cases, in divergence already. I was fixing our exim config today, and encountered modules/standard/templates/mail/exim4.minimal.labtest.erb, a pristine copy of production's introduced with 762a25bfbf57a0a3ff441eb2b55b38a596bc3189. etc. that I would have to manually keep in sync. Copying identical files around and keeping them in sync manually is never the right solution.
Before filing this task, it took me less than 5 minutes to find another place of duplication, network::constants, which has even resulted into divergence already that will soon cause some monitoring breakage: 47a0be200d90142564180014558627cc75549684 did not notice or update neon's references for the labtest realm, and you really can't blame them for that.
Let's just please get rid of the labtest realm ASAP.