Application Management

Update Application parameters

Update an existing, deployed FAST Application with the supplied parameters. Existing parameter values from the deployed Application will be used as defaults for any missing parameter values.

patch/applications/{tenantName}/{appName}

Request body

parametersParametersDefinition required

Object must conform to specified template's schema.

Example request

{
  "parameters": {
    "tenant": "foo",
    "application": "bar",
    "virtualAddress": "192.0.2.11"
  }
}

Response

Template Job Submitted Successfully, check the provided Task ID to get the status of the deployment.

codeinteger required

requestIdinteger

Example response

{
  "_links": {
    "self": "/mgmt/shared/fast/applications",
    "task": "/mgmt/shared/fast/tasks/12345"
  },
  "code": 202,
  "requestId": 3,
  "message": [
    {
      "id": "ff70c2c0-af21-44c8-8fec-18e2d82eabf0",
      "name": "examples/simple_udp_defaults",
      "parameters": {
        "tenant_name": "tenant",
        "application_name": "app"
      }
    }
  ]
}

Changes

Changed in 2 of the 50 revisions of this API.534

Oct 20, 2025702ae6b27810222See the full diff
- ▲
  the code response's property type/format changed from integer/int32 to / for status 400
  response-property-type-changed
- ▲
  the code response's property type/format changed from integer/int32 to / for status 500
  response-property-type-changed
- ●
  added the new 400.00 enum value to the code response property for the response status 400
  response-property-enum-value-added
- ●
  added the new 500.00 enum value to the code response property for the response status 500
  response-property-enum-value-added
- ○
  added the optional property error to the response with the 500 status
  response-optional-property-added
- ○
  added the required property errors to the response with the 400 status
  response-required-property-added
Sep 26, 20228a7a27296ff3312See the full diff
- ▲
  the code response's property type/format changed from / to integer/int32 for status 400
  response-property-type-changed
- ▲
  the code response's property type/format changed from / to integer/int32 for status 500
  response-property-type-changed
- ▲
  removed the required property errors from the response with the 400 status
  response-required-property-removed
- ●
  removed the optional property error from the response with the 500 status
  response-optional-property-removed
- ○
  removed the 400.00 enum value from the code response property for the response status 400
  response-property-enum-value-removed
- ○
  removed the 500.00 enum value from the code response property for the response status 500
  response-property-enum-value-removed
This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history