Can HumDay connect to Google Container Analysis?

Yes. HumDay reads Google Container Analysis's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 15 operations are documented.

Do I need to write code to automate Google Container Analysis?

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 Google Container Analysis account.

What can HumDay do in Google Container Analysis?

9 of the 15 documented operations change something in Google Container Analysis, and 6 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Container Analysis 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 Google Container Analysis is held behind that approval.

Automate Google Container Analysis

HumDay reads Google Container Analysis’s own published API description and derives 15 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 Google Container Analysis is

An implementation of the Grafeas API, which stores, and enables querying and retrieval of critical metadata about all of your software artifacts.

API host: containeranalysis.googleapis.com

What HumDay can do in Google Container Analysis

9 documented operations change something in Google Container Analysis.

POSTCreates a new note./v1beta1/{parent}/notes
POSTCreates a new occurrence./v1beta1/{parent}/occurrences
POSTCreates new notes in batch./v1beta1/{parent}/notes:batchCreate
POSTCreates new occurrences in batch./v1beta1/{parent}/occurrences:batchCreate
DELETEDeletes the specified occurrence./v1beta1/{name}
PATCHUpdates the specified occurrence./v1beta1/{name}
POSTGets the access control policy for a note or an occurrence resource./v1beta1/{resource}:getIamPolicy
POSTSets the access control policy on the specified note or occurrence./v1beta1/{resource}:setIamPolicy
POSTReturns the permissions that a caller has on the specified note or occurrence./v1beta1/{resource}:testIamPermissions

What HumDay can read from Google Container Analysis

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

GETGets the specified occurrence./v1beta1/{name}
GETGets the note attached to the specified occurrence./v1beta1/{name}/notes
GETLists notes for the specified project./v1beta1/{parent}/notes
GETLists occurrences referencing the specified note./v1beta1/{name}/occurrences
GETLists occurrences for the specified project./v1beta1/{parent}/occurrences
GETGets a summary of the number and severity of occurrences./v1beta1/{parent}/occurrences:vulnerabilitySummary

How automating Google Container Analysis 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 Google Container Analysis account.
Grant access, then go live. You approve the specific Google Container Analysis operations it may use — and only those.