Document that keeping the global config in All-Projects may be dangerous
If the global code owners configuration is maintained in All-Projects,
rather than in gerrit.config, configuration changes are effective
immediately. Mention that this can also be a disadvantage as it means
that also bad config changes are effective immediately.
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ie0a286a94c292eead15780bf0dbac79400a801d3
diff --git a/resources/Documentation/config-faqs.md b/resources/Documentation/config-faqs.md
index 8e0ba49..dc8c6a5 100644
--- a/resources/Documentation/config-faqs.md
+++ b/resources/Documentation/config-faqs.md
@@ -145,7 +145,9 @@
preferred can depend on the system setup, e.g. changes to `gerrit.config` may be
harder to do and require a multi-day rollout, whereas changes of the
`All-Projects` configuration can be done through the [REST
-API](rest-api.html#update-code-owner-project-config) and are always instant.
+API](rest-api.html#update-code-owner-project-config) and are always instant
+(this can also be a disadvantage as it means that also bad config changes are
+effective immediately).
**NOTE:** Any configuration that is done in `All-Projects` overrides the
corresponding configuration that is inherited from `gerrit.config`.
