64 lines
1.6 KiB
Markdown
64 lines
1.6 KiB
Markdown
# Creating fedscm-admin token for releng
|
|
|
|
Members of the releng team that are processing fedora-scm-requests are using
|
|
the CLI tool: fedscm-admin.
|
|
They will need a few access to be able to use this tool properly:
|
|
|
|
- they will need a token to add/adjust things in PDC
|
|
- they will need a token to create/modify things on src.fp.o
|
|
- they will need a token to act on the fedora-scm-requests repo on pagure.io (this one
|
|
can be created by themselves once they are given the access)
|
|
|
|
This doc covers the second point.
|
|
|
|
|
|
* Log into pkgs01.iad2.fedoraproject.org
|
|
* Run the following command:
|
|
|
|
````
|
|
pagure-admin admin-token create <username> <expiration_date>
|
|
````
|
|
|
|
For example:
|
|
|
|
````
|
|
pagure-admin admin-token create petersen 2020-06-30
|
|
````
|
|
|
|
This will ask you which ACLs you want this token to have, select:
|
|
- create_project
|
|
- modify_project
|
|
- create_branch
|
|
- generate_acls_project
|
|
|
|
Then confirm the creation of the token.
|
|
|
|
Once the token is created, you can check that it was properly created by doing:
|
|
|
|
````
|
|
pagure-admin admin-token list --user<username>
|
|
````
|
|
|
|
This will return all the active admin-token of that user. You should find the
|
|
newly created token there.
|
|
|
|
You can also check the ACLs of that token by doing:
|
|
````
|
|
pagure-admin admin-token info <token>
|
|
````
|
|
|
|
Finally, you can edit the expiration date of the token by doing:
|
|
````
|
|
pagure-admin admin-token update <token> <expiration_date>
|
|
````
|
|
|
|
For example:
|
|
````
|
|
pagure-admin admin-token update foobarbaz 2000-01-01
|
|
````
|
|
|
|
|
|
|
|
/!\ Note: there is no need to send that token to the user, simply ask them to
|
|
check their API tokens in their settings' page. It will be shown there :)
|
|
|