Skip to content

Commit 6f71809

Browse files
authored
update capability for artifactory readme (#334)
1 parent 006a853 commit 6f71809

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

artifactory-automation/README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,15 +5,17 @@ Workflow that will automate the creation and updating of pull tokens to allow cu
55
For this workflow to run properly, you will need to create an [assumable identity](https://edu.chainguard.dev/chainguard/administration/custom-idps/custom-idps/) beforehand. It will need a role with the correctly scoped permissions.
66

77
## Creating the Role and Identity
8-
Create a role that matches the registry.pull_token_creator role.
8+
Create a role for artifactory that can create and delete pull tokens.
99
> [!IMPORTANT]
1010
> If you want to enable pruning of expired pull tokens, you must add identity.list and identity.delete capabilities.
1111
12-
`chainctl iam roles create artifactory --parent <your-organization> --capabilities apk.list,groups.list,identity.create,manifest.list,manifest.metadata.list,record_signatures.list,repo.list,role_bindings.create,roles.list,sboms.list,tag.list,vuln_reports.list,identity.list,identity.delete,apk.blobs.get,repo.blobs.get`
12+
1. Create a role with identity.delete capabilities:
1313

14+
`chainctl iam roles create token-delete --parent <your-organization> --capabilities identity.delete`
1415

15-
Create the assumable identity
16-
`chainctl iam identities create github artifactory --github-repo=<your-repository> --parent=<your-organization> --role artifactory`
16+
2. Create the assumable identity and bind the token-delete role:
17+
18+
`chainctl iam identities create github artifactory --github-repo=<your-repository> --parent=<your-organization> --role=token-delete,registry.pull_token_creator`
1719

1820

1921
## Example Workflow

0 commit comments

Comments
 (0)