Add new API documentation for managing blueprints and visual connections

- Created documentation for removing visual connectors by alias and endpoints.
- Added methods for setting visual connector attributes.
- Introduced new API endpoints for importing blueprints and managing global inputs.
- Documented various operations for updating blueprints, including adding/removing resources, services, and attributes.
- Enhanced existing documentation with clearer examples and structured parameters.
- Organized new and existing documentation under the "Updating Blueprints" category for better navigation.

Author: qkalsky

docs/api-guide/packaging-api/creat-and-load-blueprint-pkg/packaging-functions/create.md

@@ -18,5 +18,5 @@ sidebar_position: 1
 
 **Sample:**
 ```javascript
-`packageEditor.create('c:\\temp\\TestPackage.zip')`
+packageEditor.create('c:\\temp\\TestPackage.zip')
 ```

docs/api-guide/packaging-api/creat-and-load-blueprint-pkg/packaging-functions/get-topology-names.md

@@ -17,7 +17,7 @@ sidebar_position: 4
 **Sample:**
 
 ```javascript
-`packageEditor.get_topology_names()`
+packageEditor.get_topology_names()
 ```
 
 ```javascript

docs/api-guide/packaging-api/creat-and-load-blueprint-pkg/packaging-functions/load.md

@@ -17,5 +17,5 @@ sidebar_position: 2
 **Sample:**
 
 ```javascript
-`packageEditor.load('c:\\temp\\TestPackage.zip')`
+packageEditor.load('c:\\temp\\TestPackage.zip')
 ```

docs/api-guide/packaging-api/editing-blueprint-connectivity/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Editing Blueprint Connectivity",
+  "position": 5
+}

docs/api-guide/packaging-api/editing-blueprint-connectivity/index.md

@@ -0,0 +1,18 @@
+# Editing Blueprint Connectivity
+
+![](/Images/API/Packaging-API/UpdatingDataModel.png)
+
+This section explains how to:
+
+**Routing:**
+- [Add Routes](./routing/add-routes.md)
+- [Remove Routes (by Alias)](./routing/remove-routes-by-alias.md)
+- [Remove Routes (by Endpoints)](./routing/remove-routes-by-endpoint.md)
+- [Set a Route's Attributes](./routing/set-route-attr.md)
+
+**Visual Connectors:**
+- [Add Visual Connectors](./visual-connections/add-visual-conn.md)
+- [Remove Visual Connectors (by Alias)](./visual-connections/remove-visual-conn-by-alias.md)
+- [Remove Visual Connectors (by Endpoints)](./visual-connections/remove-visual-conn-vy-endpoint.md)
+- [Set a Visual Connector's Attributes](./visual-connections/set-visual-conn-attr.md)
+

docs/api-guide/packaging-api/editing-blueprint-connectivity/routing/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Routing",
+  "position": 1,
+  "link": {
+    "type": "generated-index",
+    "description": "This section provides an overview of the APIs available for editing blueprint connectivity using routes. To learn more about these APIs, check out the following articles:"
+  }
+}

docs/api-guide/packaging-api/editing-blueprint-connectivity/routing/add-routes.md

@@ -0,0 +1,28 @@
+---
+sidebar_position: 1
+---
+
+# Add Routes
+
+**Description**: Create a route between the source and target resources in a specific blueprint.
+
+**Signature**: `add_route(topology_name, route_alias, source, target, route_interface, max_hops, direction, shared)`
+
+**Parameters**:
+
+| Name | Direction | Required | Description |
+| --- | --- | --- | --- |
+| `topology_name` | In | Yes | The name of the blueprint |
+| `route_alias` | In | Yes | Specify the route’s alias. |
+| `source` | In | Yes | The name and path of the source resource (end point) |
+| `target` | In | Yes | The name and path of the target resource (end point) |
+| `route_interface` | In | Yes | The protocol type of the end points |
+| `max_hops` | In | Yes | Specify the maximum number or allowed hops. |
+| `direction` | In | Yes | Specify the direction of the route: Uni, Bi |
+| `shared` | In | Yes | Specify whether these routes are shared. Shared routes can be used in more than one sandbox. |
+
+**Sample**:
+
+```javascript
+packageEditor.add_route('blueprint1', 'ABC','Chassis1/Blade1/Port1','Chassis2/Blade1/Port1','Ethernet',3,'Bi',False)
+```

docs/api-guide/packaging-api/editing-blueprint-connectivity/routing/remove-routes-by-alias.md

@@ -0,0 +1,22 @@
+---
+sidebar_position: 2
+---
+
+# Remove Routes (by Alias)
+
+**Description**: Remove an existing route from a specific blueprint.
+
+**Signature**: `remove_route_by_alias(topology_name, route_alias)`
+
+**Parameters**:
+
+| Name | Direction | Required | Description |
+| --- | --- | --- | --- |
+| `topology_name` | In | Yes | The name of the blueprint |
+| `route_alias` | In | Yes | Specify the route’s alias. |
+
+**Sample**:
+
+```javascript
+packageEditor.remove_route_by_alias('blueprint1', 'ABC')
+```

docs/api-guide/packaging-api/editing-blueprint-connectivity/routing/remove-routes-by-endpoint.md

@@ -0,0 +1,24 @@
+---
+sidebar_position: 3
+---
+
+# Remove Routes (by Endpoints)
+
+**Description**: Remove an existing route from a specific blueprint.
+
+**Signature**: `remove_route_by_endpoints(topology_name, source, target, direction)`
+
+**Parameters**:
+
+| Name | Direction | Required | Description |
+| --- | --- | --- | --- |
+| `topology_name` | In | Yes | The name of the blueprint |
+| `source` | In | Yes | The name and path of the source resource (end point) |
+| `target` | In | Yes | The name and path of the target resource (end point) |
+| `direction` | In | Yes | Specify the direction of the route: Uni, Bi |
+
+**Sample**:
+
+```javascript
+packageEditor.remove_route_by_endpoints('blueprint1', 'Chassis1/Blade1/Port4','Chassis2/Blade1/Port1','Bi')
+```

docs/api-guide/packaging-api/editing-blueprint-connectivity/routing/set-route-attr.md

@@ -0,0 +1,74 @@
+---
+sidebar_position: 4
+---
+
+# Set a Route's Attributes
+
+**Description**: Set the value for an attribute on the route's L1 ports. The attribute is specified by the route’s alias and attribute name. Note that this action sets the attribute value on the actual L1 resource ports.
+
+**Signature**: `set_route_attribute(topology_name, route_alias, attribute_name, target, attribute_value)`
+
+**Parameters**:
+
+
+<table>
+<thead>
+    <tr>
+        <th>Name</th>
+        <th>Direction</th>
+        <th>Required</th>
+        <th>Description</th>
+    </tr>
+</thead>
+<tbody>
+    <tr>
+        <td>`topology_name`</td>
+        <td>In</td>
+        <td>Yes</td>
+        <td>The name of the blueprint</td>
+    </tr>
+    <tr>
+        <td>`route_alias`</td>
+        <td>In</td>
+        <td>Yes</td>
+        <td>Specify the route’s alias.</td>
+    </tr>
+    <tr>
+        <td>`attribute_name`</td>
+        <td>In</td>
+        <td>Yes</td>
+        <td>Specify the attribute name that you want to add / update, only attributes that have the rule **Link Configurations** can be used as route attributes</td>
+    </tr>
+    <tr>
+        <td>`target`</td>
+        <td>In</td>
+        <td>Yes</td>
+        <td>
+Specify on which resources to apply the attribute changes:
+<ul>
+<li>
+**Source** refers to the L1 resource connected to the source endpoint of the route
+</li>
+<li>
+**Target** refers to the L1 resource connected to the target endpoint of the route
+</li>
+<li>
+**All** encompasses all of the route's L1 resources
+</li>
+</ul>
+        </td>
+    </tr>
+    <tr>
+        <td>`attribute_value`</td>
+        <td>In</td>
+        <td>Yes</td>
+        <td>Specify the value to set on the attribute</td>
+    </tr>
+</tbody>
+</table>
+
+**Sample**:
+
+```javascript
+packageEditor.set_route_attribute(‘environment1’, 'alias', 'type', 'All', 'auto connection')
+```