merge

Author: aviat cohen

.changes/unreleased/added-20251111-144602.yaml

@@ -0,0 +1,25 @@
+## [v1.3.1](https://pypi.org/project/ms-fabric-cli/v1.3.1) - December 15, 2025
+
+### ✨ New Functionality
+
+* Add support of mv, cp, export and import for SQLDatabase item type
+* Add new 'job run-rm' command for remove a scheduled job
+* Enhance `set` command for items to support any settable property path within the item's definition and metadata structure
+* Add support in `ls` commmand using `-q` flag for filtering based on JMESPath expressions
+
+### 🔧 Bug Fix
+
+* Fix `--output_format` argument for command `fab auth status`
+* Fix context persistence in virtual environment
+* Fix create connection with onPremGateway and encryptedCredentials
+
+### ⚡ Additional Optimizations
+
+* Add support for print in key-value list style
+* Optimize LRO polling by calling GetOperationResult API only when a Location header is present
+* Enforce CLI parameter values must be wrapped in single (') or double (") quotes in interactive mode
+
+### 📝 Documentation Update
+
+* Documentation updates
+

.changes/unreleased/fixed-20251111-053940.yaml

@@ -0,0 +1,2 @@
+include src/fabric_cli/core/fab_config/command_support.yaml
+recursive-include src/fabric_cli/commands/fs/payloads *

.changes/unreleased/fixed-20251111-134254.yaml

@@ -28,20 +28,22 @@ List access control entries for a workspace, item, or OneLake resource.
 **Usage:**
 
 ```
-fab acl ls <path> [-l]
+fab acl ls <path> [-l] [-q <query>]
 ```
 
 **Parameters:**
 
 - `<path>`: Path to the resource.
 - `-l, --long`: Show detailed output. Optional.
+- `-q, --query`: JMESPath query to filter results. Optional.
 
 **Examples:**
 
 ```
 fab acl ls workspace1.workspace
 fab acl ls lh1.lakehouse -l
 fab acl ls /Files/data -l
+fab acl ls workspace1.workspace -q [].[?role=='Admin']
 ```
 
 ---

.changes/unreleased/fixed-20251112-081104.yaml

@@ -7,17 +7,24 @@ List workspaces, items, and files.
 **Usage:**
 
 ```
-fab ls <path> [-l] [-a]
+fab ls <path> [-l] [-a] [-q <query>]
 ```
 
 **Parameters:**
 
 - `<path>`: Path to list. Optional.
 - `-l, --long`: Show detailed output. Optional.
 - `-a, --all`: Show hidden entities. Optional.
+- `-q, --query`: JMESPath query to filter results. Optional.
 
-**Example:**
+**Examples:**
 
 ```
 fab ls ws1.Workspace
+fab ls -l
+
+# Using JEMSPath to filter items within ws1 workspace
+fab ls -l -q [].{name:name}
+fab ls ws1.Workspace -q [?contains(name, 'report')]
+fab ls -l -q [?id=='123456']
 ```

.changes/v1.3.1.md

@@ -1,6 +1,18 @@
 # `set` Command
 
-Set a workspace or item property.
+Set a resource property.
+
+**Supported Resource Types:**
+
+- Workspace
+- Item
+- Capacity
+- Domain
+- Connection
+- Gateway
+- Spark Pool
+- Folder
+- Shortcut
 
 !!! info "Setting domain properties requires tenant-level Fabric Administrator privileges"
 
@@ -9,18 +21,64 @@ Set a workspace or item property.
 **Usage:**
 
 ```
-fab set <path> -q <jmespath_query> -i <input_to_replace> [-f]
+fab set <path> -q <jmespath_query> -i <input_value> [-f]
 ```
 
 **Parameters:**
 
 - `<path>`: Path to the resource.
-- `-q, --query <jmespath_query>`: JMESPath query.
-- `-i, --input <input_to_replace>`: Input value to replace.
+- `-q, --query <jmespath_query>`: JMESPath query to the property.
+- `-i, --input <input_value>`: Input value to set.
+    
+    !!! tip "Working with JSON input"
+        For guidance on providing JSON input values across different shells, see [JSON Input Handling](../../essentials/input.md#json-input-handling).
+
 - `-f, --force`: Force set without confirmation. Optional.
 
 **Example:**
 
+```bash
+fab set ws1.Workspace -q displayName -i "New Name" -f
 ```
-fab set ws1.Workspace/nb1.Notebook -q .property -i value
-```
+
+## Limitations
+
+- Only one property path can be specified per `--query` argument
+- Paths must map directly to JSON paths **without** filters or wildcards
+- If the property path doesn't exist on the item definition, it will be added, provided it's valid according to the item's schema. The `set` command supports creation of 1 level at a time (e.g., to set `a.b.c`, first set `a.b`, then set `a.b.c`)
+- Properties that expect a JSON string value are not supported - JSON input is always parsed as an object
+
+## Query Support
+
+The following table shows supported queries per resource type:
+
+| Resource | Supported Queries |
+|----------------|-------------------|
+| **Item** | `displayName`, `description`, `properties` (`.VariableLibrary` only), [`definition.<path>`](#definition-paths) |
+| **Workspace** | `displayName`, `description`, `sparkSettings` |
+| **Capacity** | `sku.name` |
+| **Domain** | `displayName`, `description`, `contributorsScope` |
+| **Connection** | `displayName`, `privacyLevel`, `credentialDetails` |
+| **Gateway** | `displayName`, `allowCloudConnectionRefresh`, `allowCustomConnectors`, `capacityId`, `inactivityMinutesBeforeSleep`, `numberOfMemberGateways` |
+| **Spark Pool** | `name`, `nodeSize`, `autoScale.enabled`, `autoScale.minNodeCount`, `autoScale.maxNodeCount` |
+| **Folder** | `displayName` |
+| **Shortcut** | `name`, `target` |
+
+<a id="definition-paths"></a>
+!!! note "Setting Item Definition Properties"
+    For **Items**, you can set any explicit path within the `definition` structure using dot notation for nested properties (e.g. `definition.parts[0].property`).
+    Paths must map directly to JSON paths **without** filters or wildcards. Refer to the [Microsoft Fabric item definitions](https://learn.microsoft.com/en-us/rest/api/fabric/articles/item-management/definitions) for the complete definition structure.
+
+#### Item-Specific Definition Path Aliasing
+
+!!! warning "Note on definition path aliases"
+
+    These definition path aliases may be deprecated in a future release. We strongly recommend using explicit JSON paths within the item's definition structure rather than aliases.
+
+These are definition path aliases that map to specific paths in the item's definition structure. When using the `set` command, you can use these aliases directly (as the `-query` / `--q` argument value) as they map to the correct definition paths:
+
+| Item Type | Definition Path Alias | Notes |
+|-----------|----------------|-------|
+| **Notebook** | `lakehouse`, `environment`, `warehouse` | |
+| **Report** | `semanticModelId` | Applies only to [Report definition.pbir version 1](https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-report?tabs=v1%2Cdesktop#definitionpbir). For other versions, check the correct property path in the Report definition documentation |
+| **SparkJobDefinition** | `payload` | |

MANIFEST.in

@@ -20,6 +20,7 @@ The `job` commands provide tools for starting, running, monitoring, and scheduli
 | `job run-status`| Get job run details       | `job run-status <path> [--id <id>] [--schedule]`                      |
 | `job run-sch`   | Schedule a job            | `job run-sch <path> [-i <json_inline_or_path>*] [--type <type>] [--interval <interval>] [--days <days>]` |
 | `job run-update`| Update a scheduled job    | `job run-update <path> [--id <id>] [-i <json_inline_or_path>] [--type <type>] [--enable/--disable]` |
+| `job run-rm`    | Delete a scheduled job    | `job run-rm <path> [--id <scheduled-id>] [--force]` |
 
 ---
 
@@ -161,4 +162,22 @@ fab job run-cancel <path> --id <job_id> [--wait]
 
 ---
 
+### run-rm
+
+Remove a scheduled job.
+
+**Usage:**
+
+```
+fab job run-rm <path> --id <scheduled-id> [-f]
+```
+
+**Parameters:**
+
+- `<path>`: Path to the resource.
+- `--id`: Schedule ID to remove.
+- `-f, --force`: Bypass confirmation prompt. Optional.
+
+---
+
 For more examples and detailed scenarios, see [Job Management Examples](../../examples/job_examples.md).