+
+ There are many circumstances where permissions for repositories need to be shared across those repositories (continuous integration, etc).
+ To support this case, Quay allows the use of robot accounts which can be created in the user/organization's admin view and can be
+ shared by multiple repositories that are owned by that user or organization.
+
+
+
+ - Robot accounts can be managed in the user or organization admin's interface
+
- Adding a robot account: Click "Create Robot Account" and enter a name for the account. The username will become namespace+accountname where "namespace" is the name of the user or organiaztion.
+
- Setting permissions: Permissions can be granted to a robot account in a repository by adding that account like any other user or team.
+
- Deleting a robot account: A robot account can be deleted by clicking the X and then clicking Delete
+
- Using a robot account: To use the robot account, the following credentials can be used:
+
+ - Username
- namespace+accountname (Example: mycompany+deploy)
+ - Password
- (token value can be found by clicking on the robot account in the admin panel)
+ - Email
- This value is ignored, any value may be used.
+
+
+
- There are many circumstances where it makes sense to not use a user's username and password (deployment scripts, etc).
- To support this case, Quay allows the use of access tokens which can be created on a repository and have read and/or write
+ For per-repository token authentication, Quay allows the use of access tokens which can be created on a repository and have read and/or write
permissions, without any passwords.