Skip to content

Remove excess line from Model.md #18

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
hsluoyz merged 1 commit into from
May 29, 2017
Merged

Remove excess line from Model.md #18

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
4 changes: 2 additions & 2 deletions Model.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
* [How to add a customized function](#how-to-add-a-customized-function)
- [Role definition (optional)](#role-definition--optional-)
- [Role definition with domains/tenants (optional)](#role-definition-with-domains-tenants--optional-)

A model CONF should have at least four sections: ``[request_definition], [policy_definition], [policy_effect], [matchers]``. If the model uses RBAC, it should also add ``[role_definition]``. The comments start with ``#``.

## Request definition
Expand Down Expand Up @@ -56,7 +56,7 @@ For common cases, the user doesn't have multiple policy definitions, so probably
[policy_effect]
e = some(where (p.eft == allow))
```
e = !any(where (p.eft == deny))

The above policy effect means if there's any matched policy rule of ``allow``, the final effect is ``allow`` (aka allow-override). ``p.eft`` is the effect for a policy, it can be ``allow`` or ``deny``. It's optional and the default value is ``allow``. So as we didn't specify it above, it uses the default value.

Another example for policy effect is:
Expand Down