Can HumDay connect to Google Artifact Registry?

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

Do I need to write code to automate Google Artifact 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 Google Artifact Registry account.

What can HumDay do in Google Artifact Registry?

10 of the 18 documented operations change something in Google Artifact Registry, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google Artifact Registry

HumDay reads Google Artifact Registry’s own published API description and derives 18 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 Artifact Registry is

Store and manage build artifacts in a scalable and integrated service built on Google infrastructure.

API host: artifactregistry.googleapis.com

What HumDay can do in Google Artifact Registry

10 documented operations change something in Google Artifact Registry.

POSTTests if the caller has a list of permissions on a resource./v1beta2/{resource}:testIamPermissions
POSTCreates a tag./v1beta2/{parent}/tags
POSTCreates a repository. The returned Operation will finish once the repository has been created. Its response will be the created Repository./v1beta2/{parent}/repositories
POSTDirectly uploads an Apt artifact./v1beta2/{parent}/aptArtifacts:create
POSTDirectly uploads a Yum artifact./v1beta2/{parent}/yumArtifacts:create
DELETEDeletes a version and all of its content./v1beta2/{name}
PATCHUpdates a tag./v1beta2/{name}
POSTImports Apt artifacts./v1beta2/{parent}/aptArtifacts:import
POSTImports Yum (RPM) artifacts./v1beta2/{parent}/yumArtifacts:import
POSTUpdates the IAM policy for a given resource./v1beta2/{resource}:setIamPolicy

What HumDay can read from Google Artifact Registry

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

GETLists files./v1beta2/{parent}/files
GETGets a version/v1beta2/{name}
GETLists tags./v1beta2/{parent}/tags
GETLists information about the supported locations for this service./v1beta2/{name}/locations
GETLists packages./v1beta2/{parent}/packages
GETLists versions./v1beta2/{parent}/versions
GETLists repositories./v1beta2/{parent}/repositories
GETGets the IAM policy for a given resource./v1beta2/{resource}:getIamPolicy

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