xsoar-cli 1.0.5__py3-none-any.whl → 1.0.6__py3-none-any.whl

xsoar_cli/__about__.py

@@ -1,4 +1,4 @@
 # SPDX-FileCopyrightText: 2025-present Torbjørn Lium <torben@lium.org>
 #
 # SPDX-License-Identifier: MIT
-__version__ = "1.0.5"
+__version__ = "1.0.6"

xsoar_cli/case/README.md

@@ -1,31 +1,57 @@
 # Case
 
-**Various case/incident related commands**
+Various case/incident related commands for XSOAR.
 
-## Clone
-It may be useful to clone a case from the production environment to the dev environment. This will of course require a configuration file
-with API keys for both environments. The syntax is `xsoar-cli case clone --dest TEXT --source TEXT CASENUMBER` where default environments for `dest` and `source` are "dev" and "prod", respectively.
+## Get
+
+Retrieve basic information about a single case. Returns raw JSON formatted with 4-space indentation.
+
+**Syntax:** `xsoar-cli case get [OPTIONS] CASENUMBER`
+
+**Options:**
+- `--environment TEXT` - Target environment (default: uses default environment from config)
 
-#### Example invocation
+**Examples:**
 ```
-xsoar-cli case clone --dest prod --source dev 312412  # explicitly using the default options
-xsoar-cli case clone 312412                           # shorthand for the same invocation as above
+xsoar-cli case get 312412
+xsoar-cli case get --environment prod 312412
 ```
 
+## Clone
+
+Clone a case from one environment to another. Useful for copying production cases to development environment for testing.
 
-## Create
-It may be useful to create a case in the dev environment. The syntax is `xsoar-cli case create [OPTIONS] [NAME] [DETAILS]` where NAME and
-DETAILS are optional. If NAME and DETAILS are not filled in, then default values are used.
-#### Example invocation
+**Syntax:** `xsoar-cli case clone [OPTIONS] CASENUMBER`
+
+**Options:**
+- `--source TEXT` - Source environment (default: prod)
+- `--dest TEXT` - Destination environment (default: dev)
+
+**Examples:**
 ```
-xsoar-cli case create 312412
-xsoar-cli case create 312412 "This is the name/title of the case" "This is some descriptive text on what the case is about."
+xsoar-cli case clone 312412                           # Clone from prod to dev (defaults)
+xsoar-cli case clone --source dev --dest prod 312412  # Clone from dev to prod
 ```
 
+## Create
 
-## Get
-It may be useful to quickly fetch some case data. The syntax is `xsoar-cli case clone [OPTIONS] CASENUMBER` and the command outputs raw JSON indented with 4 whitespaces to make the resulting output at least somewhat readable.
-#### Example invocation
+Create a new case in XSOAR with optional custom fields and case type.
+
+**Syntax:** `xsoar-cli case create [OPTIONS] [NAME] [DETAILS]`
+
+**Options:**
+- `--environment TEXT` - Target environment (default: uses default environment from config)
+- `--casetype TEXT` - Case type (default: uses default case type from config)
+- `--custom-fields TEXT` - Additional fields in format "field1=value1,field2=value2" (useful when XSOAR has mandatory custom case fields configured)
+- `--custom-fields-delimiter TEXT` - Delimiter for custom fields (default: ",")
+
+**Arguments:**
+- `NAME` - Case title (default: "Test case created from xsoar-cli")
+- `DETAILS` - Case description (default: "Placeholder case details")
+
+**Examples:**
 ```
-xsoar-cli case get 312412
+xsoar-cli case create
+xsoar-cli case create "Security Incident" "Suspicious network activity detected"
+xsoar-cli case create --casetype "Phishing" --custom-fields "severity=High,source=Email" "Phishing Email" "Suspicious email received"
 ```

xsoar_cli/case/commands.py

@@ -33,15 +33,31 @@ def get(ctx: click.Context, casenumber: int, environment: str | None) -> None:
 @click.argument("casenumber", type=int)
 @click.option("--source", default="prod", show_default=True, help="Source environment")
 @click.option("--dest", default="dev", show_default=True, help="Destination environment")
+@click.option(
+    "--custom-fields",
+    default=None,
+    help='Additional fields on the form "myfield=my_value,anotherfield=another value". Use machine name for field names, e.g mycustomfieldname.',
+)
+@click.option("--custom-fields-delimiter", default=",", help='Delimiter when specifying additional fields. Default is ","')
 @click.command()
 @click.pass_context
 @load_config
-def clone(ctx: click.Context, casenumber: int, source: str, dest: str) -> None:
+def clone(  # noqa: PLR0913
+    ctx: click.Context,
+    casenumber: int,
+    source: str,
+    dest: str,
+    custom_fields: str | None,
+    custom_fields_delimiter: str,
+) -> None:
     """Clones a case from source to destination environment."""
     valid_envs = validate_environments(source, dest, ctx=ctx)
     if not valid_envs:
         click.echo(f"Error: cannot find environments {source} and/or {dest} in config")
         ctx.exit(1)
+    if custom_fields and "=" not in custom_fields:
+        click.echo('Malformed custom fields. Must be on the form "myfield=myvalue"')
+        ctx.exit(1)
     xsoar_source_client: Client = ctx.obj["server_envs"][source]["xsoar_client"]
     results = xsoar_source_client.get_case(casenumber)
     data = results["data"][0]
@@ -58,6 +74,8 @@ def clone(ctx: click.Context, casenumber: int, source: str, dest: str) -> None:
     data.pop("modified")
     # Ensure that playbooks run immediately when the case is created
     data["createInvestigation"] = True
+    if "CustomFields" in data:
+        data["CustomFields"] = data["CustomFields"] | parse_string_to_dict(custom_fields, custom_fields_delimiter)
 
     xsoar_dest_client: Client = ctx.obj["server_envs"][dest]["xsoar_client"]
     case_data = xsoar_dest_client.create_case(data=data)
@@ -83,10 +101,13 @@ def create(  # noqa: PLR0913
     casetype: str,
     name: str,
     custom_fields: str | None,
-    custom_fields_delimiter: str | None,
+    custom_fields_delimiter: str,
     details: str,
 ) -> None:
     """Creates a new case in XSOAR. If invalid case type is specified as a command option, XSOAR will default to using Unclassified."""
+    if custom_fields and "=" not in custom_fields:
+        click.echo('Malformed custom fields. Must be on the form "myfield=myvalue"')
+        ctx.exit(1)
     if not environment:
         environment = ctx.obj["default_environment"]
     xsoar_client: Client = ctx.obj["server_envs"][environment]["xsoar_client"]

xsoar_cli/config/README.md

@@ -1,12 +1,64 @@
 # Config
-At the moment, only a single config command is implemented
+
+Configuration management commands for XSOAR CLI.
 
 ## Create
-Creates a new configuration file in `~/.config/xsoar-cli/config.json` based on a template. If the file already exists, then the user is prompted to overwrite
-the existing file.
 
-## Get
-Reads the current configuration file and prints it out as JSON indented with 4 whitespaces. API keys are masked from output.
+Create a new configuration file based on a template. If the configuration file already exists, prompts for confirmation to overwrite.
+
+**Syntax:** `xsoar-cli config create`
+
+**Examples:**
+```
+xsoar-cli config create
+```
+
+## Show
+
+Display the current configuration file contents as formatted JSON. API keys are masked by default for security.
+
+**Syntax:** `xsoar-cli config show [OPTIONS]`
+
+**Options:**
+- `--unmask` - Show unmasked API keys in output
+
+**Examples:**
+```
+xsoar-cli config show
+xsoar-cli config show --unmask
+```
 
 ## Validate
-Ensures that the configuration file is valid parsable JSON and that each server environment defined is reachable.
+
+Validate that the configuration file is properly formatted JSON and test connectivity to each XSOAR environment defined in the configuration.
+
+**Syntax:** `xsoar-cli config validate [OPTIONS]`
+
+**Options:**
+- `--only-test-environment TEXT` - Test connectivity for only the specified environment
+
+**Examples:**
+```
+xsoar-cli config validate
+xsoar-cli config validate --only-test-environment prod
+```
+
+## Set Credentials
+
+Update API credentials for a specific environment in the configuration file. Automatically sets server version based on whether a key ID is provided.
+
+**Syntax:** `xsoar-cli config set-credentials [OPTIONS] APITOKEN`
+
+**Options:**
+- `--environment TEXT` - Target environment (default: dev)
+- `--key_id INTEGER` - API key ID for XSOAR 8 (sets server_version to 8, omit for XSOAR 6)
+
+**Arguments:**
+- `APITOKEN` - The API token to set for the environment
+
+**Examples:**
+```
+xsoar-cli config set-credentials your-api-token-here
+xsoar-cli config set-credentials --environment prod your-api-token-here
+xsoar-cli config set-credentials --environment prod --key_id 123 your-api-token-here
+```

xsoar_cli/manifest/README.md

@@ -1,269 +1,122 @@
-# Manifest Commands
+# Manifest
 
-The manifest commands help you manage XSOAR content pack deployments using a declarative configuration file (`xsoar_config.json`). This file defines which content packs should be installed on your XSOAR server and their specific versions.
+Content pack deployment management commands using a declarative configuration file (`xsoar_config.json`).
 
-## Prerequisites
+## Generate
 
-- Valid XSOAR CLI configuration file (`~/.config/xsoar-cli/config.json`)
-- Access to XSOAR server API
-- For custom packs: AWS S3 credentials configured (AWS S3 is currently the only supported artifacts repository provider)
-- Content repository with proper directory structure
+Generate a new manifest file from currently installed content packs. Assumes all packs are marketplace packs (no custom packs).
 
-## Manifest File Structure
+**Syntax:** `xsoar-cli manifest generate [OPTIONS] MANIFEST_PATH`
 
-The `xsoar_config.json` file contains two main sections:
+**Options:**
+- `--environment TEXT` - Target environment (default: uses default environment from config)
 
-```json
-{
-    "custom_packs": [
-        {
-            "id": "MyCustomPack",
-            "version": "1.0.0",
-            "_comment": "Optional comment for documentation"
-        }
-    ],
-    "marketplace_packs": [
-        {
-            "id": "CommonScripts", 
-            "version": "1.20.0"
-        }
-    ]
-}
-```
+**Arguments:**
+- `MANIFEST_PATH` - Path where the new manifest file will be created
 
-- **custom_packs**: Content packs developed by your organization, stored in AWS S3 (currently the only supported artifacts repository provider; pull requests for new providers are welcome!)
-- **marketplace_packs**: Official Palo Alto Networks content packs from the marketplace
-- **_comment**: Optional field for documentation/notes about specific pack versions
+**Examples:**
+```
+xsoar-cli manifest generate ./xsoar_config.json
+xsoar-cli manifest generate --environment prod ./xsoar_config.json
+```
 
-## Commands
+## Validate
 
-### validate
-Validates the manifest file and verifies all specified content packs are available.
+Validate manifest JSON syntax and verify all specified content packs are available. Tests connectivity to pack sources and checks local pack metadata for development packs.
 
-**Usage:**
-```bash
-xsoar-cli manifest validate [OPTIONS] MANIFEST_PATH
-```
+**Syntax:** `xsoar-cli manifest validate [OPTIONS] MANIFEST_PATH`
 
 **Options:**
-- `--environment TEXT`: Environment name from config file (default: dev)
+- `--environment TEXT` - Target environment (default: uses default environment from config)
+
+**Arguments:**
+- `MANIFEST_PATH` - Path to the manifest file to validate
 
 **Examples:**
-```bash
-# Validate manifest in current directory
+```
 xsoar-cli manifest validate ./xsoar_config.json
-
-# Validate with specific environment
-xsoar-cli manifest validate --environment prod ./xsoar_config.json
+xsoar-cli manifest validate --environment staging ./xsoar_config.json
 ```
 
-**What it checks:**
-- JSON syntax validity
-- Custom pack availability in S3 artifact repository
-- Marketplace pack availability via HTTP connectivity
-- Local pack metadata consistency for new packs in development
-
-**Sample output:**
-```
-Manifest is valid JSON
-Checking custom_packs availability ........................done.
-Checking marketplace_packs availability ........................done.
-Manifest is valid JSON and all packs are reachable.
-```
+## Update
 
-### update
-Compares installed packs against available versions and updates the manifest with latest versions.
+Compare installed packs against available versions and update the manifest file with latest versions. Prompts for confirmation on each upgrade.
 
-**Usage:**
-```bash
-xsoar-cli manifest update [OPTIONS] MANIFEST_PATH
-```
+**Syntax:** `xsoar-cli manifest update [OPTIONS] MANIFEST_PATH`
 
 **Options:**
-- `--environment TEXT`: Environment name from config file (default: dev)
+- `--environment TEXT` - Target environment (default: uses default environment from config)
+
+**Arguments:**
+- `MANIFEST_PATH` - Path to the manifest file to update
 
 **Examples:**
-```bash
-# Update manifest with latest versions
+```
 xsoar-cli manifest update ./xsoar_config.json
-
-# Interactive prompts for each pack upgrade
-xsoar-cli manifest update --environment staging ./xsoar_config.json
+xsoar-cli manifest update --environment dev ./xsoar_config.json
 ```
 
-**Behavior:**
-- Queries XSOAR server for outdated packs
-- Displays upgrade candidates in tabular format
-- Prompts for confirmation on each upgrade
-- Preserves `_comment` fields but shows warnings
-- Updates manifest file on disk
+## Diff
 
-**Sample output:**
-```
-Fetching outdated packs from XSOAR server. This may take a minute...done.
-Pack ID                                           Installed version   Latest available version
-CommonScripts                                     1.19.0              1.20.0              
-Base                                              1.40.14             1.41.14             
-Total number of outdated content packs: 2
-Upgrade CommonScripts from 1.19.0 to 1.20.0? [Y/n]: y
-Upgrade Base from 1.40.14 to 1.41.14? [Y/n]: y
-Written updated manifest to './xsoar_config.json'
-```
+Compare the manifest definition against what is actually installed on the XSOAR server. Shows packs that are missing or have version mismatches.
 
-### diff
-Compares the manifest definition against what's actually installed on the XSOAR server.
-
-**Usage:**
-```bash
-xsoar-cli manifest diff [OPTIONS] MANIFEST_PATH
-```
+**Syntax:** `xsoar-cli manifest diff [OPTIONS] MANIFEST_PATH`
 
 **Options:**
-- `--environment TEXT`: Environment name from config file (default: dev)
+- `--environment TEXT` - Target environment (default: uses default environment from config)
+
+**Arguments:**
+- `MANIFEST_PATH` - Path to the manifest file to compare
 
 **Examples:**
-```bash
-# Show differences between manifest and server
+```
 xsoar-cli manifest diff ./xsoar_config.json
-
-# Check production environment
 xsoar-cli manifest diff --environment prod ./xsoar_config.json
 ```
 
-**Output shows:**
-- Packs defined in manifest but not installed
-- Version mismatches between manifest and installed packs
-- Summary message when everything is up to date
-
-**Sample output:**
-```
-Pack MyCustomPack is not installed
-Manifest states CommonScripts version 1.20.0 but version 1.19.0 is installed
-```
+## Deploy
 
-### deploy
-Installs or updates content packs on the XSOAR server according to the manifest.
+Install or update content packs on the XSOAR server according to the manifest. Only deploys packs that differ from current installation.
 
-**Usage:**
-```bash
-xsoar-cli manifest deploy [OPTIONS] MANIFEST_PATH
-```
+**Syntax:** `xsoar-cli manifest deploy [OPTIONS] MANIFEST_PATH`
 
 **Options:**
-- `--environment TEXT`: Environment name from config file (default: dev)
-- `--verbose`: Show detailed information about skipped packs
-- `--yes`: Skip confirmation prompt
+- `--environment TEXT` - Target environment (default: uses default environment from config)
+- `--verbose` - Show detailed information about skipped packs
+- `--yes` - Skip confirmation prompt
+
+**Arguments:**
+- `MANIFEST_PATH` - Path to the manifest file to deploy
 
 **Examples:**
-```bash
-# Deploy with confirmation prompt
+```
 xsoar-cli manifest deploy ./xsoar_config.json
-
-# Deploy to production without prompts
 xsoar-cli manifest deploy --environment prod --yes ./xsoar_config.json
-
-# Deploy with verbose output
 xsoar-cli manifest deploy --verbose ./xsoar_config.json
 ```
 
-**Behavior:**
-- Prompts for confirmation before deployment (unless --yes used)
-- Only installs/updates packs that differ from current installation
-- Shows progress for each pack installation
-- Skips packs already at correct version
-
-**Sample output:**
-```
-WARNING: this operation will attempt to deploy all packs defined in the manifest to XSOAR dev environment. Continue? [y/N]: y
-Fetching installed packs...done.
-Installing MyCustomPack version 1.0.0...OK.
-Installing CommonScripts version 1.20.0...OK.
-Not installing Base version 1.41.14. Already installed.
-```
-
-## Common Workflows
-
-### Initial Setup
-1. Create manifest: `xsoar-cli manifest validate ./xsoar_config.json` (validates structure)
-2. Deploy: `xsoar-cli manifest deploy ./xsoar_config.json`
-
-### Regular Updates
-1. Check for updates: `xsoar-cli manifest update ./xsoar_config.json`
-2. Review changes in manifest file
-3. Deploy updates: `xsoar-cli manifest deploy ./xsoar_config.json`
+## Manifest File Structure
 
-### Environment Consistency
-1. Check differences: `xsoar-cli manifest diff --environment prod ./xsoar_config.json`
-2. Deploy if needed: `xsoar-cli manifest deploy --environment prod ./xsoar_config.json`
+The `xsoar_config.json` file defines content packs to be installed:
 
-### CI/CD Pipeline Integration
-```bash
-# Typical CI/CD workflow
-xsoar-cli manifest validate ./xsoar_config.json    # Fail fast on invalid manifest
-xsoar-cli manifest diff --environment dev ./xsoar_config.json  # Show what will change
-xsoar-cli manifest deploy --yes --environment dev ./xsoar_config.json  # Deploy changes
+```json
+{
+    "custom_packs": [
+        {
+            "id": "MyCustomPack",
+            "version": "1.0.0",
+            "_comment": "Optional documentation comment"
+        }
+    ],
+    "marketplace_packs": [
+        {
+            "id": "CommonScripts",
+            "version": "1.20.0"
+        }
+    ]
+}
 ```
 
-## Troubleshooting
-
-### Common Issues
-
-**"Failed to decode JSON in {filepath}"**
-- Check JSON syntax in manifest file
-- Ensure no trailing commas or missing quotes
-- Use a JSON validator to identify syntax errors
-
-**"Failed to reach pack {pack_id} version {version}"**
-- **For custom packs**: Check AWS S3 credentials and bucket access
-- **For marketplace packs**: Verify internet connectivity to Palo Alto Networks CDN
-- Ensure pack version exists in the artifact repository
-- Check if pack is in development locally (may not be uploaded yet)
-
-**"Pack {pack_id} not found in manifest"**
-- Verify pack ID matches exactly (case-sensitive)
-- Check that pack is in correct section (`custom_packs` vs `marketplace_packs`)
-- Ensure pack ID in manifest matches the ID in pack metadata
-
-**"Environment not found"**
-- Check config file exists: `~/.config/xsoar-cli/config.json`
-- Verify environment name matches configuration exactly
-- Run `xsoar-cli config create` if configuration is missing
-- Check server connectivity and API credentials
-
-**"WARNING: comment found in manifest for {pack_id}: {comment}"**
-- This is informational only - comments are preserved during updates
-- Review the comment to understand why the version was pinned
-- Decide whether to accept or decline the upgrade based on the comment
-
-### Performance Considerations
-
-- **Large manifests**: Commands may take several minutes with 100+ packs
-- **Network timeouts**: Custom pack validation requires S3 connectivity
-- **Rate limiting**: XSOAR API calls are rate-limited; large deployments may be slower
-
-### Best Practices
-
-1. **Version Control**: Keep `xsoar_config.json` in version control
-2. **Comments**: Use `_comment` field to document version pin reasons
-3. **Testing**: Always validate before deploying to production
-4. **Environment Separation**: Consider different manifests for dev/staging/prod
-5. **Backup**: Run `diff` before `deploy` to understand changes
-6. **Incremental Updates**: Update and deploy frequently rather than large batch updates
-7. **Monitoring**: Check deployment results and verify pack functionality after updates
-
-### Development Workflow
-
-When developing new custom packs:
-
-1. Add pack to manifest with new version
-2. Run `xsoar-cli manifest validate` - may show pack not available (expected)
-3. The validation will pass if local pack metadata matches manifest version
-4. Deploy pack artifacts to S3 repository
-5. Run `xsoar-cli manifest deploy` to install on XSOAR server
-
-### Security Notes
-
-- AWS credentials should be configured securely (IAM roles, not hardcoded keys)
-- XSOAR API keys should be stored in the configuration file with appropriate permissions
-- Consider using different credentials for different environments
-- Review pack sources and content before deploying to production systems
+- **custom_packs**: Organization-developed packs stored in artifact repositories
+- **marketplace_packs**: Official Palo Alto Networks content packs
+- **_comment**: Optional field for documentation (preserved during updates)

xsoar_cli/pack/README.md

@@ -1,7 +1,36 @@
 # Pack
 
+Content pack management commands for XSOAR.
+
 ## Delete
 
-## Deploy
+Delete a content pack from the XSOAR server. Verifies the pack is installed before attempting deletion.
+
+**Syntax:** `xsoar-cli pack delete [OPTIONS] PACK_ID`
+
+**Options:**
+- `--environment TEXT` - Target environment (default: uses default environment from config)
+
+**Arguments:**
+- `PACK_ID` - The ID of the content pack to delete
+
+**Examples:**
+```
+xsoar-cli pack delete MyCustomPack
+xsoar-cli pack delete --environment prod CommonScripts
+```
+
+## Get Outdated
+
+Display a list of outdated content packs showing current and latest available versions in table format.
+
+**Syntax:** `xsoar-cli pack get-outdated [OPTIONS]`
+
+**Options:**
+- `--environment TEXT` - Target environment (default: uses default environment from config)
 
-## Get outdated
+**Examples:**
+```
+xsoar-cli pack get-outdated
+xsoar-cli pack get-outdated --environment staging
+```

xsoar_cli/playbook/README.md

@@ -1,19 +1,43 @@
 # Playbook
 
+Playbook management commands for XSOAR development workflows.
+
 ## Download
-**This command requires a content repository-like directory structure in the current working directory**
-It attempts to provide a smoother development experience when modifying playbooks by doing the following steps:
-1. download the playbook. Attempts to detect the proper content pack and outputs the file to $(cwd)/Packs/PackID/Playbooks/<playbook name>.yml
-2. run demisto-sdk format --assume-yes --no-validate --no-graph <playbook_name.yml>
-3. re-attach the downloaded playbook in XSOAR
-Whitespace characters in Pack ID and Playbook name will be converted to underscores "_".
-
-### Current limitations
-- This command only supports downloading playbooks which are already part of a content pack. Proper implementation on completely new
-playbooks is yet to be implemented.
-- Attempting to download a non-existing playbook will result in a 500 Internal Server Error
-
-#### Example invocation:
+
+Download a playbook from XSOAR, format it with demisto-sdk, and re-attach it to the server. Designed for content repository development workflows.
+
+**Syntax:** `xsoar-cli playbook download [OPTIONS] NAME`
+
+**Options:**
+- `--environment TEXT` - Target environment (default: uses default environment from config)
+
+**Arguments:**
+- `NAME` - The name of the playbook to download
+
+**Examples:**
 ```
-xsoar-cli playbook download "my awesome playbook.yml"
+xsoar-cli playbook download "My Awesome Playbook"
+xsoar-cli playbook download --environment dev "Security Investigation"
 ```
+
+## Requirements
+
+- Must be run from the root of a content repository with proper directory structure
+- Target directory `Packs/<PackID>/Playbooks/` must exist
+- `demisto-sdk` must be installed and available in PATH
+
+## Behavior
+
+1. Downloads the specified playbook from XSOAR
+2. Detects the content pack ID from playbook metadata
+3. Saves to `$(cwd)/Packs/<PackID>/Playbooks/<playbook_name>.yml`
+4. Runs `demisto-sdk format --assume-yes --no-validate --no-graph` on the file
+5. Re-attaches the formatted playbook to XSOAR
+6. Replaces whitespace characters in filenames with underscores
+
+## Limitations
+
+- Only supports playbooks that are already part of a content pack
+- Requires existing content repository directory structure
+- Attempting to download non-existing playbooks results in server errors
+- Does not support completely new playbooks (not yet implemented)

xsoar_cli/utilities.py

@@ -14,7 +14,7 @@ def parse_string_to_dict(input_string: str | None, delimiter: str) -> dict:
     # Parse a string into a python dictionary
     pairs = [pair.split("=", 1) for pair in input_string.split(delimiter)]
     # Filter pairs that have exactly 2 parts (key and value) after splitting by "="
-    valid_pairs = [pair for pair in pairs if len(pair) == 2]
+    valid_pairs = [pair for pair in pairs if len(pair) == 2]  # noqa: PLR2004
     return {key.strip(): value.strip() for key, value in valid_pairs}
 
 

{xsoar_cli-1.0.5.dist-info → xsoar_cli-1.0.6.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xsoar-cli
-Version: 1.0.5
+Version: 1.0.6
 Project-URL: Documentation, https://github.com/tlium/xsoar-cli#readme
 Project-URL: Issues, https://github.com/tlium/xsoar-cli/issues
 Project-URL: Source, https://github.com/tlium/xsoar-cli
@@ -23,13 +23,13 @@ Description-Content-Type: text/markdown
 
 # xsoar-cli
 
-[![PyPI version](https://badge.fury.io/py/xsoar-cli.svg)](https://badge.fury.io/py/xsoar-cli) [![Python](https://img.shields.io/pypi/pyversions/xsoar-cli.svg)](https://pypi.org/project/xsoar-cli/) [![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+![PyPI - Version](https://img.shields.io/pypi/v/xsoar-cli) [![Python](https://img.shields.io/pypi/pyversions/xsoar-cli.svg)](https://pypi.org/project/xsoar-cli/) [![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
 
 A command-line interface for managing Palo Alto Networks XSOAR (Cortex XSOAR) that streamlines content development and deployment workflows.
 
 **Key Features:**
 - **Content Management**: Validate and deploy content packs with declarative manifests
-- **Case Operations**: Retrieve case details and clone cases between environments  
+- **Case Operations**: Retrieve case details and clone cases between environments
 - **Playbook Development**: Download playbooks for local editing and testing
 - **Dependency Analysis**: Generate visual graphs of content pack dependencies
 - **Plugin System**: Extend functionality with custom commands
@@ -165,7 +165,7 @@ For more information on a specific command execute `xsoar-cli <command> --help`.
 ### Commands
 
 - **[case](src/xsoar_cli/case/README.md)** - Retrieve case details and clone cases between environments
-- **[config](src/xsoar_cli/config/README.md)** - Create, validate, and manage CLI configuration files  
+- **[config](src/xsoar_cli/config/README.md)** - Create, validate, and manage CLI configuration files
 - **[graph](src/xsoar_cli/graph/README.md)** - Generate visual dependency graphs for content packs
 - **[manifest](src/xsoar_cli/manifest/README.md)** - Validate and deploy content using declarative manifests
 - **[pack](src/xsoar_cli/pack/README.md)** - Manage content pack operations and information

{xsoar_cli-1.0.5.dist-info → xsoar_cli-1.0.6.dist-info}/RECORD

@@ -1,31 +1,31 @@
-xsoar_cli/__about__.py,sha256=WJ_NW-EdxC6N1rZ9OTTVUtKWWLaNJ0AvBoPxIYQkuYc,127
+xsoar_cli/__about__.py,sha256=GW2FEewJ8n3aYhdn_Mw4Wp6iKtgixzjB_UbHmq0x_1Y,127
 xsoar_cli/__init__.py,sha256=AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs,1
 xsoar_cli/cli.py,sha256=iAlSeZe2iR6ciTVrJYLt-CDZk7b5I-hzHFXbYoXhupA,1342
-xsoar_cli/utilities.py,sha256=ZK0rW4jl1hSbphU_auuuBgwUSmDDP9kq3ZoAFp6D-3g,5697
-xsoar_cli/case/README.md,sha256=MTfgVeW3qJXRPNFo8CkZvulm2vwbN8sgiW86V-qXRFw,1342
+xsoar_cli/utilities.py,sha256=k3REV-d_RFYYjDj8Kb2ljPxADkYffwdfaj0HFeEArbo,5714
+xsoar_cli/case/README.md,sha256=Qpf-HUdkboYoHU5GDkQG1EsQpX2wF7LKsW0CKxmqG1M,1903
 xsoar_cli/case/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-xsoar_cli/case/commands.py,sha256=fdAqX_anYkyRKzzoUNZVYhkTJBqBieUXJX5QqpfEdbE,4255
-xsoar_cli/config/README.md,sha256=pcO858PDL9c0qtwj3_a6B8q2CGvcka3dwclVnwi2vlA,516
+xsoar_cli/case/commands.py,sha256=06UEPoSKutrBtAIbgpp_g6YzYXW2N9zx_KtRi16nPlg,5135
+xsoar_cli/config/README.md,sha256=v8xvmuTV-goDRDn48Ko7VG6YZRy89KajBsGx38Jfj_I,1718
 xsoar_cli/config/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 xsoar_cli/config/commands.py,sha256=i6lWaR0LjAzMpNVPZyCsDPaT0GMVqTUXdau6Id0iOrs,4193
 xsoar_cli/graph/README.md,sha256=kyWIGs2Sd-OdqAaCWJjyvGpAhXhFcuqQwVqFBgzgWzk,861
 xsoar_cli/graph/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 xsoar_cli/graph/commands.py,sha256=LKOpUu8r6KThJ5HdyjZlhpwLKRgMcEu7btBOQXwDkMs,1069
-xsoar_cli/manifest/README.md,sha256=0oiA6rZEAUQMOYM7VmtUBtW3PRo7-exfkjw5JLt_whU,9282
+xsoar_cli/manifest/README.md,sha256=HfdhHlpyJFIm9fC37YaWAwXlG9arhGwpQf2aWO5OewY,3607
 xsoar_cli/manifest/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 xsoar_cli/manifest/commands.py,sha256=nd7-xIJs9qda5iXfFvyfXUG6gctbW9yeUry5KWltisc,10127
-xsoar_cli/pack/README.md,sha256=CA7jAEphHxK0gh58rLRKL-u3wx29QgNAXojd_tGBXnY,46
+xsoar_cli/pack/README.md,sha256=YYVBjxGT4aCQAu1CE16Yo5AnjdL_uh6T9bpAD2eSpl8,891
 xsoar_cli/pack/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 xsoar_cli/pack/commands.py,sha256=1vGF8_mMemZt75qCBTau_M3dihSr79vc2vea8xr5h_Y,2063
-xsoar_cli/playbook/README.md,sha256=8y_YhvZtLP7KzYG83jiVBF-wBAEh8UTJcgmTOTynmbc,977
+xsoar_cli/playbook/README.md,sha256=00ohD9gH_Dt4vWlnPGJIpl_GwVHb274Xao8fR9SHAVc,1474
 xsoar_cli/playbook/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 xsoar_cli/playbook/commands.py,sha256=fZnL5L3pG2gKC4h6q6jmfOQFTa0Tpwnn4e8E5YhDbk0,2794
 xsoar_cli/plugins/README.md,sha256=pxBZlEvWyhRhS4x79dPudYLJHctzuiVxLXBlQ8o2BPI,11236
 xsoar_cli/plugins/__init__.py,sha256=81IZsMbZsqrLdB6TjA9t6s3yS8FkuihliBFX4xZUpTo,1753
 xsoar_cli/plugins/commands.py,sha256=HC0sWu149uQG9Ztag4t2CNPKXTM4WJbEdLSvFMEjw80,10660
 xsoar_cli/plugins/manager.py,sha256=7RPk3lAYDifGMLOU-hFOqyPxTVk8ibBVzBqH7R8wy4g,13012
-xsoar_cli-1.0.5.dist-info/METADATA,sha256=PQLPj12eaIU_U0WJWW07jmVl-5gQmIJLFjdvNihGPfQ,9218
-xsoar_cli-1.0.5.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
-xsoar_cli-1.0.5.dist-info/entry_points.txt,sha256=s6Klu4QRekXsmZaBxMyFlE4Q-4_jIA9uijk4qIYUPvE,48
-xsoar_cli-1.0.5.dist-info/licenses/LICENSE.txt,sha256=l6xnqWKshqwwTXt6ayO6MX8Uvygq0YnkUuFTNnR3ba4,1097
-xsoar_cli-1.0.5.dist-info/RECORD,,
+xsoar_cli-1.0.6.dist-info/METADATA,sha256=k4xkGmn4aS6o5czj5FrPKZaoftTSTzaw0pVe5SLNsSQ,9223
+xsoar_cli-1.0.6.dist-info/WHEEL,sha256=qtCwoSJWgHk21S1Kb4ihdzI2rlJ1ZKaIurTj_ngOhyQ,87
+xsoar_cli-1.0.6.dist-info/entry_points.txt,sha256=s6Klu4QRekXsmZaBxMyFlE4Q-4_jIA9uijk4qIYUPvE,48
+xsoar_cli-1.0.6.dist-info/licenses/LICENSE.txt,sha256=l6xnqWKshqwwTXt6ayO6MX8Uvygq0YnkUuFTNnR3ba4,1097
+xsoar_cli-1.0.6.dist-info/RECORD,,