diff --git a/skills/cdata-cli/SKILL.md b/skills/cdata-cli/SKILL.md index fc6c3a2..8ac3cbc 100644 --- a/skills/cdata-cli/SKILL.md +++ b/skills/cdata-cli/SKILL.md @@ -66,6 +66,10 @@ If `cdatacli --version` is missing, install: | Inspect connection properties | `drivers connectionprops [--full]` | | Generate driver-specific skill | `drivers skill ` | | Create connection | `connection create --driver --name N --connectionstring CS` | +| Update connection (merge) | `connection update --name N --connectionstring CS` | +| Update connection (replace) | `connection update --name N --connectionstring CS --replace` | +| Update, skip validation | `connection update --name N --connectionstring CS --force` | +| Remove properties | `connection update --name N --unset "Key1,Key2"` | | List connections | `connection list` | | Delete connection | `connection delete --name N` | | List catalogs | `metadata catalogs --connection N` | @@ -245,9 +249,14 @@ Common patterns: ```bash cdatacli connection list +cdatacli connection update --name "" --connectionstring "" +cdatacli connection update --name "" --connectionstring "" --replace +cdatacli connection update --name "" --unset "Key1,Key2" cdatacli connection delete --name "" ``` +`connection update` merges new properties into the existing connection by default — useful for changing a single property without recreating the connection. Use `--replace` to swap the entire connection string, or `--unset` to remove specific properties. Property names are case-insensitive. `--replace` and `--unset` cannot be combined. Use `--force` to skip connection validation — useful for placeholder connections or testing without a live source. + Connections are saved as encrypted `.conn` files (AES-256): | OS | Location | @@ -328,7 +337,7 @@ cdatacli query sql --connection --sql "UPDATE [TableName] SET [Col1] = 'n cdatacli query sql --connection --sql "DELETE FROM [TableName] WHERE [Id] = '123'" ``` -If writes fail, the connection may have `ReadOnly=true`. Do not change this on your own — point it out to the user and ask whether they want to recreate the connection without `ReadOnly=true` before taking any action. +If writes fail, the connection may have `ReadOnly=true`. Do not change this on your own — point it out to the user and ask whether they want to remove it. If they confirm, use `connection update --unset "ReadOnly"` rather than recreating the connection. #### Stored Procedures