Skip to content

Latest commit

 

History

History
61 lines (58 loc) · 2.76 KB

proc_configuring-custom-alternate-content-sources.adoc

File metadata and controls

61 lines (58 loc) · 2.76 KB

Configuring Custom Alternate Content Sources

Prerequisites

  • If the repository requires SSL authentication, import the SSL certificate and key to the {Project}. For more information, see {ContentManagementDocURL}Importing_Custom_SSL_Certificates_content-management[Importing Custom SSL Certificates] in {ContentManagementDocTitle}.

  • Note that the alternate content source paths consist of a base URL appended with the subpaths that you provide. For example, if your base URL is https://{server-example-com} and your subpaths are rhel7/ and rhel8/, then both https://{server-example-com}/rhel7/ and https://{server-example-com}/rhel8/ will be searched.

Procedure

  1. In the {ProjectWebUI}, navigate to Content > Alternate Content Sources.

  2. Click Add Source and set the Source type as Custom.

  3. Select the Content type.

  4. In the Name field, enter a name for the alternate content source.

  5. Optional: In the the Description field, provide a description for the ACS.

  6. Select {SmartProxies} to which the alternate content source is to be synced.

  7. Enter the Base URL of the alternate content source.

  8. Enter a comma-separated list of Subpaths.

  9. Provide the Manual Authentication or Content Authentication credentials, if these are needed.

  10. If SSL verification is required, enable Verify SSL and select the SSL CA certificate.

  11. Review details and click Add.

  12. Navigate to Content > Alternate Content Sources > click the vertical ellipsis next to the newly created alternate content source > Select Refresh.

CLI procedure

  1. On {ProjectServer}, enter the following command:

    # hammer alternate-content-source create \
--alternate-content-source-type custom \
--base-url "https://local-repo.example.com:port" \
--name "My_ACS_Name" \
--smart-proxy-ids My_{smart-proxy-context-titlecase}_ID

  2. Check if the newly created alternate content source is listed:

    # hammer alternate-content-source list

  3. Refresh the alternate content source:

    # hammer alternate-content-source refresh --id My_Alternate_Content_Source_ID

  4. Add the {SmartProxies} to which the alternate content source is to be synced:

    # hammer alternate-content-source update \
--id My_Alternate_Content_Source_ID \
--smart-proxy-ids My_{smart-proxy-context-titlecase}_ID

  5. Refresh the alternate content sources:

    # hammer alternate-content-source refresh --id My_Alternate_Content_Source_ID