I’ve been reading everyone’s message about ENC and...
# puppet
m
I’ve been reading everyone’s message about ENC and it’s been quite interesting. But now I’m wondering if I’m introducing an anti-pattern to my ENC. Some of you mention malicious code injected by an attacker but dangerous code can also be introduced by legitimate users. For example a wrong regex could add a class to the entire estate. I’ve implemented a feature that prevents adding entries that overlap with existing entries. For example, if I have a regex pattern like
/test-foo/
another pattern like
/test-f/
will be detected and blocked (see image). It works also the way around (if you added
test-f
first,
test-foo
will also be rejected. I find it useful but I’m wondering if it’s an anti-pattern (because it contradicts the merge logic). Is it a feature that a user must be able to disable or to override? p.s.: I have also added the "Spring Cleaning" which detects orphan definitions, that are not matching anything on the puppetDB, and I took the idea from @CVQuesty Dashboard to add "Unclassified hosts" 😉