valitydev/bouncer
14
0
Fork 0
mirror of https://github.com/valitydev/bouncer.git synced 2024-11-06 02:15:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
19 Commits 25 Branches 0 Tags 328 KiB
Erlang 92.6%
Open Policy Agent 4.7%
Makefile 1.7%
Dockerfile 1%
4b86d8e48f
Go to file
Andrew Mayorov 4b86d8e48f
MSPF-641: Relax fsync-every-write audit log handler policy (#20) 
* Make fsync repeat interval configurable as usual.

* Dig into logger internals to sync w/ handler reliably

* Upgrade to opa 0.26.0-debug service image in tests

* Bump to rbkmoney/image-build-erlang@61a001b
2021-02-18 11:24:50 +03:00
build_utils@e1318727d4 Enforce unified formatting w/ erlfmt (#18) 2021-02-04 17:23:35 +03:00
config Add forgotten vm.args file (#6) 2020-10-30 16:14:01 +03:00
src MSPF-641: Relax fsync-every-write audit log handler policy (#20) 2021-02-18 11:24:50 +03:00
test MSPF-641: Relax fsync-every-write audit log handler policy (#20) 2021-02-18 11:24:50 +03:00
.gitignore MSPF-629: Add decisions (#12) 2020-12-31 17:26:12 +03:00
.gitmodules Implement a thrift service around opa policy solver (#1) 2020-10-14 12:09:26 +03:00
docker-compose.sh MSPF-641: Relax fsync-every-write audit log handler policy (#20) 2021-02-18 11:24:50 +03:00
Dockerfile.sh Implement a thrift service around opa policy solver (#1) 2020-10-14 12:09:26 +03:00
Jenkinsfile Cut fragments ctx out of audit logs (#19) 2021-02-08 11:12:39 +03:00
Makefile MSPF-641: Relax fsync-every-write audit log handler policy (#20) 2021-02-18 11:24:50 +03:00
README.md MSPF-641: Relax fsync-every-write audit log handler policy (#20) 2021-02-18 11:24:50 +03:00
rebar.config MSPF-641: Relax fsync-every-write audit log handler policy (#20) 2021-02-18 11:24:50 +03:00
rebar.lock MSPF-641: Relax fsync-every-write audit log handler policy (#20) 2021-02-18 11:24:50 +03:00

README.md

Bouncer

Does someone look like a troublemaker?

Primary Arbiter thrift service implementation.

In a nutshell this service maps incoming contexts into OPA input documents and asks OPA to compute a judgement allowing, restricting or forbidding actions under given input context.

From the service's point of view a ruleset id is a path to OPA document that define a subdocument named judgement with a rudimentary schema. See https://github.com/rbkmoney/bouncer-policies#authoring for more detailed information.

Things to keep in mind

  • When upgrading service to a newer Erlang OTP release please be aware of potential breakages in bouncer_audit_log not strictly related to usual API deprecations and removals which is an essintial part of a release. That is because this module relies on some OTP libraries' interal implementation details. See module-level notes for additional details.