[trafficcontrol] branch master updated: updates content invalidation permission documentation (#3194)

[ra...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rawlin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git


The following commit(s) were added to refs/heads/master by this push:
     new 57f650e  updates content invalidation permission documentation (#3194)
57f650e is described below

commit 57f650ee71a903add9c6d1821a420c8d1eca4e13
Author: Jeremy Mitchell <mi...@users.noreply.github.com>
AuthorDate: Tue Jan 8 15:19:18 2019 -0700

    updates content invalidation permission documentation (#3194)
---
 docs/source/api/user_current_jobs.rst | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/docs/source/api/user_current_jobs.rst b/docs/source/api/user_current_jobs.rst
index d05d2fb..cf926bd 100644
--- a/docs/source/api/user_current_jobs.rst
+++ b/docs/source/api/user_current_jobs.rst
@@ -129,8 +129,6 @@ Request Structure
 -----------------
 :dsId: The integral, unique identifier of the Delivery Service on which the revalidation job shall operate
 
-	.. note:: As well as satisfying tenancy and role authentication\ [1]_, the user must have been assigned the Delivery Service identified by this integral, unique identifier.
-
 :regex: This should be a `PCRE <http://www.pcre.org/>`_-compatible regular expression for the path to match for forcing the revalidation
 
 	.. warning:: This is concatenated directly to the origin URL of the Delivery Service identified by ``dsId`` to make the full regular expression. Thus it is not necessary to restate the URL but it should be noted that if the origin URL does not end with a backslash (``/``) then this should begin with an escaped backslash to ensure proper behavior (otherwise it will match against FQDNs, which leads to undefined behavior in Traffic Control).
@@ -188,4 +186,4 @@ Response Structure
 		}
 	]}
 
-.. [1] Regardless of role or tenancy, a user may only create content revalidation jobs on Delivery Services assigned to him or her. A role is only required if tenancy is not used; if tenancy is used by Traffic Control, then the user will be able to create the content revalidation job on Delivery Services assigned to his or her user and tenant regardless of role. This means that **even read-only users can create content invalidation jobs for Delivery Services owned by themselves and their [...]
+.. [1] A role is only required if tenancy is not used; if tenancy is used by Traffic Control, then the user will be able to create the content revalidation job on Delivery Services scoped to his or her tenancy regardless of role. This means that **even read-only users can create content invalidation jobs for Delivery Services scoped to their tenancy**. This behavior is considered a bug, and it is tracked by `GitHub Issue #3116 <https://github.com/apache/trafficcontrol/issues/3116>`_.