Linux cesa-www-main 6.1.0-49-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.174-1 (2026-05-26) x86_64
Apache/2.4.68 (Debian)
Server IP : 10.218.0.2 & Your IP : 216.73.216.28
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
lib /
google-cloud-sdk /
platform /
bq /
utils /
Delete
Unzip
Name
Size
Permission
Date
Action
__pycache__
[ DIR ]
drwxr-xr-x
2026-06-08 18:08
bq_api_utils.py
9.67
KB
-rw-r--r--
1980-01-01 08:00
bq_consts.py
775
B
-rw-r--r--
1980-01-01 08:00
bq_error.py
6.18
KB
-rw-r--r--
1980-01-01 08:00
bq_error_utils.py
9.71
KB
-rw-r--r--
1980-01-01 08:00
bq_gcloud_utils.py
6.83
KB
-rw-r--r--
1980-01-01 08:00
bq_id_utils.py
14.68
KB
-rw-r--r--
1980-01-01 08:00
bq_logging.py
4.54
KB
-rw-r--r--
1980-01-01 08:00
bq_processor_utils.py
14.19
KB
-rw-r--r--
1980-01-01 08:00
Save
Rename
#!/usr/bin/env python """Constants for the BQ CLI.""" import enum from typing import Literal class Service(enum.Enum): """Enum for the different BigQuery APIs supported.""" ANALYTICS_HUB = 1 BIGLAKE = 2 BIGQUERY = 3 CONNECTIONS = 4 RESERVATIONS = 5 DTS = 6 # This is the BQ core discovery doc with some IAM additions. See cl/600781292 # for exactly what is added. There is some context in b/296612193 but IAM # needs to be a separate enum option until Dataset IAM is launched # (b/284146366). BQ_IAM = 7 FormatType = Literal['json', 'prettyjson', 'csv', 'sparse', 'pretty'] CustomPrintFormat = Literal[ # Commands 'list', 'make', 'show', # Resources 'materialized_view', 'schema', 'table_replica', 'view', ]