The region ID of the stack group. You can call the \[DescribeRegions]\(~~131035~~) operation to query the latest list of Alibaba Cloud regions.
Operation description
The name of the stack group. The name must be unique within a region.
The name can be up to 255 characters in length and can contain digits, letters, hyphens (-), and underscores (_). The name must start with a digit or a letter.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
ros:UpdateStackGroup | update |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
RegionId | string | Yes | The region IDs of stack instances. You can specify a maximum of 20 region IDs. | cn-hangzhou |
StackGroupName | string | Yes | The region IDs of stack instances. You can specify a maximum of 20 region IDs. | MyStackGroup |
Description | string | No | The structure that contains the template body. The template body must be 1 to 524,288 bytes in length. If the length of the template body exceeds the upper limit, we recommend that you add parameters to the HTTP POST request body to prevent request failures caused by excessively long URLs. Note
You must specify only one of the TemplateBody, TemplateURL, and TemplateId parameters.
| My Stack Group |
AccountIds | array | No | The URL of the file that contains the template body. The URL must point to a template that is located on an HTTP or HTTPS web server or in an Alibaba Cloud Object Storage Service (OSS) bucket. The template body must be 1 to 524,288 bytes in length. Examples: oss://ros/template/demo and oss://ros/template/demo?RegionId=cn-hangzhou. If you do not specify the region ID of the OSS bucket, the value of the RegionId parameter is used. Note
You must specify only one of the TemplateBody, TemplateURL, and TemplateId parameters.
| |
string | No | The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that the token is unique among different requests. The token can be up to 64 characters in length and can contain letters, digits, hyphens (-), and underscores (_). For more information, see Ensure idempotence. | ["151266687691****","141261387191****"] | |
RegionIds | array | No | The description of the operation to update the stack group. | |
string | No | The preferences of the operation to update the stack group. The following parameters are available:
Separate multiple parameters with commas (,). Note
| ["cn-hangzhou","cn-beijing"] | |
TemplateBody | string | No | The name of the RAM role to be assumed by the administrator account in ROS. This parameter is required if you want to grant self-managed permissions to the stack group. If you do not specify a value for this parameter, the default value AliyunROSStackGroupAdministrationRole is used. You can use the administrator role in ROS to assume the execution role AliyunROSStackGroupExecutionRole to perform operations on the stacks that correspond to stack instances in the stack group. The name must be 1 to 64 characters in length, and can contain letters, digits, and hyphens (-). | {"ROSTemplateFormatVersion": "2015-09-01"} |
TemplateURL | string | No | The name of the RAM role to be assumed by the administrator role AliyunROSStackGroupAdministrationRole. This parameter is required if you want to grant self-managed permissions to the stack group. If you do not specify a value for this parameter, the default value AliyunROSStackGroupExecutionRole is used. You can use this role in ROS to perform operations on the stacks that correspond to stack instances in the stack group. The name must be 1 to 64 characters in length, and can contain letters, digits, and hyphens (-). | oss://ros-template/demo |
ClientToken | string | No | The ID of the template. This parameter applies to shared and private templates. Note
You must specify only one of the TemplateBody, TemplateURL, and TemplateId parameters.
| 123e4567-e89b-12d3-a456-42665544**** |
OperationDescription | string | No | The version of the template. If you do not specify a version, the latest version is used. Note
This parameter takes effect only if the TemplateId parameter is set.
| Update stack instances in hangzhou |
OperationPreferences | object | No | The list of parameters. | {"FailureToleranceCount": 1,"MaxConcurrentCount": 2} |
AdministrationRoleName | string | No | The key of parameter N. If you do not specify the key and value of the parameter, ROS uses the default key and value in the template. Maximum value of N: 200. Note
The Parameters parameter is optional. If you set the Parameters parameter, you must set the Parameters.N.ParameterKey parameter.
| AliyunROSStackGroupAdministrationRole |
ExecutionRoleName | string | No | The value of parameter N. Maximum value of N: 200. Note
The Parameters parameter is optional. If you set the Parameters parameter, you must set the Parameters.N.ParameterValue parameter.
| AliyunROSStackGroupExecutionRole |
TemplateId | string | No | The permission model. Valid values:
Note
| 5ecd1e10-b0e9-4389-a565-e4c15efc**** |
TemplateVersion | string | No | The information about automatic deployment settings. Note
This parameter is required only if the PermissionModel parameter is set to SERVICE_MANAGED.
| v1 |
Parameters | array<object> | No | Specifies whether to enable automatic deployment. Valid values:
| |
object | No | |||
ParameterKey | string | Yes | Specifies whether to retain stacks in a member when you remove the member from the folder. Valid values:
Note
This parameter is required if the Enabled parameter is set to true.
| Amount |
ParameterValue | string | Yes | The folders in which you want to use service-managed permissions to update stacks. | 1 |
PermissionModel | string | No | The folder IDs in the resource directory. You can specify a maximum of five folder IDs. You must set at least one of the RdFolderIds and AccountIds parameters. The parameters are subject to the following items:
Note
To view the folder IDs, go to the Overview page in the Resource Management console. For more information, see View the basic information of a folder.
| SELF_MANAGED |
AutoDeployment | object | No | The IDs of the folders in the resource directory. You can specify up to five folder IDs. You can create stacks within all members in the specified folders. If you create stacks in the Root folder, the stacks are created within all members in the resource directory. Note
To view the folder IDs, go to the Overview page in the Resource Management console. For more information, see View the basic information of a folder.
| |
Enabled | boolean | Yes | The IDs of the members in the resource directory. You can specify a maximum of 20 member IDs. Note
To view the member IDs, go to the Overview page in the Resource Management console. For more information, see View the detailed information of a member.
| true |
RetainStacksOnAccountRemoval | boolean | No | The IDs of the members in the resource directory. You can specify a maximum of 20 member IDs. Note
To view the member IDs, go to the Overview page in the Resource Management console. For more information, see View the detailed information of a member.
| true |
DeploymentTargets | object | No | The ID of the request. | |
RdFolderIds | array | No | The ID of the operation. | |
string | No | The IDs of the folders in the resource directory. You can add up to five folder IDs. You can create stacks within all members in the specified folders. If you create stacks in the Root folder, the stacks are created within all members in the resource directory. Note
To view the folder IDs, go to the Overview page in the Resource Management console. For more information, see View the basic information of a folder.
| ["fd-4PvlVLOL8v"] | |
AccountIds | array | No | The list of one or more Alibaba Cloud accounts with which you want to share or unshare the template. | |
string | No | The IDs of the members in the resource directory. You can specify up to 20 member IDs. Note
To view the member IDs, go to the Overview page in the Resource Management console. For more information, see View the detailed information of a member.
| ["151266687691****","141261387191****"] | |
Capabilities | array | No | The option for the stack group. You can specify up to one option. | |
string | No | The option for the stack group. Valid value: ExpandModules. A value of ExpandModules specifies to expand modules within the current account. Note
| ExpandModules |
The description of the stack group.
The description must be 1 to 256 characters in length.
Response parameters
The IDs of the accounts within which you want to use self-managed permissions to deploy stacks. You can specify a maximum of 20 account IDs.
Examples
Sample success responses
JSON
format
{
"RequestId": "14A07460-EBE7-47CA-9757-12CC4761D47A",
"OperationId": "6da106ca-1784-4a6f-a7e1-e723863d****"
}
Error codes
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|---|---|
2024-01-11 | The internal configuration of the API is changed, but the call is not affected | View Change Details |
2023-05-10 | The request parameters of the API has changed | View Change Details |