Curation Federation

Configuring Curation Federation ensures that repositories, conditions, labels, and policies created on the controller are consistently federated to all follower sites. This process allows organizations to enforce standardized governance rules across multiple JPD instances, while still enabling followers to maintain local flexibility where appropriate.

To Learn about how to define a federation that syncs Curation policies and metadata across servers in your JFrog subscription.

In this section, you will learn how each federated entity behaves in a federated environment:

• Remote Repositories – Connections created on the controller are propagated to all followers, ensuring consistent repository configurations.
• Conditions – Controller-defined conditions are federated as read-only on followers, while followers may create additional local conditions.
• Labels – Federated labels are available for use on followers in read-only mode, with the option for followers to add their own local labels.
• Policies – Policies defined on the controller can be applied organization-wide or by repository type, incorporating federated conditions and labels.

This configuration process ensures that global rules are consistently enforced across the organization while giving followers the ability to extend governance through local additions.

Connecting Remote Repositories

When a remote repository of a specific type (e.g., NPM) is connected to the controller, the connection is federated to all followers. Followers cannot disconnect this federated connection. If a follower does not yet have that repository type, the configuration will be applied automatically if and when the repository is created.

Followers retain limited local control:

• They can exclude specific multi-site remote repositories via local settings.
• They can add new repository types that are not configured on the controller. For example, if the controller does not configure a PyPI repository, a follower may configure one locally for its own use.

Conditions

All conditions created on the controller are federated to followers. These federated conditions are read-only on follower sites and cannot be modified. Followers can, however, create their own local conditions. These are separate from the federated ones and are not propagated back to the controller. Local conditions may still use read-only federated conditions as building blocks for policies.

User Events and Logs

All curation and federation events are logged for review:

• Controller Events: Show when federation started, what changes were applied, and which entities were affected.
• Follower Events: Show when changes were received and applied locally. Clicking on any event row will provide details such as when the federation started running on the controller and when it was received on the follower. This helps with gap analysis in case changes took a long time to propagate.

Reviewing logs provides insight into federation behavior and aids troubleshooting when combined with error messages.