cd258e5a1d
The upload-afs role is actually fairly specialised for uploading docs with its root-marker scheme. As we're moving more parts of our infrastructure to publish via AFS I think it's worth making this quite explicit by renaming the upload-afs role to upload-afs-roots. This should be transparent as we call the renamed role, and once callers have been migrated we can use the usual deprecation process. Add a partner role, upload-afs-synchronize, which is more of a straight copy with options to synchronize. This will be suitable for uploading tarball and release artifacts. This is similar in concept to the promotion job used by zuul [1], but in this case will be focused on the extant publishing jobs in project-config which don't currently use the artifact-reporting/promote process. [1] https://opendev.org/opendev/base-jobs/src/branch/master/playbooks/artifacts/promote.yaml#L39 Change-Id: I493d8829e3fd98e84f1b8f0e776e7ba41abf16c2 Story: #2006598 Task: #38600
10 lines
240 B
ReStructuredText
10 lines
240 B
ReStructuredText
AFS Roles
|
|
=========
|
|
|
|
.. zuul:autorole:: destroy-afs-token
|
|
.. zuul:autorole:: upload-afs
|
|
.. zuul:autorole:: upload-afs-roots
|
|
.. zuul:autorole:: upload-afs-synchronize
|
|
.. zuul:autorole:: create-afs-token
|
|
.. zuul:autorole:: release-afs-volume
|