show service order as-yaml
Syntax
show service order as-yaml
show service order as-yaml service-order-name
show service order as-yaml service-order-name | save directory-path/file-name.yaml
Description
Displays details of a service order in the YAML format. If you do not specify a service order name for viewing details, details of all the service orders generated in an organization is displayed as an array. You can save the service order details in the YAML format in the service orchestration cMGD pod file system by providing the directory and filename to save.
Options
|
none |
View all service orders generated for an organization in the YAML format, as an array. |
|
service-order-name |
The service order that you want to view in the YAML format. This option allows you to view a specific order in the YAML format. |
|
save |
This option allows you to save service orders in the YAML format to the service orchestration cMGD pod file system. |
|
directory-path |
The location in the service orchestration cMGD pod file system where you want to save the YAML file. For example, /var/tmp. |
|
file-name |
File name you assign to the YAML file when you are saving the file in the service orchestration cMGD pod file system. |
Sample Output
show service order as-yaml
- "customer_id": "ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879"
"design_id": "routing"
"design_version": "0.1.0"
"fh_config":
"edited-by": "3pic.t3st3r@gmail.com"
"status": "network resources updated"
"instance_id": "l3vpn-routing-iid"
"operation": "create"
"order_id": "cc198caf-e2c1-11ee-a392-f6e61c3d4879"
"org_id": "3c97990f-8446-4fa5-9b88-edd3ddad6cb0"
"routing":
"autonomous_system":
- "count": !!int "1024"
"name": !!int "65001"
"route_reflector":
"clusters":
- "cluster": "1.1.1.1"
- "cluster": "2.2.2.2"
- "cluster": "3.3.3.3"
"spring":
"sids":
"size": !!int "1000"
"upload_time": "2024-03-15T11:47:38Z"
"version": "1.0.0"
"workflow_run_id": "manual__2024-03-15T11:47:35.218599+00:00"
- "customer_id": "ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879"
"design_id": "vpn"
"design_version": "0.3.0"
"fh_config":
"edited-by": "3pic.t3st3r@gmail.com"
"status": "network resources updated"
"instance_id": "l3vpn-vpn-iid"
"operation": "create"
"order_id": "d66e57c1-e2c1-11ee-a392-f6e61c3d4879"
"org_id": "3c97990f-8446-4fa5-9b88-edd3ddad6cb0"
"upload_time": "2024-03-15T11:47:53Z"
"version": "1.0.0"
"vpn":
"route_distinguisher":
- "count": !!int "1024"
"name": !!int "1234"
- "count": !!int "1024"
"name": !!int "1235"
"route_target":
- "count": !!int "1024"
"name": !!int "1234"
- "count": !!int "1024"
"name": !!int "1235"
"workflow_run_id": "manual__2024-03-15T11:47:49.885346+00:00"
- "customer_id": "ebd5a8bf-e2bf-11ee-a392-f6e61c3d4879"
"design_id": "topo"
"design_version": "0.5.4"
"fh_config":
"edited-by": "3pic.t3st3r@gmail.com"
"status": "network resources updated"
"instance_id": "l3vpn-topology-iid"
"operation": "create"
"order_id": "6f80e20e-e2c2-11ee-a392-f6e61c3d4879"
"org_id": "3c97990f-8446-4fa5-9b88-edd3ddad6cb0"
"topo":
"pop":
- "name": "f883d678-c42f-4ddc-9476-ba30a1a2ef45"
"pe":
- "access":
- "ce": "ce1"
"name": "xe-1/0/3"
"speed": !!int "10000"
"type": "ethernet"
"bandwidth": !!int "40000000"
"mac_addrs": !!int "1000000"
"name": "00000000-0000-0000-1000-d4996c636668"
"routes": !!int "100000"
"postal_code": "10321"
"postal_code_matches":
- "name": "SVL"
"regex": "10..."
- "name": "f2d77dde-682b-4e16-94a2-97cff5e30fc7"
"pe":
- "access":
- "ce": "ce2"
"name": "xe-1/0/3"
"speed": !!int "10000"
"type": "ethernet"
"bandwidth": !!int "40000000"
"mac_addrs": !!int "1000000"
"name": "00000000-0000-0000-1000-d4996c4c2ac0"
"routes": !!int "100000"
"postal_code": "20321"
"postal_code_matches":
- "name": "BNG"
"regex": "20..."
"upload_time": "2024-03-15T11:52:12Z"
"version": "1.0.0"
"workflow_run_id": "manual__2024-03-15T11:52:07.069486+00:00"
Release Information
Command introduced in Juniper Paragon Automation Release 2.0.0.