For CI/CD, we would recommend that you create a bot Cloudsmith user in your organization.
If you've got an email system that supports it, you could append "+cloudsmithbot" to your email prefix. E.g. "[email protected]" - This will still go to your "[email protected]" email but will be treated as separate by us.
Once you've got the bot user in, you can create a team for them, and assign them as little privileges as they need to do their job (usually "Write" access on a key repository for uploading).
In the future, we'll be supporting scoped API keys at which point it won't be necessary to create least-privilege users (but probably still recommended for CI/CD).
Updated 10 months ago