Can HumDay connect to Google VM Migration?

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

Do I need to write code to automate Google VM Migration?

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 VM Migration account.

What can HumDay do in Google VM Migration?

18 of the 31 documented operations change something in Google VM Migration, and 13 read from it. HumDay only ever uses the specific operations your approved contract needs.

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

Automate Google VM Migration

HumDay reads Google VM Migration’s own published API description and derives 31 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 VM Migration is

Use the Migrate to Virtual Machines API to programmatically migrate workloads.

API host: vmmigration.googleapis.com

What HumDay can do in Google VM Migration

18 documented operations change something in Google VM Migration.

POSTCreates a new Group in a given project and location./v1alpha1/{parent}/groups
POSTCreates a new Source in a given project and location./v1alpha1/{parent}/sources
POSTCreates a new MigratingVm in a given Source./v1alpha1/{parent}/migratingVms
POSTCreates a new TargetProject in a given project./v1alpha1/{parent}/targetProjects
POSTCreates a new UtilizationReport./v1alpha1/{parent}/utilizationReports
POSTCreates a new DatacenterConnector in a given Source./v1alpha1/{parent}/datacenterConnectors
POSTAdds a MigratingVm to a Group./v1alpha1/{group}:addGroupMigration
DELETEDeletes a single TargetProject./v1alpha1/{name}
PATCHUpdates the parameters of a single TargetProject./v1alpha1/{name}
POSTInitiates the cancellation of a running cutover job./v1alpha1/{name}:cancel
POSTRemoves a MigratingVm from a Group./v1alpha1/{group}:removeGroupMigration
POSTUpgrades the appliance relate to this DatacenterConnector to the in-place updateable version./v1alpha1/{datacenterConnector}:upgradeAppliance
POSTInitiates a Clone of a specific migrating VM./v1alpha1/{parent}/cloneJobs
POSTInitiates a Cutover of a specific migrating VM./v1alpha1/{parent}/cutoverJobs
POSTPauses a migration for a VM./v1alpha1/{migratingVm}:pauseMigration
POSTStarts migration for a VM./v1alpha1/{migratingVm}:startMigration
POSTResumes a migration for a VM./v1alpha1/{migratingVm}:resumeMigration
POSTMarks a migration as completed, deleting migration resources that are no longer being used./v1alpha1/{migratingVm}:finalizeMigration

What HumDay can read from Google VM Migration

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

GETList remote source's inventory of VMs./v1alpha1/{source}:fetchInventory
GETGets details of a single TargetProject./v1alpha1/{name}
GETLists Groups in a given project and location./v1alpha1/{parent}/groups
GETLists information about the supported locations for this service./v1alpha1/{name}/locations
GETLists Sources in a given project and location./v1alpha1/{parent}/sources
GETLists operations that match the specified filter in the request./v1alpha1/{name}/operations
GETLists CloneJobs of a given migrating VM./v1alpha1/{parent}/cloneJobs
GETLists CutoverJobs of a given migrating VM./v1alpha1/{parent}/cutoverJobs
GETLists MigratingVms in a given Source./v1alpha1/{parent}/migratingVms
GETLists TargetProjects in a given project./v1alpha1/{parent}/targetProjects
GETLists ReplicationCycles in a given MigratingVM./v1alpha1/{parent}/replicationCycles
GETLists Utilization Reports of the given Source./v1alpha1/{parent}/utilizationReports
GETLists DatacenterConnectors in a given Source./v1alpha1/{parent}/datacenterConnectors

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