Chore: This and that

Author: amotl

doc/backlog/main.md

@@ -1,9 +1,19 @@
 # Main Backlog
 
 ## Iteration +0
-- CLI: Consider simplifying by using `--url` instead of `--sqlalchemy-url` or `--http-url`
+- CLI: Consider simplifying the API by using canonical `--cluster-url` instead of `--sqlalchemy-url` vs. `--http-url`
 - CLI: Explore consolidating all four addressing options into a single `--cluster` option
-  for more intuitive cluster addressing. This could be implemented as an option alongside existing methods.
+  for more intuitive cluster addressing. This could be implemented as a separate option alongside
+  existing methods.
+- `cratedb_toolkit/cfr/cli.py`: Migrate to `ctx.meta["address"]`, like `cratedb_toolkit/info/cli.py`
+- Cluster API: Currently, software tests do not prune tables on CrateDB Cloud.
+  This will probably cause a disk spillover sooner or later on this instance.
+- When running the test suite, a huge log obstructs the output information.
+  ```
+  2025-05-03 22:48:22,191 [crate.client.http                   ] DEBUG   : JSON response for stmt(SELECT * FROM "sys"."allocations")
+  2025-05-03 22:48:22,768 [crate.client.http                   ] DEBUG   : JSON response for stmt(SELECT * FROM "sys"."jobs_log")
+  ```
+- Refactor `model.py`, `util/database.py`, and possibly more, to `ctk.model` module namespace
 
 ## Iteration +1
 - Table Loader: Refactor URL dispatcher, use fsspec
@@ -49,7 +59,7 @@
 - UX: Accept alias `--format {jsonl,ndjson}` for `--format json_row` 
 - Catch recursion errors:
   ```
-  CRATEDB_SQLALCHEMY_URL=crate://crate@localhost:4200/
+  CRATEDB_CLUSTER_URL=crate://crate@localhost:4200/
   ```
 - CLI: Verify exit codes.
 - UX: Rename `ctk cluster info` to `ctk status cluster --id=foo-bar-baz`

doc/cluster/backlog.md

@@ -12,19 +12,21 @@ a patch for some item, it will be very much welcome.
 [issues]: https://github.com/crate/cratedb-toolkit/issues
 
 ## Iteration +1
-- `ctk cluster info` does not include information about CrateDB yet.
-  => Connect to ex-WTF utilities.
-- Less verbosity by default for `ctk cluster` operations.
+- CLI: Less verbosity by default for `ctk cluster` operations
   Possibly display cluster operation and job execution outcomes, and `last_async_operation` details
-- Python API: Make `cluster.query` use the excellent `records` package
-- `ctk cluster list`: New
+- CLI: Implement `ctk cluster list`, `ctk cluster delete`
+- Shell: Make prompt display the cluster name
+- Managed: Use `keyring` for caching the JWT token, and compensate token expiry
 
 ## Iteration +2
+- Python API: Make `cluster.query` use the excellent `records` package
 - Xon.sh example
 - Windows support. Powershell?
 - Validate multi-cluster, multi-org operations work well and make sense
 - Implement JWT token expiry handling
 - Add Apache Spark / Databricks to the client bundle?
+- Use universal `DatabaseCluster` across the board. For that to happen, it will
+  need to gain an `DatabaseCluster.from_env()` entry point.
 
 ## Iteration +3
 - Complete UI: `ctk cluster health`
@@ -87,3 +89,11 @@ a patch for some item, it will be very much welcome.
   using different credentials for connecting to individual clusters.
 - Document `ManagedCluster`'s `stop_on_exit` option
 - `toolkit/cluster/cli.py`: Also respect cluster ID and name across the board of ex-WTF utilities.
+- `ctk cluster info` does not include information about CrateDB yet.
+  => Connect to ex-WTF utilities.
+- Make CLI options override ENV vars. Otherwise, using `--sqlalchemy-url=crate://`
+  will never work if an `.env` file is present.
+- SDK: Rename `ctk.cluster` to `ctk.sdk`? => No.
+- CLI: Shrink address URLs to single parameter `--cluster-url`
+- Changelog: Notify about breaking change with input address parameter names
+- Docs: Update guidelines about input address parameter preferences