[Extend Governor APIs] Extensions and ERD schemas

[bailinhe]

Currently Governor API supports addons by allowing standalone applications to listen to various governor events and perform additional tasks accordingly. This approach, while being simple yet powerful and flexible, limits the capabilities of the addons. Namely, addons that provide configurability for the end users, require communications between the users and the addons through the Governor API.

This [Extend Governor APIs] series PRs aim to provide an alternative way, in addition to the existing addons, to improve the Governor API's extendibility, by implementing a solution that allows the API itself to be extended, in a design that is heavily influenced by Kubernetes' CRD and operator patten.

Data schema created:

• Extensions
• Extension Resource Definitions

erDiagram
  extension {
    uuid id
    string url
    string name
    string slug
    string description
    bool enabled
    enum status "offline, online"
  }

  extension_resource_definition {
    uuid id
    string name
    string slug_singular
    string slug_plural
    enum scope "system or user"

    bool enabled
    string version
    jsonb schema "JSON schema"
  }

  user_extension_resource {
    uuid id
    jsonb resource
  }

  system_extension_resource {
    uuid id
    jsonb resource
  }

  extension ||--o{ extension_resource_definition: has

  user ||--o{ user_extension_resource: has
  extension_resource_definition ||--o{ user_extension_resource: validates

  extension_resource_definition ||--o{ system_extension_resource: validates

Loading

[fishnix]

couple minor comments 👍