You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This release pulls in [OPA v1.9.0](https://github.com/open-policy-agent/opa/releases/tag/v1.9.0) and the latest Regal release, [v0.36.1](https://github.com/open-policy-agent/regal/releases/tag/v0.36.1).
21
+
22
+
The Compile API extensions have been ported from EOPA to OPA, and are now feature in EOPA as a standard OPA feature.
23
+
Concretely, this means that the **headers** and **annotations** expected for Compile API usage need to follow the OPA requirements.
24
+
If you have used EOPA's Compile API extensions to generate data filters before, you need to replace:
25
+
26
+
1. Compile metadata no longer resides in "custom section"
27
+
28
+
Before:
29
+
30
+
```rego
31
+
package filters
32
+
33
+
# METADATA
34
+
# scope: document
35
+
# custom:
36
+
# unknowns:
37
+
# - input.fruits
38
+
# mask_rule: masks
39
+
```
40
+
41
+
After:
42
+
43
+
```rego
44
+
package filters
45
+
46
+
# METADATA
47
+
# scope: document
48
+
# compile: # <-------- replace custom with compile
49
+
# unknowns:
50
+
# - input.fruits
51
+
# mask_rule: masks
52
+
```
53
+
54
+
(If you have other `custom` annotations, those can stay in the "custom" section. Only the compile-related keys have been moved into their own section.)
55
+
56
+
2. Headers
57
+
58
+
The target and dialect selection was driven by Accept headers.
59
+
Previously, these used a prefix of "application/vnd.styra".
60
+
Now, they use "application/vnd.opa", e.g. "application/vnd.opa.postgresql+json".
0 commit comments