Harness is a self-service Continous Delivery platform that allows engineers and DevOps to build, test, deploy, and verify software, on-demand.
Harness also provides Continuous Integration through Drone CI
To authenticate to a private Cloudsmith repository, you first need to add either your Cloudsmith API Key or a Cloudsmith Entitlement Token in Harness as an encrypted secret in a Secrets Manager.
Harness includes a built-in Secrets Manager (Harness Vault) and also supports many third-party Secrets Managers. Please refer to the Harness documentation for details of how to configure your chosen Secrets Manager.
Please see the Entitlements documentation for details of how to create and retrieve Entitlement Tokens via the Cloudsmith CLI or the Cloudsmith Website.
Cloudsmith Repositories are added to Harness as an Artifact Server. At a minimum you need to provide the following information to configure an Artifact Server:
The type of Artifact Server, select "Docker Registry".
A name for the Artifact Server within Harness. You can use any name that you wish here.
Docker Registry URL
The Cloudsmith Username, or an Entitlement Token name that you wish to authenticate with Please see the Cloudsmith Docker Registry documentation for details of authentication methods.
Select Encrypted Password
The Encrypted Secret that you wish to use for Authentication. Please see the Harness documentation for further information on Encrypted Secrets.
A Harness Service is where you specify the artifact that you want to deploy.
Add the following to specify a Docker image :
A name within Harness for the artifact.
The "Display Name" specified when configuring the Artifact Server.
Docker Image Name
The name of the Docker image.
Updated about a month ago