Skip to content
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

Update philosophy.md #4412

Merged
merged 2 commits into from
Mar 5, 2022
Merged

Update philosophy.md #4412

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
52a8e79
Update philosophy.md
ajonesiii Mar 5, 2022
0bb7acd
Merge branch 'main' into philosophy-document-update
srenatus Mar 5, 2022
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
6 changes: 3 additions & 3 deletions docs/content/philosophy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ surfaced in virtual documents. Data loaded synchronously is kept outside of `dat
avoid naming conflicts.

The following table summarizes the different models for loading base documents into OPA,
how they can referenced inside of policies, and the actual mechanism(s) for loading.
how they can be referenced inside of policies, and the actual mechanism(s) for loading.

| Model | How to access in Rego | How to integrate with OPA |
| --- | --- | --- |
Expand Down Expand Up @@ -170,7 +170,7 @@ virtual documents named `data.iam.user_has_role` and `data.acme.user_is_assigned
{{< figure src="data-model.svg" width="65" caption="Hypothetical Policy Document Model" >}}

> [1] OPA has excellent support for loading JSON and YAML because they are prevalent
> in modern systems however OPA is not tied to any particular data format. OPA
> in modern systems; however, OPA is not tied to any particular data format. OPA
> uses its own internal representation for structures like maps and lists (a.k.a.,
> objects and arrays in JSON.)

Expand All @@ -181,5 +181,5 @@ virtual documents named `data.iam.user_has_role` and `data.acme.user_is_assigned
> nested, hierarchical data structures containing several levels of embedded
> maps and lists.

> [3] Internally HTTP requests like `GET /v1/data` or `GET /v1/data/foo/bar` are turned
> [3] Internally, HTTP requests like `GET /v1/data` or `GET /v1/data/foo/bar` are turned
> into Rego queries that are almost identical to the HTTP path (e.g., `data` or `data.foo.bar`)