This document provides a comprehensive reference for all command-line arguments available in the Cloud-Query service.
cloud-query [flags]| Argument | Default Value | Description |
|---|---|---|
--database-enabled |
true |
Enable PostgreSQL-backed CloudQuery features (disables CloudQuery service when false) |
--database-host |
localhost |
Host of the PostgreSQL database |
--database-port |
5432 |
Port of the PostgreSQL database |
--database-user |
postgres |
Username for the PostgreSQL database |
--database-password |
postgres |
Password for the PostgreSQL database |
--database-name |
postgres |
Database name for the PostgreSQL database |
--connection-ttl |
3h |
Default TTL for connections in the pool, connections will be closed after this duration if not used |
--server-address |
:9192 |
Address on which the gRPC server will listen |
--server-tls-cert |
"" |
Path to the TLS certificate file for the gRPC server |
--server-tls-key |
"" |
Path to the TLS key file for the gRPC server |
--server-enable-reflection |
false |
Enable gRPC reflection for the server, useful for debugging and introspection |
-v |
Varies | Log level verbosity (0-5) |
Some defaults can be configured via environment variables:
| Variable | Description |
|---|---|
PLRL_DATABASE_ENABLED |
Overrides the default for --database-enabled |
PLRL_PG_PASSWORD |
Overrides the default for --database-password |
The Cloud-Query service uses klog for logging with the following verbosity levels:
| Level | Description |
|---|---|
| 0 | Critical errors and minimal operational information |
| 1 | Important operational events |
| 2 | Normal operational events |
| 3 | Detailed operational events |
| 4 | Debug information |
| 5 | Trace information |
cloud-query --database-host db.example.internal --database-port 5433cloud-query --server-tls-cert /path/to/cert.pem --server-tls-key /path/to/key.pemcloud-query --connection-ttl 30mcloud-query --database-enabled=falsecloud-query --server-enable-reflectioncloud-query -v=3When specifying file paths, such as for --server-tls-cert and --server-tls-key, you should ensure that:
- The files exist and are readable by the Cloud-Query process
- The Cloud-Query process has permission to read the files
- For production use, consider using absolute paths instead of relative paths