Automate Openpolicy Open Policy Agent (OPA)

What Openpolicy Open Policy Agent (OPA) is

OPA provides policy-based control for cloud native environments. The following *endpoints* (such as `PUT /v1/policies`) provide reference documentation for the OPA REST API. ### API specification viewing options - **[View the specification in *Redoc* (default)](index.html)** - **[View the specification in *Swagger UI*](swagger-ui.html)**

API host: openpolicy.local

What HumDay can do in Openpolicy Open Policy Agent (OPA)

10 documented operations change something in Openpolicy Open Policy Agent (OPA).

• POSTExecute a simple query/
• POSTGet a document (with webhook)/v0/data/{path}
• PUTCreate or overwrite a document/v1/data/{path}
• POSTExecute an ad-hoc query (complex)/v1/query
• DELETEDelete a document/v1/data/{path}
• PATCHUpdate a document/v1/data/{path}
• POSTGet a document (with input)/v1/data/{path}
• PUTCreate or update a policy module/v1/policies/{id}
• POSTCompile/v1/compile
• DELETEDelete a policy module/v1/policies/{id}

What HumDay can read from Openpolicy Open Policy Agent (OPA)

These are the operations a schedule or a trigger can watch.

• GETExecute an ad-hoc query (simple)/v1/query
• GETList policies/v1/policies
• GETHealth/health
• GETGet a document/v1/data/{path}
• GETGet configurations/v1/config
• GETGet a policy module/v1/policies/{id}

How automating Openpolicy Open Policy Agent (OPA) works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Openpolicy Open Policy Agent (OPA) account.
4. Grant access, then go live. You approve the specific Openpolicy Open Policy Agent (OPA) operations it may use — and only those.

Automate Openpolicy Open Policy Agent (OPA) with these

• Monarchinitiative BioLink164 operations
• UniCourt Enterprise158 operations
• OSF APIv2 Documentation156 operations
• IllumiDesk143 operations
• Figshare136 operations
• MCW Rat Genome Database100 operations
• U.S. EPA Enforcement and Compliance History Online (ECHO) Detailed Facility Report (DFR)94 operations
• OpenFEC91 operations
• NBA Stats83 operations
• Thebluealliance The Blue Alliance65 operations
• eDRV57 operations
• Collegefootballdata College Football Data51 operations

Categories

• Open data

Questions about Openpolicy Open Policy Agent (OPA) automation

Can HumDay connect to Openpolicy Open Policy Agent (OPA)?

Yes. HumDay reads Openpolicy Open Policy Agent (OPA)'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 16 operations are documented.

Do I need to write code to automate Openpolicy Open Policy Agent (OPA)?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Openpolicy Open Policy Agent (OPA) account.

What can HumDay do in Openpolicy Open Policy Agent (OPA)?

10 of the 16 documented operations change something in Openpolicy Open Policy Agent (OPA), and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Openpolicy Open Policy Agent (OPA) account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Openpolicy Open Policy Agent (OPA) is held behind that approval.

Where this came from

The operations above are read from a published API description for Openpolicy Open Policy Agent (OPA) at raw.githubusercontent.com/open-policy-agent/contrib/master/open_api/openapi.yaml. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.