gcp-datastream-connection-profile-tls-client-key-input
Database TLS configuration can carry PEM client private keys in connection-profile create and update requests.
Where it sits
| location | datastream.projects.locations.connectionProfiles.create/datastream.projects.locations.connectionProfiles.patch.request.{mysqlProfile.sslConfig.clientKey,postgresqlProfile.sslConfig.serverAndClientVerification.clientKey,mongodbProfile.sslConfig.clientKey} |
|---|---|
| location kind | secret_value |
| data kinds | private_key database_credential credential |
| emits edge | ContainsCredential |
| service | Datastream / Data Fusion (gcp:datastream) |
Collection recipe
| access mode | write_only_input |
|---|---|
| operation | datastream.projects.locations.connectionProfiles.create/datastream.projects.locations.connectionProfiles.patch |
| response path | request.{mysqlProfile.sslConfig.clientKey,postgresqlProfile.sslConfig.serverAndClientVerification.clientKey,mongodbProfile.sslConfig.clientKey} |
| encoding | json |
| params | {"name": "\u003cresource-name\u003e"} |
Required permissions
datastream.connectionProfiles.create datastream.connectionProfiles.update