Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Juniper Paragon Automation User Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

show service order as-json

date_range 23-Aug-24

Syntax

content_copy zoom_out_map
show service order as-json
content_copy zoom_out_map
show service order as-json service-order-name
content_copy zoom_out_map
show service order as-json service-order-name | save directory-path/file-name.json

Description

Displays details of a specific order in the JSON 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 JSON format in the service orchestration cMGD pod file system by providing the directory and filename to save.

You can use the downloaded service order JSON files as sample templates, edit the values on the files, and upload the files to create new service orders by using the Paragon Automation GUI, service orchestration cMGD CLI, or REST API.

Options

none

View all service orders generated for an organization in the JSON format, as an array.

service-order-name

Specify the name of the service order that you want to view in the JSON format.

This option allows you to view a specific order in the JSON format.

save

This option allows you to save service orders in the JSON 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 JSON file. For example, /var/tmp.

file-name

File name you assign to the JSON file when you are saving the file in the service orchestration cMGD pod file system.

Sample Output

show service order as-json servic-order-name

content_copy zoom_out_map
[
    {
        "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": 1024,
                    "name": 65001
                }
            ],
            "route_reflector": {
                "clusters": [
                    {
                        "cluster": "1.1.1.1"
                    },
                    {
                        "cluster": "2.2.2.2"
                    },
                    {
                        "cluster": "3.3.3.3"
                    }
                ]
            },
            "spring": {
                "sids": {
                    "size": 1000
                }
            }
        },
        "upload_time": "2024-03-15T11:47:38Z",
        "version": "1.0.0",
        "workflow_run_id": "manual__2024-03-15T11:47:35.218599+00:00"
    }
]

Release Information

Command introduced in Paragon Automation Release 2.0.0.

footer-navigation