@stackone/cli 1.14.1 → 1.15.1

package/README.md

@@ -91,6 +91,88 @@ stackone push --api-key <your-api-key> --api-url <api-url> path/to/connector.s1.
 - **File validation**: Checks that the file exists and is a valid connector before attempting upload
 - **Batch upload**: Supports uploading multiple connectors from a directory
 
+### `pull`
+
+Pull a connector from the StackOne API registry to your local filesystem. This command fetches a connector from the registry and saves it locally, with interactive conflict resolution when the connector already exists.
+
+```bash
+stackone pull --connector my-provider@1.0.0 --profile <profile-label>
+```
+
+or using direct credentials:
+
+```bash
+stackone pull --connector my-provider@1.0.0 --api-key <your-api-key>
+```
+
+or with custom API URL:
+
+```bash
+stackone pull --connector my-provider@1.0.0 --api-key <your-api-key> --api-url <api-url>
+```
+
+or pulling the latest version:
+
+```bash
+stackone pull --connector my-provider --profile <profile-label>
+```
+
+**Options:**
+
+- `--connector <connector>` - Connector identifier in format `provider_key@version` (e.g., `my-provider@1.0.0`) or just `provider_key` to pull the latest version
+- `-o, --output-path <output-path>` - Directory path to save the connector to (defaults to `./connectors/<provider_key>/`)
+- `-p, --profile <label>` - Configuration profile to use
+- `--api-key <api-key>` - API key to use for authentication (alternative to using a profile)
+- `--api-url <api-url>` - API URL to use (defaults to `https://api.stackone.com` if not specified)
+
+**Note:** You must provide either `--profile` or `--api-key`. If using `--api-key`, the `--api-url` option is optional and will default to the production API URL.
+
+**Usage Examples:**
+
+1. **Pull specific version with profile:**
+
+   ```bash
+   stackone pull --connector my-provider@1.0.0 --profile production
+   ```
+
+2. **Pull latest version with API key:**
+
+   ```bash
+   stackone pull --connector my-provider --api-key your-api-key
+   ```
+
+3. **Pull to custom directory:**
+
+   ```bash
+   stackone pull --connector my-provider@1.0.0 --profile production --output-path ./my-connectors
+   ```
+
+4. **Pull with custom API URL:**
+
+   ```bash
+   stackone pull --connector my-provider@1.0.0 --api-key your-api-key --api-url https://staging.api.stackone.com
+   ```
+
+**Conflict Resolution:**
+
+When pulling a connector that already exists locally, the command will:
+
+1. Display a diff showing the differences between local and registry versions
+2. Prompt you to choose how to resolve the conflict:
+   - **Override with registry version** - Replace local file with the registry version
+   - **Keep local version** - Discard changes and keep the local file
+   - **Interactive resolution** - Manually resolve conflicts line by line
+
+**Features:**
+
+- **Flexible authentication**: Use either a saved profile or provide credentials directly
+- **Version flexibility**: Pull specific versions or the latest version by omitting version number
+- **Interactive conflict resolution**: Smart diff-based conflict resolution when local changes exist
+- **Profile validation**: Ensures the specified profile exists before fetching (when using `--profile`)
+- **Automatic file organization**: Saves connectors in organized directory structure (`./connectors/<provider_key>/`)
+- **Local validation**: Validates local connector before conflict resolution
+- **Clear feedback**: Informative success and error messages with color-coded output
+
 ### `drop`
 
 Drop (delete) a specific connector version from the StackOne API registry. This command can use either a configuration profile created with the `init` command or provide credentials directly via command-line options.

package/dist/cli.cjs

@@ -1,2 +1,2 @@
 #!/usr/bin/env node
-const e=require(`./cliCore-CiHXnjR4.cjs`);new e.t().run();
+const e=require(`./cliCore-DOB5rM16.cjs`);new e.t().run();

package/dist/cli.mjs

@@ -1,2 +1,2 @@
 #!/usr/bin/env node
-import{t as e}from"./cliCore-RHF_Qqxe.mjs";new e().run();export{};
+import{t as e}from"./cliCore-BDikKAKf.mjs";new e().run();export{};