Madelyn Olson

@nermiller I think so, the security section is pretty old and definitely needs to be updated.

I would be against this. It seems very niche to have deployments where you would have multiple administrators with different config permissions.

I think you highlight an important dimension, which is we have a bunch of configs which probably shouldn't be global configs: * `notify-keyspace-events`: A client should be able to listen...

> bottom line is that i think we probably can't avoid having a global configs that need to be controlled by the application. maybe we should have designated s different...

@valkey-io/core-team Please 👍 and 👎 for this since it's a major issue.

For some components, like check-aof, we might have a problem where they expect the name to look a certain way. We should probably rewrite them so that they are agnostic...

@placeholderkv/core-team Will you also comment here when you get a chance

> I think we can avoid one-offs and wait until RC2 to resolve all compat issues holistically. This seems like a larger scope than we need. I think the original...

> [adding two new info fields] is a NO for me I need to understand why this is a blocker. The reason given (counting number of the lines) doesn't seem...

Oh, I see, you are concerned because people might be *explicitly* looking for the 2nd and 3rd line. Would it alleviate the concern if we placed them at the bottom...