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

Creates provisioned configurations.

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

PUT /2021-04-06/services/{serviceName}/functions/{functionName}/provision-config

Request parameters

Parameter	Type	Required	Description	Example
serviceName	string	Yes	The name of the service.	demoService
qualifier	string	Yes	The service alias or latest version. Other versions are not supported.	prod
functionName	string	Yes	The function name.	demoFunction
body	object	No	The provisioned configurations.
target	long	Yes	The number of target provisioned instances. Valid values: [0,10000].	1
scheduledActions	array	No	The configurations of scheduled auto scaling.
	ScheduledActions	No	The detailed configurations of the scheduled auto scaling.
targetTrackingPolicies	array	No	The configurations of metric-based auto scaling.
	TargetTrackingPolicies	No	The detailed configurations of metric-based auto scaling.
alwaysAllocateCPU	boolean	No	Specifies whether to always allocate CPU resources. Default value: true.	true
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 follows 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 invocation request of Function Compute.	rid281s******

Response parameters

Parameter	Type	Description	Example
	object	The details of provisioned configurations.
resource	string	The description of the resource.	"12345#servierName#qualifier#functionName"
target	long	The number of target provisioned instances.	5
current	long	The actual number of provisioned instances.	1
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 the metricTarget parameter, the system scales out provisioned instances based on a progressive policy to make the metric value near the value of the metricTarget parameter. When the metric value is smaller than the value of the metricTarget parameter, the system scales in provisioned instances based on a conservative policy to make the metric value near the value of the metricTarget parameter. 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, } ]
alwaysAllocateCPU	boolean	Specifies whether to always allocate CPU to a function instance.	true

Examples

Sample success responses

JSONformat

{
  "resource": "\"12345#servierName#qualifier#functionName\"",
  "target": 5,
  "current": 1,
  "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
    }
  ],
  "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

see changesets

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

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