| indeed. There should be a viable alternative when depcrecation message is thrown. More in general, I see a reason to unify, group, merge, join all puppet configuration files, in one, unique, single file (have you neer tried to install Salt-Stack? Even the DB configuration is in the same file). But I hardly see a reason for shuffling things around. More hardly I see a reason for having, conf, yaml, ruby (see Puppetfile), hocon, ini, cfg.... After an upgrade the usual mess becomes a nightmare, because you don't know if that specific configuration is stale and it's not in use with the new version, or if it must be there. We need one single puppet.conf, with everything inside |
