@eventcatalog/generator-github

⚡️ GitHub Generator for EventCatalog

Pull and sync your schemas (e.g Avro, Protobuf, JSON) from GitHub to EventCatalog

Features: Sync your schemas from GitHub to EventCatalog. Keep schemas in sync with your producers and consumers documentation, attach them to domains, assign owners to your schemas and much more.

Read the Docs | Edit the Docs | View Demo

Core Features

• 📃 Pull and sync your schemas from your GitHub repository to EventCatalog
• 📃 Keep your schemas in sync with your producers and consumers documentation
• 📃 Supports any schema format (e.g Avro, Protobuf, JSON)
• 📃 Import all schemas, or specific folders/files
• ⭐ Go beyond a schema. Add semantic meaning to your schemas, business logic and much more. Help your developers and teams understand the meaning behind the schemas with clear documentation and visualisations.
• 📊 Visualise producers and consumers in your architecture (demo)
• ⭐ Download synced schemas from EventCatalog (e.g Avro, Protobuf, JSON) (demo)
• 📃 Assign schemas to events, commands and queries
• ⭐ Discoverability feature (search, filter and more) (demo)
• ⭐ And much more...

How it works

EventCatalog is technology agnostic, meaning it can integrate with any schemas, specs or brokers.

EventCatalog supports generators.

Generators are scripts are run to pre build to generate content in your catalog. Generators can use the EventCatalog SDK.

Many teams keep there schemas in GitHub. This is great as it allows you to version control your schemas and follow best practices (e.g pull requests, code reviews, etc).

Using this plugin you can pull your schemas from any GitHub repository and keep them in sync with your documentation. This let's you document your schemas, and architecture whilst keeping your schemas in your documentation up to date.

This is done by defining your generators in your eventcatalog.config.js file.

...
generators: [
    // Basic example mapping schemas from confluent schema registry to services without any topics
    [
      '@eventcatalog/generator-github',
      {
        // The GitHub repository to pull the schemas from
        repo: 'event-catalog/eventcatalog',
        // The path to the folder containing the schemas
        path: 'examples/default',
        // Here we define the services, we want to map the schemas to (producers/consumer relationships)
        services: [
          {
            id: 'Inventory Service',
            version: '1.0.0',
            sends: [{
              id: 'app.orders.created',
              version: '1.0.0', // optional, defaults to latest
              type: 'event', // event, command or query
              //  The path in your github repository to the schema
              schemaPath: 'domains/Orders/services/InventoryService/events/InventoryAdjusted/schema.avro',
            }],
            receives:[{
              id: 'app.orders.updated',
              version: '1.0.0', // optional, defaults to latest
              type: 'command', // command, query or event
              //  The path in your github repository to the schema
              schemaPath: 'domains/Orders/services/InventoryService/events/InventoryAdjusted/schema.avro',
            }]
          },
        ],
        // All the services are assigned to this domain (optional)
        domain: { id: 'orders', name: 'Orders', version: '0.0.1' },
      },
    ],
    // Example of just mapping schemas to events, commands and queries (without services or domains)
    [
      '@eventcatalog/generator-github',
      {
        // The url of your Confluent Schema Registry
        repo: 'event-catalog/eventcatalog',
        path: 'examples/default',
        messages: [
          {
            id: 'app.orders.created',
            version: '1.0.0',
            type: 'event',
            // The path in your github repository to the schema
            schemaPath: 'domains/Orders/services/InventoryService/events/InventoryAdjusted/schema.avro',
          },
          {
            id: 'app.orders.updated',
            version: '1.0.0',
            type: 'command',
            schemaPath: 'domains/Orders/services/InventoryService/events/InventoryAdjusted/schema.avro',
          },
          {
            id: 'app.orders.create',
            version: '1.0.0',
            type: 'query',
            schemaPath: 'domains/Orders/services/InventoryService/events/InventoryAdjusted/schema.avro',
          },
        ],
      },
    ]
  ],
...

In the example above we have two types of usecases for the generator:

• Map schemas from GitHub to Services (producers/consumers), if services or messages do not exist in EventCatalog they are created, the schema is always kept in sync.
• We don't map any schemas to services or domains, we just map schemas to events, commands and queries, we prefer to map things ourself in our EventCatalog.

Getting started

Installation and configuration

Make sure you are on the latest version of EventCatalog.

• Install the package

npm i @eventcatalog/generator-github

• Configure your eventcatalog.config.js file (see example)

• Set credentials for your GitHub. Create a .env file in the root of your project and add the following:

The machine you are running the generator on needs to have access to the GitHub repository.

# From eventcatalog.cloud (14 day free trial)
EVENTCATALOG_LICENSE_KEY_GITHUB=

• Run the generate command

npm run generate

• See your new domains, services and messages, run

npm run dev

Found a problem?

Raise a GitHub issue on this project, or contact us on our Discord server.

Commercial Use

This generator requires a license to be used with EventCatalog. You can get a 14 day free trial at https://eventcatalog.cloud or email us at [e-mail].