-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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.
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
Add --v1-compatible
flag to commands
#6463
Comments
Fixes: open-policy-agent#6463 Signed-off-by: Johan Fylling <johan.dev@fylling.se>
Fixes: open-policy-agent#6463 Signed-off-by: Johan Fylling <johan.dev@fylling.se>
Fixes: open-policy-agent#6463 Signed-off-by: Johan Fylling <johan.dev@fylling.se>
Fixes: open-policy-agent#6463 Signed-off-by: Johan Fylling <johan.dev@fylling.se>
Adding `--v1-compatible` flag to `opa test` Fixes: open-policy-agent#6463 Signed-off-by: Johan Fylling <johan.dev@fylling.se>
Fixes: open-policy-agent#6463 Signed-off-by: Johan Fylling <johan.dev@fylling.se>
Fixes: open-policy-agent#6463 Signed-off-by: Johan Fylling <johan.dev@fylling.se>
--rego-v1
flag to more commands--v1-compatible
flag to more commands
It has been decided that we should use the |
@johanfylling, I notice that this issue is closed but the PR (#6520) is still open. Do you know if this feature will make into opa soon. |
The scope of this issue was redefined to the PR #6521 implements #6520; which adds I hope this clarifies things. Thanks for making us aware of the issue 😃. |
--v1-compatible
flag to more commands--v1-compatible
flag to commands
When applied to commands other than
fmt
andcheck
, the--rego-v1
flag should enforce that all supplied modules are compatible with OPA v1.0, but not require therego.v1
orfuture.keywords
imports.Essentially, using the
--rego-v1
flag should make OPA parse, compile, and evaluate policies as if 1.0.E.g. this is a valid module in OPA 1.0:
Commands:
Commands supported at a later date (#6520):
The text was updated successfully, but these errors were encountered: