@tony.kay would you accept a PR to guardrails that suppresses the prints to stdout on startup notifying that guardrails is enabled when some config opt or jvm property is set? we use guardrails a lot in development of course but also in some prod-like situations where it's useful. it would be a nice convenience to suppress that message
I’m not opposed…what were you thinking in terms of implementation? I feel like the message is pretty important, and never considered that it would be a problem in any way since as you said you only see it in dev, and it isn’t meant to be used in production….and in both cases knowing that it’s active (and how) is pretty important info. I guess an env variable or jvm prop would be ok.