In the repositories section, you can define master, image, and mirror repositories for products, fixes, and assets. You can reference repositories that are already defined in the template.

When you define an image repository, the repository definition must include the location parameter that specifies the path to the image file that contains the products or fixes:

When you define an asset repository, you must include the type and location parameters. The type parameter indicates the type of the repository (flatfile or git) and the location parameter specifies the path to the flatfile repository or the URL of the git repository. For example, to define an asset repository located in git:

In this example, credentials: NONE indicates that the git repository is public and does not require authentication to clone the repository. For information about the default common credentials configuration instances, see COMMON-CREDENTIALS Usage Notes.

To specify the user credentials required to connect to a repository, you can create an instance of the COMMON-CREDENTIALS type (with the authentication details for the repository), using the Command Central web user interface or the sagcc create configuration data command. Add the credentials parameter and refer to the alias of the COMMON-CREDENTIALS configuration instance you created for the repository as follows:

You can specify the value for the repo.product.credentials.alias, repo.product.credentials.alias, and repo.asset.credentials.alias parameters in the environments/default section, a separate properties file, or as argument of the apply composite template command. The parameters map to the alias of a common credentials configuration instance, for example: repo.product.credentials.alias: EMPOWER-CRED, where EMPOWER_CRED is the alias of the custom COMMON-CREDENTIALS-empower_cred configuration instance that defines the credentials for the Empower product and fix repositories. For information about creating common credentials configuration instances, see Configuration Types for Command Central and Platform Manager OSGI ENGINE.

You can also specify the alias directly as the value of the credentials parameter, for example:

For examples of repository definitions, see the sag-cc-repos, sag-cc-mirrors, and sag-cc-repos-assetsample templates .