In addition, in the Repositories section of the Basic settings screen you select the Available Repositories you want to include in the new virtual repository and move them to the Selected Repositories list.
This list can be re-ordered by dragging and dropping within the Selected Repositories list.
The Included Repositories section displays the effective list of actual repositories included in this virtual repository. If any of the available repositories you have selected are themselves virtual repositories, then the Included Repositories section will display the local and remote repositories included within them. The Included Repository list is automatically updated in case any of the nested virtual repositories change.
The search/resolution order when requesting artifacts from a virtual repository is always:
The order within these categories is controlled by the order they are presented in the Selected Repositories list.
When fulfilling a request for the latest version of an artifact from a virtual repository, JFrog Container Registry will search all the included repositories to ensure it retrieves the latest version. This means that JFrog Container Registry will still search the remote repository even if it finds a version of the artifact in a local or cache repository, to be certain of returning the most current one. If the remote repository is found to have the latest version, JFrog Container Registry will download it and update the remote repository cache.
Nesting is a unique feature in JFrog Container Registry and facilitates more flexibility in using virtual repositories.
You should take care not to create an "infinite loop" of nested repositories. JFrog Container Registry analyzes the internal composition of virtual repositories and will issue a warning if the virtual repository can not be resolved due to invalid nesting.
The ability to define and Includes Pattern and an Excludes Pattern for virtual repositories (especially when nesting is used) provides a powerful tool you can use to manage artifact requests in your organization.
For example, your organization may have its own artifacts which are hosted both internally in a local repository, but also in a remote repository. For optimal performance, you would want these artifacts to be accessed from the local repository rather than from the remote one. To enforce this policy, you can define a virtual repository called "remote-repos" which includes the full set of remote repositories accessed by your organization, and then specify an Excludes Pattern with your organization's groupID. in this way, any attempt to access your internal artifact from a remote repository would be rejected.
Consider another example in which you wish to define a virtual repository for your developers, however you wish to keep certain artifacts hidden from them. This could be achieved by defining an Excludes Pattern based on groupId, source or version.
JFrog Container Registry supports deploying artifacts to a virtual repository. For example you can use
docker push to deploy packages to a virtual repository.
For more details, please refer to Deploying Artifacts.
JFrog Container Registry Requests Can Retrieve Remote Artifacts
|An JFrog Container Registry instance may request artifacts from a virtual repository in another JFrog Container Registry instance. This checkbox specifies whether the virtual repository should search through remote repositories when trying to resolve an artifact requested by another JFrog Container Registry instance. For example, you can use this feature when JFrog Container Registry is deployed in a mesh (grid) architecture, and you do not want all remote instances of JFrog Container Registry to act as proxies for other JFrog Container Registry instances.|