Skip to content

Separate control-plane from federated-catalog #5863

Description

@ndr-brt

Feature Request

At the moment, the federatedcatalog-base-bom includes the control-plane-core modules, so a federated-catalog is running a whole connector (negotiations/transfer processes).
They should be better separated

Which Areas Would Be Affected?

e.g., DPF, CI, build, transfer, etc.

Why Is the Feature Desired?

Are there any requirements?

Who will sponsor this feature?

Please @-mention the committer that will sponsor your feature.

Solution Proposal

If possible, provide a (brief!) solution proposal.

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature_requestNew feature request, awaiting triagetriageall new issues awaiting classification

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions