new feats

Author: trouze

CLAUDE.md

@@ -67,8 +67,9 @@ dbtp/
 │   │       └── dimension_values.rs
 │   └── core/                          # Shared infrastructure
 │       ├── mod.rs
-│       ├── config.rs                  # Profile loading/saving, env var fallback, config.toml
+│       ├── config.rs                  # Profile loading/saving, env var fallback, config.toml, interactive helpers
 │       ├── error.rs                   # DbtpError enum (Http, Config, GraphQL, Api, Io, Json, Arrow)
+│       ├── resolve.rs                 # Name-or-ID resolution for projects and environments
 │       ├── rest_client.rs             # REST client: v2/v3 URL routing, auth, pagination, envelope unwrapping
 │       └── graphql_client.rs          # GraphQL client for Discovery + Semantic Layer
 ├── openapi/                           # Reference OpenAPI specs (not used at build time)
@@ -89,6 +90,8 @@ dbtp/
 - **Auto-pagination**: `RestClient::paginate_v2` / `paginate_v3` loop through offset-based pages (100 per request) until `total_count` is reached or `--limit` is satisfied.
 - **Envelope unwrapping**: dbt Cloud REST APIs return `{ data, status, extra }`. The client strips this automatically via `unwrap_envelope()`.
 - **Compact mode**: A `compact` output format provides single-line JSON and uses `compact_*` helpers in `api/admin/mod.rs` to reduce verbose API responses to essential fields.
+- **Interactive configure**: `dbtp configure` detects whether stdin is a TTY. In interactive terminals, it fetches projects and environments via the API and offers a numbered selection menu. The `--non-interactive` flag or a non-TTY stdin falls through to plain ID prompts. API errors during interactive configure are handled gracefully with a fallback to manual entry.
+- **Name-or-ID resolution**: `project_id` and `environment_id` accept names or numeric IDs everywhere (config, env vars, CLI flags). `core/resolve.rs` tries `parse::<u64>()` first (zero API calls), then falls back to a list+filter API call with case-insensitive exact matching.
 
 ## Building and running
 
@@ -104,7 +107,9 @@ The release profile enables `strip = true`, `lto = true`, `codegen-units = 1` fo
 
 Config lives at `~/.config/dbtp/config.toml` (macOS) via the `directories` crate's `ProjectDirs::from("com", "dbt-labs", "dbtp")`.
 
-Precedence: CLI flags > env vars (`DBTP_TOKEN`, `DBTP_HOST`, `DBTP_ACCOUNT_ID`, `DBTP_ENVIRONMENT_ID`) > profile config > defaults.
+Precedence: CLI flags > env vars (`DBTP_TOKEN`, `DBTP_HOST`, `DBTP_ACCOUNT_ID`, `DBTP_PROJECT_ID`, `DBTP_ENVIRONMENT_ID`) > profile config > defaults.
+
+`project_id` and `environment_id` accept either a numeric ID or a name. Names are resolved to numeric IDs via a list+filter API call (case-insensitive exact match). Numeric IDs skip the API call entirely. Resolution happens in `main.rs` before command dispatch, so all downstream code receives numeric IDs.
 
 ## Key dependencies
 

README.md

@@ -3,8 +3,7 @@
 A fast, ergonomic command-line interface for the [dbt Cloud](https://www.getdbt.com/product/dbt-cloud) platform APIs. Manage accounts, projects, environments, jobs, and runs. Browse your dbt DAG through the Discovery API. Query metrics through the Semantic Layer. All from your terminal.
 
 ```
-dbtp jobs trigger 48213 --cause "deploy from CI"
-dbtp runs wait 901244 --interval 15
+dbtp jobs trigger 48213 --cause "deploy from CI" --wait
 dbtp models health orders
 dbtp metrics query revenue --group-by metric_time --grain MONTH
 ```
@@ -41,7 +40,7 @@ cargo install --path .
 dbtp configure
 ```
 
-You'll be prompted for your dbt Cloud host, API token, account ID, and (optionally) an environment ID for Discovery/Semantic Layer commands. Configuration is saved to `~/.config/dbtp/config.toml`.
+You'll be prompted for your dbt Cloud host, API token, account ID, and optionally a project and environment ID. When running in an interactive terminal, `configure` offers a numbered picker for projects and environments so you don't have to look up IDs. Use `--non-interactive` to disable the picker. Configuration is saved to `~/.config/dbtp/config.toml`.
 
 ### 2. Verify access
 
@@ -54,8 +53,11 @@ dbtp accounts list
 ```bash
 dbtp projects list
 dbtp jobs list --project-id 12345
+dbtp jobs list --project-id Analytics         # name resolution
+dbtp environments list                         # uses configured project
 dbtp runs show 901244 -o json
 dbtp models list --environment-id 67890
+dbtp models list --environment-id Production   # name resolution
 ```
 
 ## Configuration
@@ -73,12 +75,15 @@ output = "table"
 host = "https://cloud.getdbt.com"
 token = "dbtc_..."
 account_id = 51798
+project_id = "12345"           # numeric ID or project name
+environment_id = "67890"       # numeric ID or environment name
 
 [profile.staging]
 host = "https://emea.dbt.com"
 token = "dbtc_..."
 account_id = 99999
-environment_id = 67890
+project_id = "Analytics"       # resolved to numeric ID at runtime
+environment_id = "Production"
 ```
 
 ### Environment variables
@@ -88,7 +93,8 @@ environment_id = 67890
 | `DBTP_HOST` | dbt Cloud host URL |
 | `DBTP_TOKEN` | API token (service token or personal access token) |
 | `DBTP_ACCOUNT_ID` | Default account ID |
-| `DBTP_ENVIRONMENT_ID` | Default environment ID (Discovery / Semantic Layer) |
+| `DBTP_PROJECT_ID` | Default project ID or name |
+| `DBTP_ENVIRONMENT_ID` | Default environment ID or name (Discovery / Semantic Layer) |
 
 ### Precedence
 
@@ -170,8 +176,7 @@ dbtp jobs list -o compact | jq '.[].name'
 ### Trigger a job and wait for completion
 
 ```bash
-dbtp jobs trigger 48213 --cause "nightly refresh"
-dbtp runs wait 901244 --interval 10 --timeout 1800
+dbtp jobs trigger 48213 --cause "nightly refresh" --wait
 ```
 
 ### Inspect a failed run
@@ -233,10 +238,15 @@ dbtp artifacts get 901244 run_results.json
 | `--host <url>` | | dbt Cloud host URL |
 | `--token <token>` | | API token |
 | `--account-id <id>` | | dbt Cloud account ID |
-| `--environment-id <id>` | | Environment ID (Discovery / Semantic Layer) |
+| `--project-id <id-or-name>` | | Project ID or name |
+| `--environment-id <id-or-name>` | | Environment ID or name (Discovery / Semantic Layer) |
 | `--verbose` | `-v` | Enable verbose output |
 | `--query <jmespath>` | | JMESPath expression to filter JSON output |
 
+### Name resolution
+
+`--project-id` and `--environment-id` accept either a numeric ID or a project/environment **name**. When a name is given, the CLI resolves it to the numeric ID via a list API call with case-insensitive exact matching. Numeric IDs bypass the API call entirely (zero overhead). The same applies to `DBTP_PROJECT_ID`, `DBTP_ENVIRONMENT_ID`, and the config file values.
+
 ## Shell Completions
 
 Generate tab-completion scripts for your shell:
@@ -260,20 +270,8 @@ dbtp completion powershell > _dbtp.ps1
 - **API version routing** is handled automatically. The v2/v3 split in dbt Cloud's API is invisible to users — each command knows which version to use.
 - **Response envelope unwrapping** — dbt Cloud APIs return responses wrapped in `{ data, status, extra }`. The CLI strips the envelope and presents `data` directly.
 - **Auto-pagination** — `list` commands transparently paginate through all results. Use `--limit` to cap the total.
-- **Waiters** — `dbtp runs wait` polls until a run reaches a terminal state, printing status transitions as they happen.
-
-## Releasing
-
-Releases are automated via GitHub Actions. To cut a release:
-
-```bash
-# Update version in Cargo.toml, then:
-git commit -am "release: v0.1.0"
-git tag v0.1.0
-git push && git push --tags
-```
+- **Waiters** — `dbtp jobs trigger --wait` polls until a triggered run reaches a terminal state, printing status transitions as they happen.
 
-The [release workflow](.github/workflows/release.yml) builds binaries for macOS (arm64 + x86_64) and Linux (x86_64 + arm64), then creates a GitHub Release with all artifacts and checksums.
 
 ## License
 

src/api/admin/mod.rs

@@ -55,6 +55,63 @@ const RUNS_STRIP_FIELDS: &[&str] = &[
 
 const PROJECT_STRIP_FIELDS: &[&str] = &["freshness_job", "docs_job", "group_permissions"];
 
+pub const ACCOUNTS_TABLE_FIELDS: &[&str] = &[
+    "id",
+    "name",
+    "state",
+    "plan",
+    "developer_seats",
+    "run_slots",
+    "created_at",
+];
+
+pub const PROJECTS_TABLE_FIELDS: &[&str] = &[
+    "id",
+    "name",
+    "description",
+    "state",
+    "repository_id",
+    "connection_id",
+    "created_at",
+];
+
+pub const JOBS_TABLE_FIELDS: &[&str] = &[
+    "id",
+    "name",
+    "project_id",
+    "environment_id",
+    "job_type",
+    "state",
+    "dbt_version",
+];
+
+pub const RUNS_TABLE_FIELDS: &[&str] = &[
+    "id",
+    "job_id",
+    "project_id",
+    "status_humanized",
+    "duration",
+    "created_at",
+    "finished_at",
+];
+
+pub const ENVIRONMENTS_TABLE_FIELDS: &[&str] = &[
+    "id",
+    "name",
+    "type",
+    "state",
+    "project_id",
+    "dbt_version",
+    "created_at",
+];
+
+pub fn table_view(val: &Value, fields: &[&str]) -> Value {
+    match val {
+        Value::Array(arr) => Value::Array(arr.iter().map(|v| keep_fields(v, fields)).collect()),
+        other => keep_fields(other, fields),
+    }
+}
+
 pub fn compact_job(val: &Value) -> Value {
     keep_fields(val, JOBS_COMPACT_FIELDS)
 }

src/api/discovery/mod.rs

@@ -41,12 +41,14 @@ pub fn metadata_url(host: &str) -> String {
 }
 
 pub fn require_environment_id(config: &Config) -> Result<u64> {
-    config.environment_id.ok_or_else(|| {
-        DbtpError::config(
-            "environment_id is required for Discovery API; \
-             set via --environment-id, DBTP_ENVIRONMENT_ID, or `dbtp configure`",
-        )
-    })
+    config
+        .environment_id_u64()
+        .ok_or_else(|| {
+            DbtpError::config(
+                "environment_id is required for Discovery API; \
+                 set via --environment-id, DBTP_ENVIRONMENT_ID, or `dbtp configure`",
+            )
+        })
 }
 
 /// Extract nodes from paginated GraphQL edges: `[{node: ...}, ...]` -> `[...]`

src/cli/commands/accounts.rs

@@ -1,7 +1,7 @@
 use clap::{Args, Subcommand};
 use serde_json::Value;
 
-use crate::api::admin::accounts;
+use crate::api::admin::{self, accounts};
 use crate::core::config::Config;
 use crate::core::error::Result;
 use crate::core::rest_client::RestClient;
@@ -24,8 +24,17 @@ pub enum AccountsCommand {
 }
 
 pub async fn exec(args: &AccountsArgs, client: &RestClient, config: &Config) -> Result<Value> {
+    let is_table = config.output == "table" || config.output.is_empty();
+
     match &args.command {
-        AccountsCommand::List => accounts::list(&config.host, &config.token).await,
+        AccountsCommand::List => {
+            let val = accounts::list(&config.host, &config.token).await?;
+            Ok(if is_table {
+                admin::table_view(&val, admin::ACCOUNTS_TABLE_FIELDS)
+            } else {
+                val
+            })
+        }
         AccountsCommand::Show { account_id } => match account_id {
             Some(id) => accounts::get_by_id(&config.host, &config.token, *id).await,
             None => accounts::get(client).await,