Chapter 2. Customizing your installation

Procedure

1. Before you can integrate your instance of ACS, you need an API token and the central endpoint URL.

   1. Follow the instructions for the prerequisites here to create an API token. Save the token in private.env.
   2. Follow the instructions here to configure your endpoint. Save the URL in private.env.

2. In your rhtap-cli container, run the integration command. Replace $ACS_ENDPOINT with your ACS central endpoint URL, and $ACS_TOKEN with your ACS API token.

   bash-5.1$ rhtap-cli integration acs --endpoint="$ACS_ENDPOINT" --token="$ACS_TOKEN"

Procedure:

1. In your web browser, login to Quay. On the right side of the banner, select your username and select Account Settings from the dropdown menu.
2. On your user settings page, under Docker CLI Password, select Generate Encrypted Password. In the popup window, enter your password to authenticate.
3. Next, still in the popup window, select Docker Configuration > View [username]-auth.json. Copy the string, without the quotation marks, following "auth":.
4. In your private.env file, label and create the Docker configuration value with the following format, using your username and auth token where appropriate: {"auths": {"quay.io": {"auth": "[auth token]","email": ""}}}
5. Back in the Quay UI, return to the default Repositories page. On the right side, under Users and Organizations, select the Quay organization you want to use for RHTAP.
6. From the tabs on the left side, select Applications.
7. Click Create New Application. Give your application a name.
8. Click on the application’s name.
9. From the tabs on the left, select Generate Token.
10. From the options for permissions for the token, select View all visible repositories.
11. Click Generate Access Token.
12. Click Authorize Applicaiton.
13. The UI displays an access token. Label and save this token in private.env, too.

14. In your rhtap-cli container, run the following command to integrate your instance of Quay. Replace $QUAY_DOCKERCONFIGJSON with the Docker configuration value. Replace $QUAY_TOKEN with the token you just generated. And replace $QUAY_URL with the address for your instance of Quay (https://quay.io if you have not installed Quay in your cluster).

    bash-5.1$ rhtap-cli integration quay --dockerconfigjson='$QUAY_DOCKERCONFIGJSON' --token="$QUAY_TOKEN" --url="$QUAY_URL"

Procedure

1. In your rhtap-cli container, run the integration command. Replace $BB_USERNAME with your Bitbucket username, and $BB_TOKEN with your Bitbucket access tokens. If you are integrating with a custom Bitbucket host, replace $BB_URL with you Bitbucket host URL. If you are using the default bitbucket.org host, you can remove the --host option.

   bash-5.1$ rhtap-cli integration bitbucket --username="$BB_USERNAME" --app-password="$BB_TOKEN" --host="$BB_URL"

Procedure

1. In your rhtap-cli container, run the integration command. Replace $GL_API_TOKEN with your GitLab API token. If you are integrating with a custom GitLab host, replace $GL_URL with you GitLab host URL. If you are using the default gitlab.com host, you can remove the --host option.

   bash-5.1$ rhtap-cli integration gitlab --token="$GL_API_TOKEN" --host="$GL_URL"

Procedure

1. In your rhtap-cli container, run the integration command. Replace $JK_API_TOKEN with your Jenkins API token, $JK_URL with you Jenkins instance URL, $JK_USERNAME with your Jenkins user ID.

   bash-5.1$ rhtap-cli integration jenkins --token="$JK_API_TOKEN" --url="$JK_URL" --username="$JK_USERNAME"

Procedure

1. In the Artifactory UI, in the Administration view, click the green Set Up Client/CI Tool button next to the repository that you want to use.
2. Select Docker Client

3. Follow the UI instructions to authenticate in your CLI.

   1. The UI generates a token to use as a password. Make sure to save it in private.env.
   2. When you login to JFrog in your CLI, you should get a message saying your password has been stored in a location such as ~/.docker/config.json. If you do not see this message, a later step in this procedure explains what to do.

4. In your rhtap-cli container, run the integration command. Set the value of AF_URL to the URL of your instance (for example, "https://myusername.jfrog.io"). Set the value of AF_DOCKERCONFIGJSON to the contents of the file where your password was stored. Set the value of AF_API_TOKEN to the token that JFrog generated.

   bash-5.1$ rhtap-cli integration artifactory --url="$AF_URL" --dockerconfigjson='$AF_DOCKERCONFIGJSON' --token="$AF_API_TOKEN"