Reverse Dependencies of opal-common

The following projects have a declared dependency on opal-common:

• dynamodb-fetch-provider — Custom Fetch Provider for DynamoDB
• opal-client — OPAL is an administration layer for Open Policy Agent (OPA), detecting changes to both policy and data and pushing live updates to your agents. The opal-client is deployed alongside a policy-store (e.g: OPA), keeping it up-to-date, by connecting to an opal-server and subscribing to pub/sub updates for policy and policy data changes.
• opal-fetcher-cosmos — An OPAL fetch provider to bring authorization state from CosmosDB.
• opal-fetcher-mongodb — An OPAL fetch provider to bring authorization state from MongoDB.
• opal-fetcher-mongodb-treedom — An OPAL fetch provider to bring authorization state from MongoDB.
• opal-fetcher-mysql — An OPAL fetch provider to bring authorization state from MySQL DB.
• opal-fetcher-postgres — An OPAL fetch provider to bring authorization state from Postgres DB.
• opal-fetcher-test-dynamodb — A short description of your package
• opal-server — OPAL is an administration layer for Open Policy Agent (OPA), detecting changes to both policy and data and pushing live updates to your agents. The opal-server creates a pub/sub channel clients can subscribe to (i.e: acts as coordinator). The server also tracks a git repository (via webhook) for updates to policy (or static data) and accepts continuous data update notifications via REST api, which are then pushed to clients.
• opal-trino-fetcher — An OPAL fetch provider to bring authorization state from Trino.