Egeria's Git Repositories
Egeria has an increasing number of git repositories and this page summarizes what they are for, how they are used and how they are governed. The picture below shows the repositories grouped by purpose:
Project wide repositories cover multiple aspects of the Egeria project's capabilities.
UI repositories cover different aspects of Egeria's user interfaces. The split is driven by the technology and skills needed to work on the content.
Connector repositories host one or more connectors. They are kept in separate repositories because each brings the dependencies of the technologies they connect to. By separating the connectors out from the main egeria code base, it is easier to both inderstand and control the dependencies that occur in an Egeria deployment to just those components that the deployment needs.
Deployment repositories cover capabilities used in the set up or management of an Egeria deployment
Historial repositories contain work that is out of date. Typically it has been superceeded by the other repositories. However, this new effort may still be work in progress.
The table below summarizes the purpose, use and management of each repository. Details of dependencies between artifaces are covered on the specific artifact pages to come.
Repository | | | | | | | | | | | | | | | | | | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Purpose | Code and resources for contributors to Egeria's core capability. | Project-wide documentation for consumers and potential collaborators. This is the starting point for most people. Links to content in other repositories as needed. | Resources and code for assembling simple samples. | Projects for developers to build integrations to Egeria using different techniques, connectors and APIs. | General metadata | Specialist Egeria user | Graph component for UI. | Shared components for UI. | Testing components for UI. | Native XTDB (Crux) repository | Repository connector to the | Connectors to | Connectors to | Various database connectors. | Kubernettes operator. | Kubernettes helm charts. | Data governance guidance. | Test integration between Egeria and Palisade. |
Audience | Egeria core contributors. | Everyone | Egeria contributors building new samples. | Developers with responsibility for building integrations to Egeria. | Contributors to Egeria's UIs. | Contributors to Egeria's UIs. | Contributors to Egeria's UIs. | Contributors to Egeria's UIs. | Contributors to Egeria's UIs. | Egeria core contributors. | Contributors to Egeria's connector catalog | Contributors to Egeria's connector catalog | Contributors to Egeria's connector catalog | Contributors to Egeria's connector catalog | Contributors to Egeria's deployment utilties. | Contributors to Egeria's deployment utilties. | Contributors to egeria-docs | Egeria core contributors. |
Primary technologies | Java | Markdown | Java | Java | Javascript | Javascript | Javascript | Javascript | NodeJS | Java | Java | Java | Java | Java | Go, Kubernettes | Helm, Kubernettes | Markdown | Java |
Provides Artifacts |
| Project website
| Various sample Java components. | Instructions, sample code and other resources | Static content server for | Presentation Server | javascript components | javascript components | Connector Archive | Connector Archive | Connector Archive | Connector Archive | Connector Archive | |||||
Owners | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria UI Maintainers | Egeria UI Maintainers | Egeria UI Maintainers | Egeria UI Maintainers | Egeria UI Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers | Egeria Maintainers |
Security Scans |
| none | none | none |
|
| none | none | none |
|
|
|
|
| none | none | none | none |