Get Connection Profile

database_migration.get_connection_profile
ActionGoogle Cloudconnection required

Calls datamigration v1 GET /v1/projects/{projectsId}/locations/{locationsId}/connectionProfiles/{connectionProfilesId}.

Gets details of a single connection profile.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Database Migration
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location
Resolved by
config.connection_id, else node.connection_id

Configuration

2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
connection_profile
Connection profile name or id.
stringYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
alloydb
object—
cloudsql
object—
createTime
string—
displayName
string—
error
object—
labels
object—
mysql
object—
name
string—
oracle
object—
postgresql
object—
provider
string—
role
string—
satisfiesPzi
boolean—
satisfiesPzs
boolean—
sqlserver
object—
state
string—
updateTime
string—
{
  "alloydb": {},
  "cloudsql": {},
  "createTime": "",
  "displayName": "",
  "error": {},
  "labels": {},
  "mysql": {},
  "name": "",
  "oracle": {},
  "postgresql": {},
  "provider": "",
  "role": "",
  "satisfiesPzi": false,
  "satisfiesPzs": false,
  "sqlserver": {},
  "state": "",
  "updateTime": ""
}

See Get Connection Profile run in a workflow.

In a technical demo we add the Google Database Migration connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.