-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: clarify mutate exisitng vs standard mutate policy #1293
Conversation
Signed-off-by: ShutingZhao <shuting@nirmata.com>
This is already present in the same doc in the next paragraph:
|
Yes, but I want to distinguish between a mutate existing policy and a standard mutate policy. The current doc doesn't seem to define what is a standard mutate policy. Could you help suggest? |
Yes, I was not clear on the difference as well. It will be good to state explicitly early in the text, when we introduce the concept. |
The docs for this section state, in the following order:
If you feel this isn't clear, it should go in the third section which is the paragraph under the "two important implications". Maybe something like:
|
Signed-off-by: ShutingZhao <shuting@nirmata.com>
Signed-off-by: ShutingZhao <shuting@nirmata.com>
Updated, please take a look, thanks! |
This PR clarifies stand mutate policy VS mutate existing policy. This is from Kyveno Slack: