List Event Types in Anchore Engine Server

What this operation does

List Event Types

• GETReads data · Eventsanchore.local/event_types

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Anchore Engine Server operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other Anchore Engine Server operations

• Create a new userPOST · changes data
• Add a new policyPOST · changes data
• Add a new registryPOST · changes data
• Add a subscription of a specific typePOST · changes data
• Add/replace credentialPOST · changes data
• Adds the capabilities to test a webhook deliveryPOST · changes data
• Delete EventDELETE · changes data
• Delete EventsDELETE · changes data

All 112 Anchore Engine Server operations

Questions

Can HumDay list event types in Anchore Engine Server?

Yes. This operation is published in Anchore Engine Server's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Does this change anything in my Anchore Engine Server account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Anchore Engine Server.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Anchore Engine Server account.

Where this came from

Read from a published API description for Anchore Engine Server at raw.githubusercontent.com/anchore/anchore-engine/master/anchore_engine/services/apiext/swa. The description above is the provider’s own wording, not ours. Last published 2023-03-06.