Comment 3 for bug 1739646

As much as I would like us to default to enforce, I think there will be existing installation which will break as I am willing to bet that there are people who rely on this (as a matter of fact, I know some of our customers do this because it's easier than creating and deleting volumes).

We'd ideally work to transition them out but I can imagine it being a surprise to a user. I think a more sensible thing is to introduce the flag set to non-enforcing but with a warning when the service starts that in <foo>-release, this will be defaulted to enforce.

I'm not sure about the feasibility and the ability to detect if we're using the default value *or* if it was manually added by the deployed in the config.