Store workspace secrets, create or revoke Harbor API keys, and choose the right credential model for local use, CI, or plugins. Use when access control and credentials matter.
Use this skill when the task is about credentials that Harbor itself manages: workspace secrets for tools and API keys for programmatic access.
hrbr secrets create and hrbr secrets list for workspace secrets.read secret value back flow.hrbr api-keys create for long-lived programmatic access.hrbr api-keys revoke --key-id <id> to invalidate compromised or obsolete keys.hrbr-env-sync for git-project .env files.hrbr
hrbr workspaces list
hrbr secrets list
hrbr api-keys list
hrbr secrets create --name openai-api-key --value <value>
hrbr api-keys create --name github-actions
hrbr api-keys list --full
hrbr api-keys revoke --key-id <id>
hrbr secrets list
hrbr secrets create --name github-token --value <value>
hrbr api-keys list
hrbr api-keys create --name local-dev
hrbr api-keys list --full
hrbr api-keys revoke --key-id <id>
.env files across clones → use hrbr env instead.openai-api-key, prod-database-url, or stripe-webhook-secret.hrbr api-keys list --full and use the key ID, not just the prefix.hrbr env push / hrbr env pull.