8000 docs(configure_external_data_sources.mdx): policies can now also come from an API server by emily-zall · Pull Request #577 · permitio/opal · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

docs(configure_external_data_sources.mdx): policies can now also come from an API server #577

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 27, 2024
Merged

docs(configure_external_data_sources.mdx): policies can now also come from an API server #577

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/docs/tutorials/configure_external_data_sources.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ OPAL clients have two **distinct** types of data sources:

| Data Source Type | Format of data | Function | Source of data 645A |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Policies (and static data)** | **Policy bundle** - data format is very similar to OPA native bundles. | Each bundle contains the policies (rego) and static data that is usually included as part of the policy. By "static", we mean the data rarely changes, same as declaring the data _inside_ the rego file. | Git repository (we are thinking about expanding this to more sources in the near future). |
| **Policies (and static data)** | **Policy bundle** - data format is very similar to OPA native bundles. | Each bundle contains the policies (rego) and static data that is usually included as part of the policy. By "static", we mean the data rarely changes, same as declaring the data _inside_ the rego file. | Default source is Git repository. Alternate source is an API server that exposes tar bundles. |
| **Dynamic Data** | **DataSourceEntry** - think about it as a "directive" how to fetch the data and where to put it in OPA document tree - i will give an example below. | Realtime updates about data that changes in the rate of the application (i.e: as a result of user action), for example - we invited a user to a document in google drive. If we implement this internally as the user now having a `Viewer` role on the document, we can send a data update containing the new role, with instructions to put it inside the roles document in OPA cache. | Can be anything - a database, a 3rd party API, your APIs, etc - extensible by fetch providers. We support http apis out of the box. |

### Q: What are `OPAL_DATA_CONFIG_SOURCES`?
Expand Down
Loading
0