Automate Google Cloud SQL Admin
HumDay reads Google Cloud SQL Admin’s own published API description and derives 53 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 Cloud SQL Admin is
API for Cloud SQL database instance management
API host: sqladmin.googleapis.com
What HumDay can do in Google Cloud SQL Admin
36 documented operations change something in Google Cloud SQL Admin.
- POSTCreates a new user in a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/users - POSTCreates a new Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances - DELETEDeletes a user from a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/users - PUTUpdates an existing user in a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/users - POSTCreates a new backup run on demand.
/sql/v1beta4/projects/{project}/instances/{instance}/backupRuns - POSTAdd a new trusted Certificate Authority (CA) version for the specified instance.
/sql/v1beta4/projects/{project}/instances/{instance}/addServerCa - POSTCreates a Cloud SQL instance as a clone of the source instance.
/sql/v1beta4/projects/{project}/instances/{instance}/clone - POSTExports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.
/sql/v1beta4/projects/{project}/instances/{instance}/export - POSTImports data into a Cloud SQL instance from a SQL dump or CSV file in Cloud Storage.
/sql/v1beta4/projects/{project}/instances/{instance}/import - POSTCreates an SSL certificate and returns it along with the private key and server certificate authority.
/sql/v1beta4/projects/{project}/instances/{instance}/sslCerts - POSTTruncate MySQL general and slow query log tables MySQL only.
/sql/v1beta4/projects/{project}/instances/{instance}/truncateLog - POSTDeletes all client certificates and generates a new server SSL certificate for the instance.
/sql/v1beta4/projects/{project}/instances/{instance}/resetSslConfig - DELETEDeletes a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance} - PATCHPartially updates settings of a Cloud SQL instance by merging the request with the current configuration.
/sql/v1beta4/projects/{project}/instances/{instance} - PUTUpdates settings of a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance} - POSTGenerates a short-lived X509 certificate containing the provided public key and signed by a private key specific to the target instance.
/sql/v1beta4/projects/{project}/instances/{instance}:generateEphemeralCert - POSTRestarts a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/restart - POSTInitiates a manual failover of a high availability (HA) primary instance to a standby instance, which becomes the primary instance.
/sql/v1beta4/projects/{project}/instances/{instance}/failover - POSTInserts a resource containing information about a database inside a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/databases - POSTStops the replication in the read replica instance.
/sql/v1beta4/projects/{project}/instances/{instance}/stopReplica - POSTDemotes the stand-alone instance to be a Cloud SQL read replica for an external database server.
/sql/v1beta4/projects/{project}/instances/{instance}/demoteMaster - POSTStarts the replication in the read replica instance.
/sql/v1beta4/projects/{project}/instances/{instance}/startReplica - POSTRestores a backup of a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/restoreBackup - POSTPromotes the read replica instance to be a stand-alone Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/promoteReplica - POSTRotates the server certificate to one signed by the Certificate Authority (CA) version previously added with the addServerCA method.
/sql/v1beta4/projects/{project}/instances/{instance}/rotateServerCa - POSTGenerates a short-lived X509 certificate containing the provided public key and signed by a private key specific to the target instance.
/sql/v1beta4/projects/{project}/instances/{instance}/createEphemeral - POSTReset Replica Size to primary instance disk size.
/sql/v1beta4/projects/{project}/instances/{instance}/resetReplicaSize - POSTPerform Disk Shrink on primary instance.
/sql/v1beta4/projects/{project}/instances/{instance}/performDiskShrink - POSTReschedules the maintenance on the given instance.
/sql/v1beta4/projects/{project}/instances/{instance}/rescheduleMaintenance - POSTVerify External primary instance external sync settings.
/sql/v1beta4/projects/{project}/instances/{instance}/verifyExternalSyncSettings - DELETEDeletes the backup taken by a backup run.
/sql/v1beta4/projects/{project}/instances/{instance}/backupRuns/{id} - DELETEDeletes a database from a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/databases/{database} - PATCHPartially updates a resource containing information about a database inside a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/databases/{database} - PUTUpdates a resource containing information about a database inside a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/databases/{database} - DELETEDeletes the SSL certificate.
/sql/v1beta4/projects/{project}/instances/{instance}/sslCerts/{sha1Fingerprint} - POSTStart External primary instance migration.
/sql/v1beta4/projects/{project}/instances/{instance}/startExternalSync
What HumDay can read from Google Cloud SQL Admin
These are the operations a schedule or a trigger can watch.
- GETLists all available database flags for Cloud SQL instances.
/sql/v1beta4/flags - GETLists all instance operations that have been performed on the given Cloud SQL instance in the reverse chronological order of the start time.
/sql/v1beta4/projects/{project}/operations - GETRetrieves a resource containing information about a user.
/sql/v1beta4/projects/{project}/instances/{instance}/users/{name} - GETLists all available machine types (tiers) for Cloud SQL, for example, db-custom-1-3840.
/sql/v1beta4/projects/{project}/tiers - GETLists instances under a given project.
/sql/v1beta4/projects/{project}/instances - GETLists users in the specified Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/users - GETLists all backup runs associated with the project or a given instance and configuration in the reverse chronological order of the backup initiation time.
/sql/v1beta4/projects/{project}/instances/{instance}/backupRuns - GETRetrieves a resource containing information about a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance} - GETRetrieves an instance operation that has been performed on an instance.
/sql/v1beta4/projects/{project}/operations/{operation} - GETLists all of the current SSL certificates for the instance.
/sql/v1beta4/projects/{project}/instances/{instance}/sslCerts - GETLists databases in the specified Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/databases - GETLists all of the trusted Certificate Authorities (CAs) for the specified instance.
/sql/v1beta4/projects/{project}/instances/{instance}/listServerCas - GETRetrieves connect settings about a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/connectSettings - GETGet Disk Shrink Config for a given instance.
/sql/v1beta4/projects/{project}/instances/{instance}/getDiskShrinkConfig - GETRetrieves a resource containing information about a backup run.
/sql/v1beta4/projects/{project}/instances/{instance}/backupRuns/{id} - GETRetrieves a resource containing information about a database inside a Cloud SQL instance.
/sql/v1beta4/projects/{project}/instances/{instance}/databases/{database} - GETRetrieves a particular SSL certificate.
/sql/v1beta4/projects/{project}/instances/{instance}/sslCerts/{sha1Fingerprint}
How automating Google Cloud SQL Admin 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 Cloud SQL Admin account.
- Grant access, then go live. You approve the specific Google Cloud SQL Admin operations it may use — and only those.
Automate Google Cloud SQL Admin with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Cloud SQL Admin automation
- Can HumDay connect to Google Cloud SQL Admin?
- Yes. HumDay reads Google Cloud SQL Admin's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 53 operations are documented.
- Do I need to write code to automate Google Cloud SQL Admin?
- 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 Cloud SQL Admin account.
- What can HumDay do in Google Cloud SQL Admin?
- 36 of the 53 documented operations change something in Google Cloud SQL Admin, and 17 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Cloud SQL Admin 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 Cloud SQL Admin is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Cloud SQL Admin at sqladmin.googleapis.com/$discovery/rest?version=v1beta4. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.