The connection resource allows exposing internal services from your internal infra structure to users.
The definition of this resource represent how clients will be able to interact with internal resources.
Each type/subtype may represent a distinct implementation:
application/<subtype> - An alias to map distinct types of shell applications (e.g.: python, ruby, etc)
application/tcp - Forward TCP connections
This type requires the following environment variables:
HOST: ip or dns of the internal servicePORT: the port of the internal servicecustom - Any custom shell application
database/<subtype> - Allow connecting to databases through multiple clients (Webapp, cli, IDE’s)
Each <subtype> has distinct environment variables that are allowed to be configured, refer to our documentation for more information.
Tags are key/value pairs that are attached to objects such as Connections. Tags are intended to be used to specify identifying attributes of objects that are meaningful and relevant to users, but do not directly imply semantics to the core system.
{
"connection_tags": {
"environment": "production",
"component": "backend"
}
}
Equality- or inequality-based requirements allow filtering by tags keys and values. Matching objects must satisfy all of the specified tag constraints, though they may have additional tags as well. Three kinds of operators are admitted =,!=. The first represent equality, while the last represents inequality. For example:
environment = production
tier != frontend
The former selects all resources with key equal to environment and value equal to production. The latter selects all resources with key equal to tier and value distinct from frontend. One could filter for resources in production excluding frontend using the comma operator: environment=production,tier!=frontend
The request body resource
Toggle Port Forwarding
enabled, disabled Toggle Ad Hoc Executions
enabled, disabled Toggle Ad Hoc Runbooks Executions
enabled, disabled Toggle Introspection Schema
enabled, disabled The agent associated with this connection
"1837453e-01fc-46f3-9e4c-dcf22d395393"
Name of the connection. This attribute is immutable when updating it
"pgdemo"
Type represents the main type of the connection:
database, application, custom "database"
Is the shell command that is going to be executed when interacting with this connection. This value is required if the connection is going to be used from the Webapp.
["/bin/bash"]Tags to identify the connection
{ "environment": "prod", "tier": "frontend" }Default databases returns the configured value of the attribute secrets->'DB'
The guard rail association id rules
[
"5701046A-7B7A-4A78-ABB0-A24C95E6FE54",
"B19BBA55-8646-4D94-A40A-C3AFE2F4BAFD"
]The jira issue templates ids associated to the connection
"B19BBA55-8646-4D94-A40A-C3AFE2F4BAFD"
When this option is enabled it will allow managing the redact types through the attribute redact_types
Redact Types is a list of info types that will used to redact the output of the connection. Possible values are described in the DLP documentation: https://cloud.google.com/sensitive-data-protection/docs/infotypes-reference
["EMAIL_ADDRESS"]Resource to which this connection belongs to, it'll be created if it doesn't exist
"pgdemo"
Reviewers is a list of groups that will review the connection before the user could execute it
["dba-group"]Secrets are environment variables that are going to be exposed in the runtime of the connection:
The value could also represent an integration with a external provider:
Sub Type is the underline implementation of the connection:
"postgres"
DEPRECATED: Tags to classify the connection
["prod"]Created
Toggle Port Forwarding
enabled, disabled Toggle Ad Hoc Executions
enabled, disabled Toggle Ad Hoc Runbooks Executions
enabled, disabled Toggle Introspection Schema
enabled, disabled The agent associated with this connection
"1837453e-01fc-46f3-9e4c-dcf22d395393"
Name of the connection. This attribute is immutable when updating it
"pgdemo"
Type represents the main type of the connection:
database, application, custom "database"
Is the shell command that is going to be executed when interacting with this connection. This value is required if the connection is going to be used from the Webapp.
["/bin/bash"]Tags to identify the connection
{ "environment": "prod", "tier": "frontend" }Default databases returns the configured value of the attribute secrets->'DB'
The guard rail association id rules
[
"5701046A-7B7A-4A78-ABB0-A24C95E6FE54",
"B19BBA55-8646-4D94-A40A-C3AFE2F4BAFD"
]Unique ID of the resource
"5364ec99-653b-41ba-8165-67236e894990"
The jira issue templates ids associated to the connection
"B19BBA55-8646-4D94-A40A-C3AFE2F4BAFD"
Managed By is a read only field that indicates who is managing this resource. When this attribute is set, this resource is considered immutable
""
When this option is enabled it will allow managing the redact types through the attribute redact_types
Redact Types is a list of info types that will used to redact the output of the connection. Possible values are described in the DLP documentation: https://cloud.google.com/sensitive-data-protection/docs/infotypes-reference
["EMAIL_ADDRESS"]Resource to which this connection belongs to, it'll be created if it doesn't exist
"pgdemo"
Reviewers is a list of groups that will review the connection before the user could execute it
["dba-group"]Secrets are environment variables that are going to be exposed in the runtime of the connection:
The value could also represent an integration with a external provider:
Status is a read only field that informs if the connection is available for interaction
online, offline Sub Type is the underline implementation of the connection:
"postgres"
DEPRECATED: Tags to classify the connection
["prod"]