Automate Apicurio Registry [ ]
HumDay reads Apicurio Registry [ ]’s own published API description and derives 64 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Apicurio Registry [ ] is
Apicurio Registry is a datastore for standard event schemas and API designs. Apicurio Registry enables developers to manage and share the structure of their data using a REST interface. For example, client applications can dynamically push or pull the latest updates to or from the registry without needing to redeploy. Apicurio Registry also enables developers to create rules that govern how regist
API host: apicurio.local
What HumDay can do in Apicurio Registry [ ]
32 documented operations change something in Apicurio Registry [ ].
- POSTCreate a new group
/groups - POSTSearch for artifacts by content
/search/artifacts - POSTCreate artifact
/groups/{groupId}/artifacts - DELETEDelete a group by the specified ID.
/groups/{groupId} - DELETEDelete artifacts in group
/groups/{groupId}/artifacts - POSTCreate artifact rule
/groups/{groupId}/artifacts/{artifactId}/rules - POSTCreate artifact version
/groups/{groupId}/artifacts/{artifactId}/versions - DELETEDelete artifact
/groups/{groupId}/artifacts/{artifactId} - PUTUpdate artifact
/groups/{groupId}/artifacts/{artifactId} - POSTCreate a new role mapping
/admin/roleMappings - POSTGet artifact version metadata by content
/groups/{groupId}/artifacts/{artifactId}/meta - PUTUpdate artifact metadata
/groups/{groupId}/artifacts/{artifactId}/meta - PUTTest update artifact
/groups/{groupId}/artifacts/{artifactId}/test - PUTUpdate artifact owner
/groups/{groupId}/artifacts/{artifactId}/owner - DELETEDelete artifact rules
/groups/{groupId}/artifacts/{artifactId}/rules - PUTUpdate artifact state
/groups/{groupId}/artifacts/{artifactId}/state - POSTCreate global rule
/admin/rules - DELETEDelete artifact rule
/groups/{groupId}/artifacts/{artifactId}/rules/{rule} - PUTUpdate artifact rule configuration
/groups/{groupId}/artifacts/{artifactId}/rules/{rule} - DELETEDelete artifact version metadata
/groups/{groupId}/artifacts/{artifactId}/versions/{version}/meta - PUTUpdate artifact version metadata
/groups/{groupId}/artifacts/{artifactId}/versions/{version}/meta - PUTUpdate artifact version state
/groups/{groupId}/artifacts/{artifactId}/versions/{version}/state - DELETEDelete all global rules
/admin/rules - POSTImport registry data
/admin/import - DELETEDelete global rule
/admin/rules/{rule} - PUTUpdate global rule configuration
/admin/rules/{rule} - DELETERemoves logger configuration
/admin/loggers/{logger} - PUTSet a logger's configuration
/admin/loggers/{logger} - DELETEDelete a role mapping
/admin/roleMappings/{principalId} - PUTUpdate a role mapping
/admin/roleMappings/{principalId} - DELETEReset a configuration property
/admin/config/properties/{propertyName} - PUTUpdate a configuration property
/admin/config/properties/{propertyName}
What HumDay can read from Apicurio Registry [ ]
These are the operations a schedule or a trigger can watch.
- GETGet current user
/users/me - GETList groups
/groups - GETSearch for artifacts
/search/artifacts - GETList artifacts in group
/groups/{groupId}/artifacts - GETGet system information
/system/info - GETGet resource limits information
/system/limits - GETList artifact references by global ID
/ids/globalIds/{globalId}/references - GETGet a group by the specified ID.
/groups/{groupId} - GETList artifact references by content ID
/ids/contentIds/{contentId}/references - GETList artifact references by hash
/ids/contentHashes/{contentHash}/references - GETGet artifact by global ID
/ids/globalIds/{globalId} - GETGet artifact content by ID
/ids/contentIds/{contentId}/ - GETGet artifact content by SHA-256 hash
/ids/contentHashes/{contentHash}/ - GETList artifact rules
/groups/{groupId}/artifacts/{artifactId}/rules - GETList artifact versions
/groups/{groupId}/artifacts/{artifactId}/versions - GETGet latest artifact
/groups/{groupId}/artifacts/{artifactId} - GETGet artifact metadata
/groups/{groupId}/artifacts/{artifactId}/meta - GETGet artifact owner
/groups/{groupId}/artifacts/{artifactId}/owner - GETList global rules
/admin/rules - GETGet artifact rule configuration
/groups/{groupId}/artifacts/{artifactId}/rules/{rule} - GETList logging configurations
/admin/loggers - GETList all role mappings
/admin/roleMappings - GETGet artifact version
/groups/{groupId}/artifacts/{artifactId}/versions/{version} - GETList artifact types
/admin/artifactTypes - GETList all configuration properties
/admin/config/properties - GETGet artifact version metadata
/groups/{groupId}/artifacts/{artifactId}/versions/{version}/meta - GETGet artifact version
/groups/{groupId}/artifacts/{artifactId}/versions/{version}/references - GETExport registry data
/admin/export - GETGet global rule configuration
/admin/rules/{rule} - GETGet a single logger configuration
/admin/loggers/{logger} - GETReturn a single role mapping
/admin/roleMappings/{principalId} - GETGet configuration property value
/admin/config/properties/{propertyName}
How automating Apicurio Registry [ ] works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- 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.
- See it proven. The program runs and shows you the result before it is allowed near your live Apicurio Registry [ ] account.
- Grant access, then go live. You approve the specific Apicurio Registry [ ] operations it may use — and only those.
Automate Apicurio Registry [ ] with these
- OData for namespace microsoft.graph11412 operations
- GitHub811 operations
- Atlassian The Jira Cloud platform474 operations
- Gitlab358 operations
- JIRA 7.6.1324 operations
- Appcenter App Center Client323 operations
- Gitea .321 operations
- Bitbucket292 operations
- Keycloak Admin281 operations
- Apple App Store Connect251 operations
- Files.com222 operations
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about Apicurio Registry [ ] automation
- Can HumDay connect to Apicurio Registry [ ]?
- Yes. HumDay reads Apicurio Registry [ ]'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 64 operations are documented.
- Do I need to write code to automate Apicurio Registry [ ]?
- 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 Apicurio Registry [ ] account.
- What can HumDay do in Apicurio Registry [ ]?
- 32 of the 64 documented operations change something in Apicurio Registry [ ], and 32 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Apicurio Registry [ ] 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 Apicurio Registry [ ] is held behind that approval.
Where this came from
The operations above are read from a published API description for Apicurio Registry [ ] at raw.githubusercontent.com/Apicurio/apicurio-registry/master/app/src/main/resources-unfilte. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.