Feat: Update management-domains Federated Catalog docs. #1530
Conversation
|
|
||
|  | ||
| ### Deployment Topologies |
There was a problem hiding this comment.
I don't think there is much value in copy-pasting documentation content that is already present in the upstream repo. In particular image material might be copyrighted there, so I'm not sure we even could legally copy it without attribution.
Instead, I would document how to set up a catalog server, i.e. which assets must be added there, how the resulting federated catalog looks like (flattened vs hierarchical), etc.
|
This pull request is stale because it has been open for 7 days with no activity. |
|
This pull request is stale because it has been open for 7 days with no activity. |
|
This pull request is stale because it has been open for 7 days with no activity. |
|
This pull request was closed because it has been inactive for 7 days since being marked as stale. |
|
@jimmarino @paullatzelsperger @ndr-brt can this PR be reopened, please? |
|
|
This pull request is stale because it has been open for 7 days with no activity. |
bmg13
changed the title
WHAT
Suggestion update for Federated Catalog usage documentation.
WHY
To keep Federated Catalog documentation up-to-date.
FURTHER NOTES
Still in draft since is part of a larger Federated Catalog changes that are still to be aligned.
Management Deployments Documentation was based in this one https://github.com/eclipse-edc/Connector/blob/main/docs/developer/management-domains/management-domains.md#type-2c-catalog-servercontrol-plane-with-data-plane-runtime
Related with
eclipse-tractusx/sig-release#736
#1585