Strengthen the caution about allowed-projects

Make it more clear that it can be dangerous to override this.

Change-Id: I34d3ec1a68bf9217552d6d7d1e1ce74830f6c7c6
This commit is contained in:
James E. Blair 2019-06-24 15:30:51 -07:00
parent 9021fdf8bb
commit f307b71edf
1 changed files with 4 additions and 2 deletions

View File

@ -1125,7 +1125,8 @@ Here is an example of two job definitions:
:term:`untrusted-project`, `allowed-projects` is automatically
set to the current project only, and can not be overridden.
However, a :term:`config-project` may still add such a job to
any project's pipeline.
any project's pipeline. Apply caution when doing so as other
projects may be able to expose the source project's secrets.
.. warning::
@ -1525,7 +1526,8 @@ projects which can invoke that job. If a job with secrets is defined
in an `untrusted-project`, `allowed-projects` is automatically set to
that project only, and can not be overridden (though a
:term:`config-project` may still add the job to any project's pipeline
regardless of this setting).
regardless of this setting; do so with caution as other projects may
expose the source project's secrets).
Secrets, like most configuration items, are unique within a tenant,
though a secret may be defined on multiple branches of the same