Add a CodeCommit Repo
This topic outlines how to use AWS CodeCommit as a source repo with your Harness account and Applications. You can pull source files, such as manifests, specs, and config files, from your Source Repo as part of setting up your Harness Service and other entities.
In this topic:
- Before You Begin
- Step 1: Add Source Repo Provider
- Step 2: Display Name
- Step 3: Git Repo or Git Account
- Step 4: HTTPS/SSH
- Step 5: URL
- Step 6: Username and Password/Token
- Step 7: SSH Key
- Step 8: Branch Name
- Step 9: Customize Commit Attributes
- Step 10: Usage Scope
- Step 11: Test and Save
Before You Begin
Step 1: Add Source Repo Provider
To add a source repo, do the following:
- Click Setup.
- Click Connectors.
- Click Source Repo Providers, and then click Add Source Repo Provider. The Git Connector settings appear.
Step 2: Display Name
Enter a name for the repo connection. This is the name you will select when you sync your Harness account and applications in Configuration as Code.You could create a Source Repo Provider for the Harness admin account, such as Admin_CodeCommit. Later, you can create a Source Repo account for each Harness user, such as J_User_CodeCommit.
Step 3: Git Repo or Git Account
You can add a connection to your entire Git account or just a repo in the account. Selecting a Git account enables you to use one Source Repo Connector for all of your subordinate repos.
Later when you test this connection, you will use a repo in the account.
In either case, when you use the Connector later in Harness, you will specify which repo to use.
Step 4: HTTPS/SSH
Select HTTPS or SSH for the connection. You will need to provide the protocol-relevant URL in URL. If you use Two-Factor Authentication for your Git repo, connect over HTTPS or SSH.
ssh-keygen -t rsa -m PEM
-m PEMensure that the key is RSA.
Next, follow the prompts to create the PEM key. For more information, see the ssh-keygen man page and Connecting to GitHub with SSH.
Step 5: URL
Enter the URL for your Git repo. Ensure that it matches the option you selected in HTTPS/SSH.
If you selected Git Repo in Type, enter the full URL for the repo, such as
If you selected Git Account in Type, enter the URL without the repo name, like
https://github.com/account-name. When you use this Source Repo Provider in a Harness setting you will be prompted to provide a repo name.
Step 6: Username and Password/Token
In Select Encrypted Password/Token, select or create a new Harness Encrypted Text secret for the credentials of your CodeCommit user account.
Step 7: SSH Key
If you selected SSH as the connection protocol, you must add the SSH Key for use with the connection.
In SSH Key, select or create a new Harness Encrypted Text secret.
If you added a key in Harness Secrets Management, you can select it here. To add a new key, click the drop-down and select Add New SSH Key. The SSH Configuration dialog appears.
In User Name, enter the SSH Key ID that was generated when you uploaded your SSH public key to CodeCommit.
In Credentials, paste in the key or key file path, enter a display name, and then click Submit.
Step 8: Branch Name
If you selected Git Repo in Type, enter the branch name to sync with Harness, such as master, dev, or myAppName. Do not enter the full URL to the branch.
Step 9: Customize Commit Attributes
Do not use this option with CodeCommit.
Step 10: Usage Scope
For HTTPS connections, usage scope is inherited from the secret you entered in Select Encrypted Password/Token.
For SSH, connections, select the Harness Applications and Environments where the connection may be used.
Step 11: Test and Save
To finish configuring this Source Repo Provider:
- Click Test. Harness verifies the settings you entered. If you selected Git Account in Type, you need to provide a subordinate repo to test with.
- When testing is successful, click Submit. This Source Repo Provider is now added to Harness.