ListProvisionConfigs - Function Compute (2.0) - Alibaba Cloud Documentation Center

Queries configurations of provisioned instances.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Debug

Authorization information

There is currently no authorization information disclosed in the API.

Request syntax

GET /2021-04-06/provision-configs

Request parameters

Parameter	Type	Required	Description	Example
limit	long	No	The maximum number of results to return. Default value: 20. Maximum value: 100. The number of returned resources is less than or equal to the specified number.	20
nextToken	string	No	The token required to obtain more results. You do not need to specify this parameter in the first call. If a NextToken value is returned by a previous call, more results are available.	demoNextToken
serviceName	string	No	The name of the service to which resources belong.	serviceName
qualifier	string	No	The qualifier of the service to which resources belong. The qualifier must be aliasName and used together with the serviceName parameter.	prod
X-Fc-Account-Id	string	No	The ID of your Alibaba Cloud account.	188077086902****
X-Fc-Date	string	No	The time when the function is invoked. The value is in the EEE,d MMM yyyy HH:mm:ss GMT format.	Wed, 11 May 2022 09:00:00 GMT
X-Fc-Trace-Id	string	No	The trace ID of the request for Function Compute API.	rid281s******

Response parameters

Parameter	Type	Description	Example
	object	Configurations of provisioned instances.
nextToken	string	The token used to obtain more results.	demoNextToken
provisionConfigs	object []	The information about provisioned instances.
resource	string	The description of the resource.	12345#servierName#qualifier#functionName
target	long	The expected number of resources.	5
current	long	The number of current resources.	5
scheduledActions	array	The configurations of scheduled auto scaling.
	ScheduledActions	Details about the scheduled scaling policy. You can use the scheduled scaling policy to flexibly configure provisioned instances. You can specify the number of provisioned instances to the desired value at the scheduled time. This way, the number of provisioned instances can meet the concurrency requirements of your business.	[ { "Name": "action_1", "StartTime": "2020-11-01T10:00:00Z", "EndTime": "2020-11-30T10:00:00Z", "TargetValue": 50, "ScheduleExpression": "cron(0 0 20 * * )" }, { "Name": "action_2", "StartTime": "2020-11-01T10:00:00Z", "EndTime": "2020-11-30T10:00:00Z", "TargetValue": 10, "ScheduleExpression": "cron(0 0 22 * *)" } ]
targetTrackingPolicies	array	The configurations of metric-based auto scaling.
	TargetTrackingPolicies	Details about the metric-based scaling policy. Provisioned instances are scaled every minute based on the concurrency usage rate of provisioned instances. When the metric value exceeds the value of metricTarget, the system starts to scale out provisioned instances with an active policy to restore the metric value close to the value of metricTarget. When the metric value is lower than the value metricTarget, the system starts to scale in provisioned instances with a conservative policy so that the metric value gradually reaches the value metricTarget. If you specify the maximum and minimum numbers of provisioned instances, the system scales provisioned instances within the range. If the number of provisioned instances reaches the specified maximum or minimum number, scaling stops.	[ { "Name": "action_1", "StartTime": "2020-11-01T10:00:00Z", "EndTime": "2020-11-30T10:00:00Z", "MetricType": "ProvisionedConcurrencyUtilization", "MetricTarget": 0.6, "MinCapacity": 10, "MaxCapacity": 100, } ]
currentError	string	The error message returned if a provisioned instance fails to be created.	image not found
alwaysAllocateCPU	boolean	Specifies whether to always allocate CPU resources to function instances.	true

Examples

Sample success responses

JSONformat

{
  "nextToken": "demoNextToken",
  "provisionConfigs": [
    {
      "resource": "12345#servierName#qualifier#functionName",
      "target": 5,
      "current": 5,
      "scheduledActions": [
        {
          "name": "name",
          "startTime": "2020-10-10T10:10:10Z",
          "endTime": "2021-10-10T10:10:10Z",
          "target": 50,
          "scheduleExpression": "cron(0/30 * * * *)"
        }
      ],
      "targetTrackingPolicies": [
        {
          "name": "test_1",
          "startTime": "2020-10-10T10:10:10Z",
          "endTime": "2020-10-10T10:10:10Z",
          "metricType": "CPUUtilization",
          "metricTarget": 0.6,
          "minCapacity": 10,
          "maxCapacity": 100
        }
      ],
      "currentError": "image not found",
      "alwaysAllocateCPU": true
    }
  ]
}

Error codes

For a list of error codes, visit the Service error codes.

Change history

Change time

Summary of changes

Operation

2021-06-30

The request parameters of the API has changed

see changesets

Change item	Change content
Input Parameters	The request parameters of the API has changed.
	Added Input Parameters: X-Fc-Account-Id
	Added Input Parameters: X-Fc-Code-Checksum
	Added Input Parameters: X-Fc-Log-Type
	Added Input Parameters: X-Fc-Invocation-Type
	Added Input Parameters: X-Fc-Date
	Added Input Parameters: X-Fc-Trace-Id

2021-06-30

The request parameters of the API has changed. The response structure of the API has changed

see changesets

Change item	Change content
Input Parameters	The request parameters of the API has changed.
	Added Input Parameters: X-Fc-Account-Id
Output Parameters	The response structure of the API has changed.

2021-06-30

The request parameters of the API has changed

see changesets

Change item	Change content
Input Parameters	The request parameters of the API has changed.
	delete Input Parameters: X-Fc-Account-Id