docs: explicit when key is dynamic in services #104
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It isn't clear to all users that
xxx
- a map of the formkey: value
means that the user can specify their own key. This PR adds additional examples to help discern whether the key is statically defined by notifications-engine or defined by the end user.This follows questions asked on #argo-cd-notifications
I also reflected this in argoproj/argo-cd: argoproj/argo-cd#10589