Skip to main content

Datometry Documentation

Policies Configuration Parameters

The [policies] section defines rules for connection routing. Incoming connections are routed to a specific pool based on policy matching. A policy matches incoming connections on the target database, user, IP and protocol. Policies are order dependent.

Note

Due to the origins of Hyper-Q using PostgreSQL clients, which provide a database name when connecting, the database name is part of the information on which policies match. For Teradata clients, which do not send a database name (not to be confused with Teradata database = schema on most target systems), the database name is configured in the [endpoint] section

"policy".protocol = all
"policy".database = all
"policy".user = all
"policy".ip = "0.0.0.0"
"policy".ip_prefix = 0
"policy".pool = "pool"
"policy".auth_method = passthru
Table 8. Policy Parameters

Parameter

Type

Description

ip

Integer

IP address of the Teradata client.

ip_prefix

Integer

Specifies the whole of IP addresses for Teradata clients. It is used to match policies with pools.

protocol

String

Specifies that the protocol attached to a policy. It is used to match policies with pools. Values can can be all or tls.

database

String

Same as one of the [endpoint] databases in order to connect the client from the specific endpoint to this policy.

user

String

Specifies the database user endpoint to attach to this policy. It can also accept a list of users. For example:

"policy1".user = ["user", "user2", "user3"]

user_regex

String

Specifies user using a regular expression. For example:

"policy1".user_regex = ["^user1.*", "^user2.*"]

auth_method

String

Specifies the authentication method for the policy. It currently accepts the value passthru.