tclake-cli
Query TCLake metadata from the terminal via the tccatalog cloud API.
No third-party runtime dependencies; only the Python standard library is used.
Install
Outside a virtualenv, install into your user site:
python3 -m pip install --user tclake-cli
~/.local/bin must be on PATH (python3 -m site --user-base prints the prefix; the command is in its bin directory).
Inside a virtualenv, drop --user. pip refuses it there because the environment cannot see user site-packages:
python3 -m pip install tclake-cli
The tclake command is then on that environment's PATH only while the environment is active.
Quick start
tclake init
tclake lakehouse list
tclake lakehouse list sales
tclake lakehouse list sales.db1
tclake lakehouse describe sales.db1.orders
tclake volume list
tclake volume list volc.db1
tclake volume describe volc.db1.raw
tclake volume credentials volc.db1.raw
list shows the next level below the path, describe shows the path itself.
volume credentials prints the temporary keys in clear text by design.
JSON output
-o json (or --output json) prints the cloud API Response object. It can
sit before or after the subcommand. The table format stays the default.
tclake lakehouse list -o json
tclake lakehouse describe sales.db1.orders --output json
tclake --output json volume credentials volc.db1.raw
A catalog list looks like:
{
"RequestId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"CatalogNames": [
{"Namespace": [], "Name": "lance_catalog"}
]
}
Pipe it to jq:
tclake lakehouse list -o json | jq -r '.CatalogNames[].Name'
tclake lakehouse list sales.db1 -o json | jq -r '.TableNames[].Name'
tclake lakehouse describe sales.db1.orders -o json | jq '.Table.Columns[] | {Name, Type, Comment}'
tclake volume describe volc.db1.raw -o json | jq -r '.Volume.StorageLocation'
tclake volume credentials volc.db1.raw -o json | jq -r '.Credentials[0].CredentialInfo[] | select(.Key=="cos-access-key-id") | .Value'
Credentials
tclake init writes ~/.tclake/config (region, endpoint) and
~/.tclake/credentials (SecretId, SecretKey), both 0600.
Environment variables override files:
TENCENTCLOUD_SECRET_ID / TENCENTCLOUD_SECRET_KEY
TENCENTCLOUD_TOKEN (optional, temporary credentials)
TENCENTCLOUD_REGION / TENCENTCLOUD_ENDPOINT
Metadata
Release files for tclake-cli 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tclake_cli-0.0.2.tar.gz | 14.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tclake_cli-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.3 kB
Release files / tclake_cli-0.0.2.tar.gz
| Download URL | tclake_cli-0.0.2.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c29b39cc05179eacfdf3858fd6cb5160efe3ca32422f9b2b7a3424504f25302
|
|
BLAKE2b-256 checksum How to use checksums |
9a7e11a5d03347e290adec77fb33aebf5cf94e4629ea6b0333ba9faf3907963b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.20
|
Release files / tclake_cli-0.0.2-py3-none-any.whl
| Download URL | tclake_cli-0.0.2-py3-none-any.whl |
|---|---|
| Size | 15.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93b04e13489f279ec2179fcf48e33f082dfa40d046e3d733b55689be35dc986e
|
|
BLAKE2b-256 checksum How to use checksums |
645dc9385468d0d864f2581ac95fea91019c5134c252af1d20c7b3a4ca90fcde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.20
|
Security for tclake-cli 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.