mirror of
https://github.com/open-policy-agent/opa.git
synced 2026-08-12 19:32:48 -06:00
Shuvam Pal
bdd4646352
fixes #6391 <!-- Thanks for submitting a PR to OPA! Before pressing 'Create pull request' please read the checklist below. * All code changes should be accompanied with tests. If you are not modifying any tests, just provide a short explanation of why updates to tests are not necessary. In addition to helping catch bugs, tests are extremely helpful in providing _context_ that explains how your changes can be used. * All changes to public APIs **must** be accompanied with docs. Examples of public APIs include built-in functions, config fields, and of course, exported Go types/functions/constants/etc. * Commit messages should explain _why_ you made the changes, not what you changed. Use active voice. Keep the subject line under 50 characters or so. * All commits must be signed off by the author. If you are not familiar with signing off, see our contributor guide below. * You have read the project's [guidelines on AI tool use](https://www.openpolicyagent.org/docs/contrib-code#ai-guidelines). For more information on contributing to OPA see our [Contributing Guide](https://www.openpolicyagent.org/docs/contributing/) for high-level contributing guidelines and development setup. (See the [Developer Certificate of Origin](https://www.openpolicyagent.org/docs/contrib-code/#developer-certificate-of-origin) section for specifics on signing off a commit.) --> ### Why the changes in this PR are needed? 1. the rewritten var `__local0__` is output instead of s for rule p.r[s]. 2. no location is given for the conflicting refs data.play.p.q and data.play.p.r[`__local0__`]. ### What are the changes in this PR? Tracking rule location as well along with ref now. Also added formatting to keep the different conflicts multiline. Signed-off-by: unichronic <ishuvam.pal@gmail.com>
Open Policy Agent
Open Policy Agent (OPA) is an open source, general-purpose policy engine that enables unified, context-aware policy enforcement across the entire stack.
OPA is proud to be a graduated project in the Cloud Native Computing Foundation (CNCF) landscape. For details read the CNCF announcement.
Get started with OPA
- Write your first Rego policy with the Rego Playground or use it to share your work with others for feedback and support. Have a look at the Access Control examples if you're not sure where to start.
- Install the VS Code extension to get started locally with live diagnostics, debugging and formatting. See Editor and IDE Support for other supported editors.
- Go to the OPA Documentation to learn about the Rego language as well as how to deploy and integrate OPA.
- Check out the learning resources in the Learning Rego section of the ecosystem directory.
- Follow the Running OPA instructions to get started with the OPA CLI locally.
- See Docker Hub for container images and the GitHub releases for binaries.
- Check out the OPA Roadmap to see a high-level snapshot of OPA features in-progress and planned.
Want to talk about OPA or get support?
- Join the OPA Slack to talk to other OPA users and maintainers. See
#helpfor support. - Check out the Community Discussions to ask questions.
- See the Support page for commercial support options.
Interested to learn what others are doing with OPA?
- Browse community projects on the OPA Ecosystem Directory - don't forget to list your own!
- Check out the ADOPTERS.md file for a list of production adopters. Does your organization use OPA in production? Support the OPA project by submitting a PR to add your organization to the list with a short description of your OPA use cases!
Want to integrate OPA?
- See the high-level Go SDK or the low-level Go API
to integrate OPA with services written in Go.
- See the REST API reference to integrate OPA with services written in other languages.
- See the integration docs for more options.
Want to contribute to OPA?
- Read the Contributing Guide to learn how to make your first contribution.
- Use #contributors in Slack to talk to other contributors and OPA maintainers.
- File a GitHub Issue to request features or report bugs.
How does OPA work?
OPA gives you a high-level declarative language to author and enforce policies across your stack.
With OPA, you define rules that govern how your system should behave. These rules exist to answer questions like:
- Can user X call operation Y on resource Z?
- What clusters should workload W be deployed to?
- What tags must be set on resource R before it's created?
You integrate services with OPA so that these kinds of policy decisions do not have to be hardcoded in your service. Services integrate with OPA by executing queries when policy decisions are needed.
When you query OPA for a policy decision, OPA evaluates the rules and data (which you give it) to produce an answer. The policy decision is sent back as the result of the query.
For example, in a simple API authorization use case:
- You write rules that allow (or deny) access to your service APIs.
- Your service queries OPA when it receives API requests.
- OPA returns allow (or deny) decisions to your service.
- Your service enforces the decisions by accepting or rejecting requests accordingly.
For concrete examples of how to integrate OPA with systems like Kubernetes, Terraform, Docker, SSH, and more, see openpolicyagent.org.
Presentations
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon EU 2026: video
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon NA 2025: video
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon EU 2025: video
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon NA 2024: video
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon EU 2024: video
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon NA 2023: video
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon EU 2023: video
- Running Policy in Hard to Reach Places with WASM & OPA @ CN Wasm Day EU 2023: video
- OPA maintainers talk @ Kubecon NA 2022: video
- Open Policy Agent (OPA) Intro & Deep Dive @ Kubecon EU 2022: video
- Open Policy Agent Intro @ KubeCon EU 2021: Video
- Using Open Policy Agent to Meet Evolving Policy Requirements @ KubeCon NA 2020: video
- Applying Policy Throughout The Application Lifecycle with Open Policy Agent @ CloudNativeCon 2019: video
- Open Policy Agent Introduction @ CloudNativeCon EU 2018: video, slides
- Rego Deep Dive @ CloudNativeCon EU 2018: video, slides
- How Netflix Is Solving Authorization Across Their Cloud @ CloudNativeCon US 2017: video, slides.
- Policy-based Resource Placement in Kubernetes Federation @ LinuxCon Beijing 2017: slides, screencast
- Enforcing Bespoke Policies In Kubernetes @ KubeCon US 2017: video, slides
- Istio's Mixer: Policy Enforcement with Custom Adapters @ CloudNativeCon US 2017: video, slides
Security
A third party security audit was performed by Cure53, you can see the full report here.
Please report vulnerabilities by email to open-policy-agent-security. We will send a confirmation message to acknowledge that we have received the report and then we will send additional messages to follow up once the issue has been investigated.