Skip to main content

Deprecating data stores

Added in eventcatalog@2.59.0

Any resource in EventCatalog can be deprecated or marked as deprecated.

This will show a banner on the page indicating that the resource is deprecated.

Deprecating data stores using frontmatter​

To deprecate a data store you need to add the deprecated field to the data store frontmatter API.

This accepts a boolean or an object with the following properties:

  • date: Date the service will be or was deprecated (YYYY-MM-DD)
  • message: Reason the service is deprecated, supports markdown (optional)
/services/OrderService/containers/OrderDatabase/index.mdx (example)
---
id: OrderDatabase
... # other data store frontmatter

# deprecated as an object (Recommended)
deprecated:
  # Date the data store will be or was deprecated (YYYY-MM-DD)
  date: 2025-01-01
  # Reason the data store is deprecated, supports markdown (optional)
  message: | 
    This data store has been deprecated and replaced by the new data store **OrderDatabaseV2**.
    Please contact the [team for more information](mailto:inventory-team@example.com) or visit our [website](https://eventcatalog.dev).

# deprecated as a boolean 
deprecated: true
---

Configuration:

  • deprecated: boolean or object

Deprecated as an object is recommended, as it gives your users more information to why the resource is deprecated and a date in the past or future.

  • deprecated.date: Date the data store will be or was deprecated (YYYY-MM-DD)
  • deprecated.message: Reason the data store is deprecated, supports markdown (optional)

Rendered output​

Example of resource that will be deprecated:

Deprecating services

Example of resource that is deprecated:

Deprecating services

Demo​

You can see a demo of deprecating resources in the EventCatalog demo site.