config-faqs.md: Mention the capability that is needed for using --debug
Calling the List Code Owners REST endpoints with the --debug option
requires the caller to have the Check Code Owner capability, but it was
not mentioned.
Signed-off-by: Edwin Kempin <ekempin@google.com>
Change-Id: Ief2b596020545af21ae61c4f576ff48b64bad5b4
diff --git a/resources/Documentation/config-faqs.md b/resources/Documentation/config-faqs.md
index 8766ffd..be0bfb0 100644
--- a/resources/Documentation/config-faqs.md
+++ b/resources/Documentation/config-faqs.md
@@ -124,13 +124,15 @@
* Use the `--debug` option of the [List Code
Owners](rest-api.html#list-code-owners-for-path-in-branch) REST endpoints to
- get debug logs included into the response.
+ get debug logs included into the response (requires the caller
+ to be host administrator or have the [Check Code Owner
+ capability](rest-api.html#checkCodeOwner)).
* Check the code owner config files for issues by calling the [Check Code Owner
- Config File REST endpoint](rest-api.html#check-code-owner-config-files)
+ Config File REST endpoint](rest-api.html#check-code-owner-config-files).
* Check the code ownership of a user for a certain path by calling the [Check
Code Owner REST endpoint](rest-api.html#check-code-owner) (requires the caller
to be host administrator or have the [Check Code Owner
- capability](rest-api.html#checkCodeOwner))
+ capability](rest-api.html#checkCodeOwner)).
Bugs with the @PLUGIN@ plugin should be filed as issues for the Gerrit team, but
only after other causes have been excluded.
