Application Move/Merge¶

Overview¶

Use this API to move or merge an AS3 or service-catalog application service.

For information about the compatibility of BIG-IQ and BIG-IP with F5 Application Services 3 Extension (AS3) and F5 Declarative Onboarding (DO) releases, please refer to the support article: K54909607: BIG-IQ Centralized Management compatibility with F5 Application Services 3 Extension and F5 Declarative Onboarding .

REST Endpoint: mgmt/cm/global/global-apps-merge-move¶

Requests¶

POST mgmt/cm/global/global-apps-merge-move¶

To move or merge an AS3 or service-catalog application service you can send the POST request to the global-apps-merge-move endpoint.

Request Parameters¶

The JSON in the body of a POST request can include the following parameters.

Name	Type	Required	Description
componentAppReferencesToMove	string	Required for a move.	Reference to the application you want to move.
link	string	True	Url for the application you want to move.
deleteEmptyGlobalAppsWhenDone	boolean	True	Remove old application when done with move or merge.
globalAppReferencesToMerge	array	Required for a merge.	A list of references to the applications you want to merge.
link	string	True	Url for an application you want to merge.
requireNewGlobalApp	boolean	True	Make the new application required.
targetGlobalAppName	string	True	Name for the new application.

Query Parameters¶

None

Response¶

HTTP/1.1 200 OK

The JSON in the body of the response can include the following parameters.

Name	Type	Description
componentAppReferencesToMove	string	Reference to the application you want to move.
link	string	Url for the application you want to move.
deleteEmptyGlobalAppsWhenDone	boolean	Remove old application when done with move or merge.
globalAppReferencesToMerge	array	A list of references to the applications you want to merge.
link	string	Url for an application you want to merge.
requireNewGlobalApp	boolean	Make the new application required.
targetGlobalAppName	string	Name for the new application.

Permissions¶

Role	Allow
Application_Creator	Yes
Application_Manager	Yes

Examples¶

POST to move an application¶

The following example sends a POST request to move an application. You can get the value of componentAppReferencesToMove for the application by using the Applications API to send a GET request to query the /mgmt/cm/global/config-sets collection.

POST https://198.51.100.35/mgmt/cm/global/global-apps-merge-move

The JSON in the body of the POST can look similar to the following example.

{
    "componentAppReferencesToMove": [{
            "link": "https://localhost/mgmt/cm/global/config-sets/d75df3c2-9527-3535-9c53-9b00b041ed08"
    }],
    "targetGlobalAppName": "new_GA_1",
    "deleteEmptyGlobalAppsWhenDone": false,
    "requireNewGlobalApp": true
}

Response¶

The JSON in the body of the response can look similar to the body of the request.

POST to merge applications¶

The following example sends a POST request to merge applications. You can get the value of globalAppReferencesToMerge for the applications by sending a GET request to query the /mgmt/cm/global/global-apps collection.

POST https://198.51.100.35/mgmt/cm/global/global-apps-merge-move

The JSON in the body of the POST can look similar to the following example.

{
    "globalAppReferencesToMerge": [{
                    "link": "https://localhost/mgmt/cm/global/global-apps/69cf49ad-de27-3540-b38f-9773d06ca1c4"
            },
            {
                    "link": "https://localhost/mgmt/cm/global/global-apps/3e4ee660-e3e4-37c9-99bf-80d79119961f"
            }
    ],
    "targetGlobalAppName": "new_GA_2",
    "deleteEmptyGlobalAppsWhenDone": false,
    "requireNewGlobalApp": true
}

Response¶

The JSON in the body of the response can look similar to the body of the request.

Previous Next