Automate Anchore Engine Server
HumDay reads Anchore Engine Server’s own published API description and derives 112 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 Anchore Engine Server is
This is the Anchore Engine API. Provides the primary external API for users of the service.
API host: anchore.local
What HumDay can do in Anchore Engine Server
44 documented operations change something in Anchore Engine Server. The 40 most useful are listed here.
- POSTCreate a new user
/accounts/{accountname}/users - POSTAdd a new policy
/policies - POSTAdd a new registry
/registries - POSTAdd a subscription of a specific type
/subscriptions - POSTadd/replace credential
/user/credentials - POSTAdds the capabilities to test a webhook delivery for the given notification type
/system/webhooks/{webhook_type}/test - DELETEDelete Event
/events/{eventId} - DELETEDelete Events
/events - POSTSubmit a new image for analysis by the engine
/images - POSTAdd repository to watch
/repositories - POSTImport an anchore image tar.gz archive file.
/import/images - POSTadd/replace credential
/accounts/{accountname}/users/{username}/credentials - DELETEDelete the specified account, only allowed if the account is in the disabled state.
/accounts/{accountname} - PUTUpdate an existing and specific subscription
/subscriptions/{subscriptionId} - DELETEBulk mark images for deletion
/images - DELETEDelete a specific user credential by username of the credential.
/accounts/{accountname}/users/{username} - PUTUpdate the state of an account to either enabled or disabled.
/accounts/{accountname}/state - POSTtrigger feeds operations
/system/feeds - POSTBegin the import of an image analyzed by Syft into the system
/imports/images - DELETEDelete a credential by type
/accounts/{accountname}/users/{username}/credentials - POSTCreate a new user. Only avaialble to admin user.
/accounts - DELETEDelete policy
/policies/{policyId} - PUTUpdate policy
/policies/{policyId} - DELETEDelete an image analysis
/images/{imageDigest} - DELETEDelete a registry configuration
/registries/{registry} - PUTUpdate/replace a registry configuration
/registries/{registry} - POSTImport a docker or OCI distribution manifest list to associate with the image
/imports/images/{operation_id}/parent_manifest - DELETEDelete subscriptions of a specific type
/subscriptions/{subscriptionId} - DELETEDelete the groups and data for the feed and disable the feed itself
/system/feeds/{feed} - PUTDisable the feed so that it does not sync on subsequent sync operations
/system/feeds/{feed} - DELETEDelete image by docker imageId
/images/by_id/{imageId} - DELETEPerforms a synchronous archive deletion
/archives/images/{imageDigest} - DELETEInvalidate operation ID so it can be garbage collected
/imports/images/{operation_id} - POSTImport a docker or OCI distribution manifest to associate with the image
/imports/images/{operation_id}/manifest - POSTBegin the import of an image analyzed by Syft into the system
/imports/images/{operation_id}/packages - POSTBegin the import of an image analyzed by Syft into the system
/imports/images/{operation_id}/dockerfile - POSTImport a docker or OCI image config to associate with the image
/imports/images/{operation_id}/image_config - DELETEDelete the group data and disable the group itself
/system/feeds/{feed}/{group} - PUTDisable a specific group within a feed to not sync
/system/feeds/{feed}/{group} - DELETEDelete the service config
/system/services/{servicename}/{hostid}
What HumDay can read from Anchore Engine Server
These are the operations a schedule or a trigger can watch.
- GETList Event Types
/event_types - GETList authenticated user info
/user - GETList Events
/events - GETList the account for the authenticated user
/account - GETList accounts for the user
/accounts/{accountname}/users - GETGet Event
/events/{eventId} - GETList of images containing given package
/query/images/by_package - GETList all visible images
/images - GETList policies
/policies - GETList images vulnerable to the specific vulnerability ID.
/query/images/by_vulnerability - GETList configured registries
/registries - GETList all subscriptions
/subscriptions - GETlist feeds operations and information
/system/feeds - GETList system services
/system/services - GETGet current credential summary
/user/credentials - GETList all visible image digests and tags
/summaries/imagetags - GETListing information about given vulnerability
/query/vulnerabilities - GETGet info about an user.
/accounts/{accountname} - GETSimple status check
/ - GETGet a specific subscription set
/subscriptions/{subscriptionId} - GETHealth check, returns 200 and no body if service is running
/health - GETService status
/status - GETSystem status
/system - GETReturns the version object for the service, including db schema version info
/version - GETGet a specific user in the specified account
/accounts/{accountname}/users/{username} - GETList image content types
/images/{imageDigest}/content - GETReturns the archive metadata record identifying the image and tags for the analysis in the archive.
/archives/images/{imageDigest} - GETList image metadata types
/images/{imageDigest}/metadata - GETLists in-progress imports
/imports/images - GETDescribe anchore engine error codes.
/system/error_codes - GETDescribe the policy language spec implemented by this service.
/system/policy_spec - GETGet current credential summary
/accounts/{accountname}/users/{username}/credentials - GETList image content types
/images/by_id/{imageId}/content - GETGet the content of an image by type files
/images/{imageDigest}/content/files - GETList uploaded image manifests
/imports/images/{operation_id}/manifest - GETList uploaded package manifests
/imports/images/{operation_id}/packages - GETGet specific policy
/policies/{policyId} - GETGet image metadata
/images/{imageDigest} - GETList uploaded dockerfiles
/imports/images/{operation_id}/dockerfile - GETGet a specific registry configuration
/registries/{registry} - GETList uploaded image configs
/imports/images/{operation_id}/image_config - GETReturn a list of analyzer artifacts of the specified type
/images/{imageDigest}/artifacts/secret_search - GETList uploaded parent manifests (manifest lists for a tag)
/imports/images/{operation_id}/parent_manifest - GETReturn a list of analyzer artifacts of the specified type
/images/{imageDigest}/artifacts/retrieved_files - GETReturn a list of analyzer artifacts of the specified type
/images/{imageDigest}/artifacts/file_content_search - GETGet the content of an image by type files
/images/by_id/{imageId}/content/files - GETLookup image by docker imageId
/images/by_id/{imageId} - GETGet vulnerability types
/images/{imageDigest}/vuln - GETCheck policy evaluation status for image
/images/{imageDigest}/check - GETGet detail on a single import
/imports/images/{operation_id} - GETGet a service configuration and state
/system/services/{servicename} - GETGet vulnerability types
/images/by_id/{imageId}/vuln - GETCheck policy evaluation status for image
/images/by_id/{imageId}/check - GETGet the content of an image by type java
/images/{imageDigest}/content/java - GETGet image sbom in the native Anchore format
/images/{imageDigest}/sboms/native - GETGet the content of an image by type malware
/images/{imageDigest}/content/malware - GETList user summaries. Only available to the system admin user.
/accounts - GETGet vulnerabilities by type
/images/{imageDigest}/vuln/{vtype} - GETGet the content of an image by type
/images/{imageDigest}/content/{ctype} - GETGet the metadata of an image by type
/images/{imageDigest}/metadata/{mtype}
How automating Anchore Engine Server 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 Anchore Engine Server account.
- Grant access, then go live. You approve the specific Anchore Engine Server operations it may use — and only those.
Popular Anchore Engine Server integrations
Connect Anchore Engine Server to the tools people pair it with most.
- Anchore Engine Server and OData for namespace microsoft.graphintegration
- Anchore Engine Server and Cloudflareintegration
- Anchore Engine Server and NetBoxintegration
- Anchore Engine Server and GitHubintegration
- Anchore Engine Server and Mistintegration
- Anchore Engine Server and Loket.nlintegration
- Anchore Engine Server and Atlassian The Jira Cloud platformintegration
- Anchore Engine Server and Magento B2Bintegration
- Anchore Engine Server and Stripeintegration
- Anchore Engine Server and Zuora Reference Billingintegration
- Anchore Engine Server and bunqintegration
- Anchore Engine Server and DocuSignintegration
Automate Anchore Engine Server 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 Anchore Engine Server automation
- Can HumDay connect to Anchore Engine Server?
- Yes. HumDay reads Anchore Engine Server's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 112 operations are documented.
- Do I need to write code to automate Anchore Engine Server?
- 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 Anchore Engine Server account.
- What can HumDay do in Anchore Engine Server?
- 44 of the 112 documented operations change something in Anchore Engine Server, and 68 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Anchore Engine Server 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 Anchore Engine Server is held behind that approval.
Where this came from
The operations above are read from a published API description for Anchore Engine Server at raw.githubusercontent.com/anchore/anchore-engine/master/anchore_engine/services/apiext/swa. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.