@alicloud/appstream-center20210901 5.8.0 → 5.9.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (111) hide show
  1. package/dist/client.d.ts +468 -22
  2. package/dist/client.js +773 -22
  3. package/dist/client.js.map +1 -1
  4. package/dist/models/ListAppsByAppInstanceGroupIdRequest.d.ts +61 -0
  5. package/dist/models/ListAppsByAppInstanceGroupIdRequest.js +64 -0
  6. package/dist/models/ListAppsByAppInstanceGroupIdRequest.js.map +1 -0
  7. package/dist/models/ListAppsByAppInstanceGroupIdResponse.d.ts +19 -0
  8. package/dist/models/ListAppsByAppInstanceGroupIdResponse.js +69 -0
  9. package/dist/models/ListAppsByAppInstanceGroupIdResponse.js.map +1 -0
  10. package/dist/models/ListAppsByAppInstanceGroupIdResponseBody.d.ts +110 -0
  11. package/dist/models/ListAppsByAppInstanceGroupIdResponseBody.js +98 -0
  12. package/dist/models/ListAppsByAppInstanceGroupIdResponseBody.js.map +1 -0
  13. package/dist/models/ListAuthorizedAppsByUserRequest.d.ts +89 -0
  14. package/dist/models/ListAuthorizedAppsByUserRequest.js +72 -0
  15. package/dist/models/ListAuthorizedAppsByUserRequest.js.map +1 -0
  16. package/dist/models/ListAuthorizedAppsByUserResponse.d.ts +19 -0
  17. package/dist/models/ListAuthorizedAppsByUserResponse.js +69 -0
  18. package/dist/models/ListAuthorizedAppsByUserResponse.js.map +1 -0
  19. package/dist/models/ListAuthorizedAppsByUserResponseBody.d.ts +126 -0
  20. package/dist/models/ListAuthorizedAppsByUserResponseBody.js +102 -0
  21. package/dist/models/ListAuthorizedAppsByUserResponseBody.js.map +1 -0
  22. package/dist/models/ListAuthorizedUsersRequest.d.ts +29 -16
  23. package/dist/models/ListAuthorizedUsersRequest.js.map +1 -1
  24. package/dist/models/ListAuthorizedUsersResponseBody.d.ts +29 -24
  25. package/dist/models/ListAuthorizedUsersResponseBody.js.map +1 -1
  26. package/dist/models/ListPublishedAppInstanceGroupRequest.d.ts +100 -0
  27. package/dist/models/ListPublishedAppInstanceGroupRequest.js +72 -0
  28. package/dist/models/ListPublishedAppInstanceGroupRequest.js.map +1 -0
  29. package/dist/models/ListPublishedAppInstanceGroupResponse.d.ts +19 -0
  30. package/dist/models/ListPublishedAppInstanceGroupResponse.js +69 -0
  31. package/dist/models/ListPublishedAppInstanceGroupResponse.js.map +1 -0
  32. package/dist/models/ListPublishedAppInstanceGroupResponseBody.d.ts +185 -0
  33. package/dist/models/ListPublishedAppInstanceGroupResponseBody.js +134 -0
  34. package/dist/models/ListPublishedAppInstanceGroupResponseBody.js.map +1 -0
  35. package/dist/models/ListPublishedAppsRequest.d.ts +96 -0
  36. package/dist/models/ListPublishedAppsRequest.js +72 -0
  37. package/dist/models/ListPublishedAppsRequest.js.map +1 -0
  38. package/dist/models/ListPublishedAppsResponse.d.ts +19 -0
  39. package/dist/models/ListPublishedAppsResponse.js +69 -0
  40. package/dist/models/ListPublishedAppsResponse.js.map +1 -0
  41. package/dist/models/ListPublishedAppsResponseBody.d.ts +126 -0
  42. package/dist/models/ListPublishedAppsResponseBody.js +102 -0
  43. package/dist/models/ListPublishedAppsResponseBody.js.map +1 -0
  44. package/dist/models/ListTagResourcesRequest.d.ts +97 -0
  45. package/dist/models/ListTagResourcesRequest.js +93 -0
  46. package/dist/models/ListTagResourcesRequest.js.map +1 -0
  47. package/dist/models/ListTagResourcesResponse.d.ts +19 -0
  48. package/dist/models/ListTagResourcesResponse.js +69 -0
  49. package/dist/models/ListTagResourcesResponse.js.map +1 -0
  50. package/dist/models/ListTagResourcesResponseBody.d.ts +88 -0
  51. package/dist/models/ListTagResourcesResponseBody.js +92 -0
  52. package/dist/models/ListTagResourcesResponseBody.js.map +1 -0
  53. package/dist/models/ListZonesRequest.d.ts +62 -0
  54. package/dist/models/ListZonesRequest.js +62 -0
  55. package/dist/models/ListZonesRequest.js.map +1 -0
  56. package/dist/models/ListZonesResponse.d.ts +19 -0
  57. package/dist/models/ListZonesResponse.js +69 -0
  58. package/dist/models/ListZonesResponse.js.map +1 -0
  59. package/dist/models/ListZonesResponseBody.d.ts +43 -0
  60. package/dist/models/ListZonesResponseBody.js +85 -0
  61. package/dist/models/ListZonesResponseBody.js.map +1 -0
  62. package/dist/models/TagResourcesRequest.d.ts +103 -0
  63. package/dist/models/TagResourcesRequest.js +91 -0
  64. package/dist/models/TagResourcesRequest.js.map +1 -0
  65. package/dist/models/TagResourcesResponse.d.ts +19 -0
  66. package/dist/models/TagResourcesResponse.js +69 -0
  67. package/dist/models/TagResourcesResponse.js.map +1 -0
  68. package/dist/models/TagResourcesResponseBody.d.ts +21 -0
  69. package/dist/models/TagResourcesResponseBody.js +58 -0
  70. package/dist/models/TagResourcesResponseBody.js.map +1 -0
  71. package/dist/models/UntagResourcesRequest.d.ts +78 -0
  72. package/dist/models/UntagResourcesRequest.js +72 -0
  73. package/dist/models/UntagResourcesRequest.js.map +1 -0
  74. package/dist/models/UntagResourcesResponse.d.ts +19 -0
  75. package/dist/models/UntagResourcesResponse.js +69 -0
  76. package/dist/models/UntagResourcesResponse.js.map +1 -0
  77. package/dist/models/UntagResourcesResponseBody.d.ts +21 -0
  78. package/dist/models/UntagResourcesResponseBody.js +58 -0
  79. package/dist/models/UntagResourcesResponseBody.js.map +1 -0
  80. package/dist/models/model.d.ts +33 -0
  81. package/dist/models/model.js +74 -8
  82. package/dist/models/model.js.map +1 -1
  83. package/package.json +1 -1
  84. package/src/client.ts +837 -22
  85. package/src/models/ListAppsByAppInstanceGroupIdRequest.ts +80 -0
  86. package/src/models/ListAppsByAppInstanceGroupIdResponse.ts +40 -0
  87. package/src/models/ListAppsByAppInstanceGroupIdResponseBody.ts +154 -0
  88. package/src/models/ListAuthorizedAppsByUserRequest.ts +116 -0
  89. package/src/models/ListAuthorizedAppsByUserResponse.ts +40 -0
  90. package/src/models/ListAuthorizedAppsByUserResponseBody.ts +174 -0
  91. package/src/models/ListAuthorizedUsersRequest.ts +29 -16
  92. package/src/models/ListAuthorizedUsersResponseBody.ts +29 -24
  93. package/src/models/ListPublishedAppInstanceGroupRequest.ts +127 -0
  94. package/src/models/ListPublishedAppInstanceGroupResponse.ts +40 -0
  95. package/src/models/ListPublishedAppInstanceGroupResponseBody.ts +256 -0
  96. package/src/models/ListPublishedAppsRequest.ts +123 -0
  97. package/src/models/ListPublishedAppsResponse.ts +40 -0
  98. package/src/models/ListPublishedAppsResponseBody.ts +174 -0
  99. package/src/models/ListTagResourcesRequest.ts +136 -0
  100. package/src/models/ListTagResourcesResponse.ts +40 -0
  101. package/src/models/ListTagResourcesResponseBody.ts +126 -0
  102. package/src/models/ListZonesRequest.ts +79 -0
  103. package/src/models/ListZonesResponse.ts +40 -0
  104. package/src/models/ListZonesResponseBody.ts +74 -0
  105. package/src/models/TagResourcesRequest.ts +140 -0
  106. package/src/models/TagResourcesResponse.ts +40 -0
  107. package/src/models/TagResourcesResponseBody.ts +34 -0
  108. package/src/models/UntagResourcesRequest.ts +105 -0
  109. package/src/models/UntagResourcesResponse.ts +40 -0
  110. package/src/models/UntagResourcesResponseBody.ts +34 -0
  111. package/src/models/model.ts +33 -0
package/dist/client.d.ts CHANGED
@@ -848,6 +848,51 @@ export default class Client extends OpenApi {
848
848
  * @returns ListAppInstancesResponse
849
849
  */
850
850
  listAppInstances(request: $_model.ListAppInstancesRequest): Promise<$_model.ListAppInstancesResponse>;
851
+ /**
852
+ * Queries the deployed applications in the image used by a specified delivery group with paging and returns the number of users with per-application authorization for each application.
853
+ *
854
+ * @remarks
855
+ * ## Operation description
856
+ * This operation returns the list of deployed applications in the application image used by a specified delivery group, including the application ID, name, version, icon, and the number of users currently **authorized by application** for each application (AuthorizedUserCount).
857
+ * The returned AppId is the input for per-application authorization: when you call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation to add or remove authorized users for a specified application in a delivery group, pass in the AppId returned by this operation.
858
+ * ## Before you begin
859
+ * - The delivery group is created, and **ProductType matches the product type of the delivery group**. If the delivery group does not exist or the product type does not match, the error code `InvalidAppInstanceGroup.NotFound` is returned.
860
+ * ## Parameter description
861
+ * - **AppInstanceGroupId is required**. This parameter is marked as optional in the parameter table, but the error code `InvalidParameter.AppInstanceGroupId` is returned if it is not specified.
862
+ * - PageNumber starts from 1. Valid values of PageSize: 1 to 100. If the values are invalid, the error codes `InvalidParameter.PageNumber` and `InvalidParameter.PageSize` are returned respectively.
863
+ * - If no applications are deployed in the delivery group image, the operation returns normally: Apps is an empty list and TotalCount is 0.
864
+ * ## Call sequence
865
+ * 1. Call the [ListAppInstanceGroup](~~ListAppInstanceGroup~~) operation to obtain the delivery group ID (AppInstanceGroupId).
866
+ * 2. Call this operation to obtain the list of deployed applications in the delivery group and the AppId of each application.
867
+ * 3. To authorize by application, call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation with the returned AppId.
868
+ *
869
+ * @param request - ListAppsByAppInstanceGroupIdRequest
870
+ * @param runtime - runtime options for this request RuntimeOptions
871
+ * @returns ListAppsByAppInstanceGroupIdResponse
872
+ */
873
+ listAppsByAppInstanceGroupIdWithOptions(request: $_model.ListAppsByAppInstanceGroupIdRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListAppsByAppInstanceGroupIdResponse>;
874
+ /**
875
+ * Queries the deployed applications in the image used by a specified delivery group with paging and returns the number of users with per-application authorization for each application.
876
+ *
877
+ * @remarks
878
+ * ## Operation description
879
+ * This operation returns the list of deployed applications in the application image used by a specified delivery group, including the application ID, name, version, icon, and the number of users currently **authorized by application** for each application (AuthorizedUserCount).
880
+ * The returned AppId is the input for per-application authorization: when you call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation to add or remove authorized users for a specified application in a delivery group, pass in the AppId returned by this operation.
881
+ * ## Before you begin
882
+ * - The delivery group is created, and **ProductType matches the product type of the delivery group**. If the delivery group does not exist or the product type does not match, the error code `InvalidAppInstanceGroup.NotFound` is returned.
883
+ * ## Parameter description
884
+ * - **AppInstanceGroupId is required**. This parameter is marked as optional in the parameter table, but the error code `InvalidParameter.AppInstanceGroupId` is returned if it is not specified.
885
+ * - PageNumber starts from 1. Valid values of PageSize: 1 to 100. If the values are invalid, the error codes `InvalidParameter.PageNumber` and `InvalidParameter.PageSize` are returned respectively.
886
+ * - If no applications are deployed in the delivery group image, the operation returns normally: Apps is an empty list and TotalCount is 0.
887
+ * ## Call sequence
888
+ * 1. Call the [ListAppInstanceGroup](~~ListAppInstanceGroup~~) operation to obtain the delivery group ID (AppInstanceGroupId).
889
+ * 2. Call this operation to obtain the list of deployed applications in the delivery group and the AppId of each application.
890
+ * 3. To authorize by application, call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation with the returned AppId.
891
+ *
892
+ * @param request - ListAppsByAppInstanceGroupIdRequest
893
+ * @returns ListAppsByAppInstanceGroupIdResponse
894
+ */
895
+ listAppsByAppInstanceGroupId(request: $_model.ListAppsByAppInstanceGroupIdRequest): Promise<$_model.ListAppsByAppInstanceGroupIdResponse>;
851
896
  /**
852
897
  * Queries the delivery groups for which a specified user has obtained access permissions through delivery group-level authorization by paging, with support for fuzzy filtering by delivery group ID, delivery group name, application ID, or application name.
853
898
  *
@@ -901,6 +946,53 @@ export default class Client extends OpenApi {
901
946
  * @returns ListAuthorizedAppInstanceGroupByUserResponse
902
947
  */
903
948
  listAuthorizedAppInstanceGroupByUser(request: $_model.ListAuthorizedAppInstanceGroupByUserRequest): Promise<$_model.ListAuthorizedAppInstanceGroupByUserResponse>;
949
+ /**
950
+ * Queries the applications for which a specified user has obtained access permissions through per-application authorization by paging. You can filter results by delivery group ID, delivery group name, application ID, or application name using fuzzy match.
951
+ *
952
+ * @remarks
953
+ * ## Operation description
954
+ * This operation queries the applications that a specified user is authorized to access at the application granularity. **Only records authorized at the application level are returned** (for example, authorizations completed through the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation). Authorizations granted to an entire delivery group through the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) operation are not included in the response.
955
+ * The results are deduplicated by the combination of delivery group and application. Each record corresponds to one application within one delivery group.
956
+ * ## Before you begin
957
+ * - The user must already exist under the current account. If the user does not exist, the error code `User.NotFound` is returned. Call the [DescribeUsers](https://help.aliyun.com/document_detail/436936.html) operation to obtain the username.
958
+ * - The delivery group that contains the application must already be created, and the application must have been authorized to the user at the application level. If no per-application authorization has been performed, an empty application list is returned.
959
+ * ## Parameter description
960
+ * - **`EndUserId` and `ProductType` are required.** Set `ProductType` to `CloudApp`, which indicates WUYING Cloud Application.
961
+ * - `AppInstanceGroupId`, `AppId`, `AppInstanceGroupName`, and `AppName` are optional filter conditions. All of them use fuzzy match and can be combined in any way. If all are omitted, all per-application authorization records for the user are returned.
962
+ * - Use `PageNumber` and `PageSize` for paging. `PageNumber` starts from 1, and `PageSize` ranges from 1 to 100. Use the returned `TotalCount` to determine whether to continue querying.
963
+ * ## Call sequence
964
+ * 1. Call the [ListAppInstanceGroup](https://help.aliyun.com/document_detail/428506.html) or [GetAppInstanceGroup](https://help.aliyun.com/document_detail/600836.html) operation to obtain the delivery group ID (AppInstanceGroupId) and the application IDs of deployed applications within the delivery group (AppId in the Apps list).
965
+ * 2. Call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation to authorize the application to the target user.
966
+ * 3. Call this operation to query the applications that the user is authorized to access.
967
+ *
968
+ * @param request - ListAuthorizedAppsByUserRequest
969
+ * @param runtime - runtime options for this request RuntimeOptions
970
+ * @returns ListAuthorizedAppsByUserResponse
971
+ */
972
+ listAuthorizedAppsByUserWithOptions(request: $_model.ListAuthorizedAppsByUserRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListAuthorizedAppsByUserResponse>;
973
+ /**
974
+ * Queries the applications for which a specified user has obtained access permissions through per-application authorization by paging. You can filter results by delivery group ID, delivery group name, application ID, or application name using fuzzy match.
975
+ *
976
+ * @remarks
977
+ * ## Operation description
978
+ * This operation queries the applications that a specified user is authorized to access at the application granularity. **Only records authorized at the application level are returned** (for example, authorizations completed through the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation). Authorizations granted to an entire delivery group through the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) operation are not included in the response.
979
+ * The results are deduplicated by the combination of delivery group and application. Each record corresponds to one application within one delivery group.
980
+ * ## Before you begin
981
+ * - The user must already exist under the current account. If the user does not exist, the error code `User.NotFound` is returned. Call the [DescribeUsers](https://help.aliyun.com/document_detail/436936.html) operation to obtain the username.
982
+ * - The delivery group that contains the application must already be created, and the application must have been authorized to the user at the application level. If no per-application authorization has been performed, an empty application list is returned.
983
+ * ## Parameter description
984
+ * - **`EndUserId` and `ProductType` are required.** Set `ProductType` to `CloudApp`, which indicates WUYING Cloud Application.
985
+ * - `AppInstanceGroupId`, `AppId`, `AppInstanceGroupName`, and `AppName` are optional filter conditions. All of them use fuzzy match and can be combined in any way. If all are omitted, all per-application authorization records for the user are returned.
986
+ * - Use `PageNumber` and `PageSize` for paging. `PageNumber` starts from 1, and `PageSize` ranges from 1 to 100. Use the returned `TotalCount` to determine whether to continue querying.
987
+ * ## Call sequence
988
+ * 1. Call the [ListAppInstanceGroup](https://help.aliyun.com/document_detail/428506.html) or [GetAppInstanceGroup](https://help.aliyun.com/document_detail/600836.html) operation to obtain the delivery group ID (AppInstanceGroupId) and the application IDs of deployed applications within the delivery group (AppId in the Apps list).
989
+ * 2. Call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation to authorize the application to the target user.
990
+ * 3. Call this operation to query the applications that the user is authorized to access.
991
+ *
992
+ * @param request - ListAuthorizedAppsByUserRequest
993
+ * @returns ListAuthorizedAppsByUserResponse
994
+ */
995
+ listAuthorizedAppsByUser(request: $_model.ListAuthorizedAppsByUserRequest): Promise<$_model.ListAuthorizedAppsByUserResponse>;
904
996
  /**
905
997
  * Queries the list of user groups authorized by a specified delivery group.
906
998
  *
@@ -917,20 +1009,41 @@ export default class Client extends OpenApi {
917
1009
  */
918
1010
  listAuthorizedUserGroups(request: $_model.ListAuthorizedUserGroupsRequest): Promise<$_model.ListAuthorizedUserGroupsResponse>;
919
1011
  /**
920
- * Queries authorized users of a cloud browser group with paging.
1012
+ * Queries the list of authorized users for a specified delivery group or delivery group set by using paging. Supports exact or fuzzy filtering by username.
921
1013
  *
922
1014
  * @remarks
1015
+ * ## Operation description
1016
+ * This operation queries the currently authorized users of a specified delivery group (AppInstanceGroupId) or delivery group set (AppInstanceGroupSetId). It returns each user\\"s username, account type, email address, phone number, and the authorization mode of the associated delivery group.
1017
+ * - This operation returns **authorization relationships** and does not indicate whether users are currently online or have established connections.
1018
+ * - In the Cloud Browser product, a delivery group corresponds to a cloud browser group, and a delivery group ID corresponds to a browser group ID.
1019
+ * The scope of results depends on the authorization mode of the delivery group (response parameter AuthMode):
1020
+ * - When the authorization mode is `App` (application-level authorization) or `AppInstanceGroup` (delivery group-level authorization): Returns users authorized through the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) operation at the delivery group level, as well as users authorized through the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation at the application level. If AppId is specified, only users **authorized for that specific application** are returned.
1021
+ * - When the authorization mode is `Session` (session-level authorization): Returns users who have been granted persistent sessions. The AppInstancePersistentIds field lists all persistent session IDs granted to each user. If AppInstancePersistentId is specified, only users granted that session are returned.
1022
+ * - When querying by delivery group set: Returns users authorized for the set. The response parameter AppInstanceGroupId is the primary delivery group ID of the set, and AppInstanceGroupSetId is the queried set ID.
1023
+ * When querying by delivery group, results are sorted in descending order by authorization time, with the most recently authorized users listed first.
923
1024
  * ## Before you begin
924
- * - The target cloud browser group or delivery group set must be created, belong to the current account, and match the specified `ProductType`.
925
- * - When querying authorized users of cloud browsers, set `ProductType` to `CloudBrowser`.
926
- * - **Specify either `AppInstanceGroupId` or `AppInstanceGroupSetId`, but not both.**
927
- * ## Query notes
928
- * - This operation returns authorization relationships and does not indicate whether users are currently online or sessions are connected.
929
- * - When querying by set, omit `AppId` and `AppInstancePersistentId`.
930
- * - Use `PageNumber` and `PageSize` for pagination and check `TotalCount` to determine whether to continue querying.
931
- * ## Example notes
932
- * The examples show how to set the fields. Replace resource identifiers with actual values in your account.
933
- * An example value of `-` indicates that the parameter does not need to be set. Omit the corresponding parameter when calling the operation. Do not pass the character `-`.
1025
+ * - The target delivery group or delivery group set must be created, belong to the current account, and match the specified ProductType. Otherwise, a resource-not-found error code is returned.
1026
+ * - Users must have been authorized through the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) or [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation. If no users have been authorized, the operation returns normally with an empty Users list and TotalCount of 0.
1027
+ * ## Parameter description
1028
+ * - **ProductType, PageNumber, and PageSize are required**. If ProductType has an invalid value, the error code `ProductTypeInvalid` is returned.
1029
+ * - **Exactly one of AppInstanceGroupId and AppInstanceGroupSetId must be specified**. If both or neither are specified, the error code `InvalidParameter.AppInstanceGroupId/AppInstanceGroupSetId` is returned.
1030
+ * - **AppId and AppInstancePersistentId are not supported when querying by delivery group set**. If specified, the error codes `InvalidParameter.AppId` and `InvalidParameter.AppInstancePersistentId` are returned respectively.
1031
+ * - EndUserId performs **exact matching** by username. UserIdFuzzy performs **fuzzy matching** by username (a hit occurs if the username contains the keyword). Both can be specified simultaneously, in which case both conditions must be met.
1032
+ * - PageNumber starts from 1. Valid values of PageSize: 1 to 100.
1033
+ * - When the authorization mode is `App` or `AppInstanceGroup`, TotalCount is the number of **authorization records** that match the conditions. If the same user has multiple authorization records (for example, authorized for multiple applications), the records are merged into a single user entry in Users. Therefore, the number of users returned on the current page may be less than PageSize. Use TotalCount to determine whether to continue paging. When the authorization mode is `Session`, TotalCount is the deduplicated user count.
1034
+ * ## Call sequence
1035
+ * 1. Call the [ListAppInstanceGroup](~~ListAppInstanceGroup~~) operation to obtain the delivery group ID. For cloud browser groups, call the [ListBrowserInstanceGroup](~~ListBrowserInstanceGroup~~) operation.
1036
+ * 2. Call the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) operation to authorize at the delivery group level, or call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation to authorize at the application level.
1037
+ * 3. Call this operation to query authorized users. To remove authorization, pass the returned EndUserId values to the UnAuthorizeUserIds parameter of the authorization operations mentioned above.
1038
+ * ## Error codes
1039
+ * - `ProductTypeInvalid`: The value of ProductType is invalid.
1040
+ * - `InvalidParameter.AppInstanceGroupId/AppInstanceGroupSetId`: Both AppInstanceGroupId and AppInstanceGroupSetId are specified, or neither is specified.
1041
+ * - `InvalidParameter.AppId`: AppId is specified when querying by delivery group set.
1042
+ * - `InvalidParameter.AppInstancePersistentId`: AppInstancePersistentId is specified when querying by delivery group set.
1043
+ * - `InvalidAppInstanceGroupSpecItem.NotFound`: The delivery group does not exist, does not belong to the current account, or the product type does not match.
1044
+ * - `InvalidBrowserInstanceGroup.NotFound`: When ProductType is `CloudBrowser`, the cloud browser group does not exist, does not belong to the current account, or the product type does not match.
1045
+ * - `InvalidAppInstanceGroupSet.NotFound`: The delivery group set does not exist, does not belong to the current account, the product type does not match, or the set does not have an available primary delivery group.
1046
+ * - `InvalidAppInstanceGroupSet.ActivationFailed`: The delivery group set is not in an available state.
934
1047
  *
935
1048
  * @param request - ListAuthorizedUsersRequest
936
1049
  * @param runtime - runtime options for this request RuntimeOptions
@@ -938,20 +1051,41 @@ export default class Client extends OpenApi {
938
1051
  */
939
1052
  listAuthorizedUsersWithOptions(request: $_model.ListAuthorizedUsersRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListAuthorizedUsersResponse>;
940
1053
  /**
941
- * Queries authorized users of a cloud browser group with paging.
1054
+ * Queries the list of authorized users for a specified delivery group or delivery group set by using paging. Supports exact or fuzzy filtering by username.
942
1055
  *
943
1056
  * @remarks
1057
+ * ## Operation description
1058
+ * This operation queries the currently authorized users of a specified delivery group (AppInstanceGroupId) or delivery group set (AppInstanceGroupSetId). It returns each user\\"s username, account type, email address, phone number, and the authorization mode of the associated delivery group.
1059
+ * - This operation returns **authorization relationships** and does not indicate whether users are currently online or have established connections.
1060
+ * - In the Cloud Browser product, a delivery group corresponds to a cloud browser group, and a delivery group ID corresponds to a browser group ID.
1061
+ * The scope of results depends on the authorization mode of the delivery group (response parameter AuthMode):
1062
+ * - When the authorization mode is `App` (application-level authorization) or `AppInstanceGroup` (delivery group-level authorization): Returns users authorized through the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) operation at the delivery group level, as well as users authorized through the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation at the application level. If AppId is specified, only users **authorized for that specific application** are returned.
1063
+ * - When the authorization mode is `Session` (session-level authorization): Returns users who have been granted persistent sessions. The AppInstancePersistentIds field lists all persistent session IDs granted to each user. If AppInstancePersistentId is specified, only users granted that session are returned.
1064
+ * - When querying by delivery group set: Returns users authorized for the set. The response parameter AppInstanceGroupId is the primary delivery group ID of the set, and AppInstanceGroupSetId is the queried set ID.
1065
+ * When querying by delivery group, results are sorted in descending order by authorization time, with the most recently authorized users listed first.
944
1066
  * ## Before you begin
945
- * - The target cloud browser group or delivery group set must be created, belong to the current account, and match the specified `ProductType`.
946
- * - When querying authorized users of cloud browsers, set `ProductType` to `CloudBrowser`.
947
- * - **Specify either `AppInstanceGroupId` or `AppInstanceGroupSetId`, but not both.**
948
- * ## Query notes
949
- * - This operation returns authorization relationships and does not indicate whether users are currently online or sessions are connected.
950
- * - When querying by set, omit `AppId` and `AppInstancePersistentId`.
951
- * - Use `PageNumber` and `PageSize` for pagination and check `TotalCount` to determine whether to continue querying.
952
- * ## Example notes
953
- * The examples show how to set the fields. Replace resource identifiers with actual values in your account.
954
- * An example value of `-` indicates that the parameter does not need to be set. Omit the corresponding parameter when calling the operation. Do not pass the character `-`.
1067
+ * - The target delivery group or delivery group set must be created, belong to the current account, and match the specified ProductType. Otherwise, a resource-not-found error code is returned.
1068
+ * - Users must have been authorized through the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) or [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation. If no users have been authorized, the operation returns normally with an empty Users list and TotalCount of 0.
1069
+ * ## Parameter description
1070
+ * - **ProductType, PageNumber, and PageSize are required**. If ProductType has an invalid value, the error code `ProductTypeInvalid` is returned.
1071
+ * - **Exactly one of AppInstanceGroupId and AppInstanceGroupSetId must be specified**. If both or neither are specified, the error code `InvalidParameter.AppInstanceGroupId/AppInstanceGroupSetId` is returned.
1072
+ * - **AppId and AppInstancePersistentId are not supported when querying by delivery group set**. If specified, the error codes `InvalidParameter.AppId` and `InvalidParameter.AppInstancePersistentId` are returned respectively.
1073
+ * - EndUserId performs **exact matching** by username. UserIdFuzzy performs **fuzzy matching** by username (a hit occurs if the username contains the keyword). Both can be specified simultaneously, in which case both conditions must be met.
1074
+ * - PageNumber starts from 1. Valid values of PageSize: 1 to 100.
1075
+ * - When the authorization mode is `App` or `AppInstanceGroup`, TotalCount is the number of **authorization records** that match the conditions. If the same user has multiple authorization records (for example, authorized for multiple applications), the records are merged into a single user entry in Users. Therefore, the number of users returned on the current page may be less than PageSize. Use TotalCount to determine whether to continue paging. When the authorization mode is `Session`, TotalCount is the deduplicated user count.
1076
+ * ## Call sequence
1077
+ * 1. Call the [ListAppInstanceGroup](~~ListAppInstanceGroup~~) operation to obtain the delivery group ID. For cloud browser groups, call the [ListBrowserInstanceGroup](~~ListBrowserInstanceGroup~~) operation.
1078
+ * 2. Call the [AuthorizeInstanceGroup](~~AuthorizeInstanceGroup~~) operation to authorize at the delivery group level, or call the [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~) operation to authorize at the application level.
1079
+ * 3. Call this operation to query authorized users. To remove authorization, pass the returned EndUserId values to the UnAuthorizeUserIds parameter of the authorization operations mentioned above.
1080
+ * ## Error codes
1081
+ * - `ProductTypeInvalid`: The value of ProductType is invalid.
1082
+ * - `InvalidParameter.AppInstanceGroupId/AppInstanceGroupSetId`: Both AppInstanceGroupId and AppInstanceGroupSetId are specified, or neither is specified.
1083
+ * - `InvalidParameter.AppId`: AppId is specified when querying by delivery group set.
1084
+ * - `InvalidParameter.AppInstancePersistentId`: AppInstancePersistentId is specified when querying by delivery group set.
1085
+ * - `InvalidAppInstanceGroupSpecItem.NotFound`: The delivery group does not exist, does not belong to the current account, or the product type does not match.
1086
+ * - `InvalidBrowserInstanceGroup.NotFound`: When ProductType is `CloudBrowser`, the cloud browser group does not exist, does not belong to the current account, or the product type does not match.
1087
+ * - `InvalidAppInstanceGroupSet.NotFound`: The delivery group set does not exist, does not belong to the current account, the product type does not match, or the set does not have an available primary delivery group.
1088
+ * - `InvalidAppInstanceGroupSet.ActivationFailed`: The delivery group set is not in an available state.
955
1089
  *
956
1090
  * @param request - ListAuthorizedUsersRequest
957
1091
  * @returns ListAuthorizedUsersResponse
@@ -1206,6 +1340,102 @@ export default class Client extends OpenApi {
1206
1340
  * @returns ListPersistentAppInstancesResponse
1207
1341
  */
1208
1342
  listPersistentAppInstances(request: $_model.ListPersistentAppInstancesRequest): Promise<$_model.ListPersistentAppInstancesResponse>;
1343
+ /**
1344
+ * Queries published delivery groups and their application information for a specified product type under the current Alibaba Cloud account by using paging. Supports filtering by delivery group, application, and user authorization status.
1345
+ *
1346
+ * @remarks
1347
+ * ## Before you begin
1348
+ * When calling this operation with a RAM user or STS credential, the `appstreaming:ListPublishedAppInstanceGroup` permission is required.
1349
+ * A delivery group must be in the published state and have deployed applications in its image to appear in the query results. This operation only queries information. It does not create delivery groups, assign users, or grant application access permissions.
1350
+ * ## Query and pagination
1351
+ * - **You must explicitly pass in `ProductType`, `PageNumber`, and `PageSize`.** Page numbers start from `1`, and the page size ranges from `1` to `100`.
1352
+ * - `AppInstanceGroupId`, `AppInstanceGroupName`, `AppId`, and `AppName` all support substring matching. You can pass them individually or in combination. When multiple conditions are specified, all conditions must be met simultaneously. When both `AppId` and `AppName` are specified, the same application must satisfy both conditions.
1353
+ * - If an optional filter parameter is not specified or is set to an empty string, that condition is not applied. Query results are sorted by delivery group creation time from newest to oldest. A delivery group is not returned multiple times even if it contains multiple matching applications.
1354
+ * - `ExcludeUserId` excludes delivery groups in which all applications have been directly authorized to the specified user. It cannot be used to determine whether the user has no access permissions at all.
1355
+ * - `AppId` and `AppName` only filter delivery groups. **They do not restrict the returned `Apps` list to only the matched applications.**
1356
+ * ## Invoke sequence
1357
+ * 1. Invoke a query with `PageNumber=1` and the desired `PageSize`. For WUYING Cloud Application common scenarios, use `ProductType=CloudApp`.
1358
+ * 2. Read `AppInstanceGroupModels`. To retrieve the next page, keep the product type and filter conditions unchanged and increment `PageNumber`. If no delivery groups match, the total count is `0` and the list is empty. If the page number exceeds the result range, the list may also be empty, but the total count still represents the total number of matching delivery groups.
1359
+ * 3. To retrieve details of a single delivery group, pass the full `AppInstanceGroupId` from the response and the same `ProductType` to [GetAppInstanceGroup](~~GetAppInstanceGroup~~).
1360
+ * The masked identifiers in the examples are for format demonstration purposes. Replace them with your actual identifiers when invoking the operation.
1361
+ *
1362
+ * @param request - ListPublishedAppInstanceGroupRequest
1363
+ * @param runtime - runtime options for this request RuntimeOptions
1364
+ * @returns ListPublishedAppInstanceGroupResponse
1365
+ */
1366
+ listPublishedAppInstanceGroupWithOptions(request: $_model.ListPublishedAppInstanceGroupRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListPublishedAppInstanceGroupResponse>;
1367
+ /**
1368
+ * Queries published delivery groups and their application information for a specified product type under the current Alibaba Cloud account by using paging. Supports filtering by delivery group, application, and user authorization status.
1369
+ *
1370
+ * @remarks
1371
+ * ## Before you begin
1372
+ * When calling this operation with a RAM user or STS credential, the `appstreaming:ListPublishedAppInstanceGroup` permission is required.
1373
+ * A delivery group must be in the published state and have deployed applications in its image to appear in the query results. This operation only queries information. It does not create delivery groups, assign users, or grant application access permissions.
1374
+ * ## Query and pagination
1375
+ * - **You must explicitly pass in `ProductType`, `PageNumber`, and `PageSize`.** Page numbers start from `1`, and the page size ranges from `1` to `100`.
1376
+ * - `AppInstanceGroupId`, `AppInstanceGroupName`, `AppId`, and `AppName` all support substring matching. You can pass them individually or in combination. When multiple conditions are specified, all conditions must be met simultaneously. When both `AppId` and `AppName` are specified, the same application must satisfy both conditions.
1377
+ * - If an optional filter parameter is not specified or is set to an empty string, that condition is not applied. Query results are sorted by delivery group creation time from newest to oldest. A delivery group is not returned multiple times even if it contains multiple matching applications.
1378
+ * - `ExcludeUserId` excludes delivery groups in which all applications have been directly authorized to the specified user. It cannot be used to determine whether the user has no access permissions at all.
1379
+ * - `AppId` and `AppName` only filter delivery groups. **They do not restrict the returned `Apps` list to only the matched applications.**
1380
+ * ## Invoke sequence
1381
+ * 1. Invoke a query with `PageNumber=1` and the desired `PageSize`. For WUYING Cloud Application common scenarios, use `ProductType=CloudApp`.
1382
+ * 2. Read `AppInstanceGroupModels`. To retrieve the next page, keep the product type and filter conditions unchanged and increment `PageNumber`. If no delivery groups match, the total count is `0` and the list is empty. If the page number exceeds the result range, the list may also be empty, but the total count still represents the total number of matching delivery groups.
1383
+ * 3. To retrieve details of a single delivery group, pass the full `AppInstanceGroupId` from the response and the same `ProductType` to [GetAppInstanceGroup](~~GetAppInstanceGroup~~).
1384
+ * The masked identifiers in the examples are for format demonstration purposes. Replace them with your actual identifiers when invoking the operation.
1385
+ *
1386
+ * @param request - ListPublishedAppInstanceGroupRequest
1387
+ * @returns ListPublishedAppInstanceGroupResponse
1388
+ */
1389
+ listPublishedAppInstanceGroup(request: $_model.ListPublishedAppInstanceGroupRequest): Promise<$_model.ListPublishedAppInstanceGroupResponse>;
1390
+ /**
1391
+ * Queries deployed applications in published delivery groups under the current Alibaba Cloud account for a specified product type by paging, and returns each application along with its delivery group and the number of authorized users by application. Supports filtering by delivery group, application, and user authorization status.
1392
+ *
1393
+ * @remarks
1394
+ * ## Before you begin
1395
+ * When you call this operation by using a RAM user or Security Token Service (STS) credential, you must have the `appstreaming:ListPublishedApps` permission.
1396
+ * Only delivery groups in the published state whose images contain deployed applications are included in the query results. This operation only queries information. It does not create delivery groups or grant or revoke application access permissions.
1397
+ * ## Response granularity
1398
+ * Results are returned on a per-delivery-group-plus-application basis. If the same application is deployed in multiple published delivery groups, a separate record is returned for each combination. `TotalCount` also reflects the number of such combinations. The list is sorted by the creation time of the delivery group in descending order.
1399
+ * ## Query and pagination
1400
+ * - **You must explicitly specify `ProductType`, `PageNumber`, and `PageSize`.** Page numbers start from `1`, and the page size ranges from `1` to `100`. Invalid values return error codes `InvalidParameter.PageNumber` and `InvalidParameter.PageSize`, respectively.
1401
+ * - `AppInstanceGroupId`, `AppInstanceGroupName`, `AppId`, and `AppName` all support substring matching. You can specify them individually or in combination. When multiple conditions are specified, all conditions must be met.
1402
+ * - If an optional filter parameter is not specified or is set to an empty string, filtering is not applied for that condition.
1403
+ * - `ExcludeUserId` excludes applications that have been authorized to the specified user by application, which helps you find applications that can still be authorized to that user. **Access permissions granted through delivery-group-level authorization or user groups are not evaluated by this condition.**
1404
+ * ## Invocation sequence
1405
+ * 1. Initiate a query with `PageNumber=1` and the desired `PageSize`. For WUYING Cloud Application common scenarios, use `ProductType=CloudApp`.
1406
+ * 2. Read `Apps`. To retrieve the next page, increment `PageNumber` while keeping the product type and filter conditions unchanged. If no results match, `TotalCount` is `0` and `Apps` is an empty list. If the page number exceeds the result range, `Apps` may also be empty, but `TotalCount` still indicates the total number of matching records.
1407
+ * 3. To authorize users for a specific application by application, pass the returned `AppInstanceGroupId`, `AppId`, and the same `ProductType` to [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~). To view delivery group details, pass `AppInstanceGroupId` and `ProductType` to [GetAppInstanceGroup](~~GetAppInstanceGroup~~).
1408
+ * The masked identities in the examples are for format demonstration purposes. Replace them with your actual identities when you invoke the operation.
1409
+ *
1410
+ * @param request - ListPublishedAppsRequest
1411
+ * @param runtime - runtime options for this request RuntimeOptions
1412
+ * @returns ListPublishedAppsResponse
1413
+ */
1414
+ listPublishedAppsWithOptions(request: $_model.ListPublishedAppsRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListPublishedAppsResponse>;
1415
+ /**
1416
+ * Queries deployed applications in published delivery groups under the current Alibaba Cloud account for a specified product type by paging, and returns each application along with its delivery group and the number of authorized users by application. Supports filtering by delivery group, application, and user authorization status.
1417
+ *
1418
+ * @remarks
1419
+ * ## Before you begin
1420
+ * When you call this operation by using a RAM user or Security Token Service (STS) credential, you must have the `appstreaming:ListPublishedApps` permission.
1421
+ * Only delivery groups in the published state whose images contain deployed applications are included in the query results. This operation only queries information. It does not create delivery groups or grant or revoke application access permissions.
1422
+ * ## Response granularity
1423
+ * Results are returned on a per-delivery-group-plus-application basis. If the same application is deployed in multiple published delivery groups, a separate record is returned for each combination. `TotalCount` also reflects the number of such combinations. The list is sorted by the creation time of the delivery group in descending order.
1424
+ * ## Query and pagination
1425
+ * - **You must explicitly specify `ProductType`, `PageNumber`, and `PageSize`.** Page numbers start from `1`, and the page size ranges from `1` to `100`. Invalid values return error codes `InvalidParameter.PageNumber` and `InvalidParameter.PageSize`, respectively.
1426
+ * - `AppInstanceGroupId`, `AppInstanceGroupName`, `AppId`, and `AppName` all support substring matching. You can specify them individually or in combination. When multiple conditions are specified, all conditions must be met.
1427
+ * - If an optional filter parameter is not specified or is set to an empty string, filtering is not applied for that condition.
1428
+ * - `ExcludeUserId` excludes applications that have been authorized to the specified user by application, which helps you find applications that can still be authorized to that user. **Access permissions granted through delivery-group-level authorization or user groups are not evaluated by this condition.**
1429
+ * ## Invocation sequence
1430
+ * 1. Initiate a query with `PageNumber=1` and the desired `PageSize`. For WUYING Cloud Application common scenarios, use `ProductType=CloudApp`.
1431
+ * 2. Read `Apps`. To retrieve the next page, increment `PageNumber` while keeping the product type and filter conditions unchanged. If no results match, `TotalCount` is `0` and `Apps` is an empty list. If the page number exceeds the result range, `Apps` may also be empty, but `TotalCount` still indicates the total number of matching records.
1432
+ * 3. To authorize users for a specific application by application, pass the returned `AppInstanceGroupId`, `AppId`, and the same `ProductType` to [AuthorizeUsersForApp](~~AuthorizeUsersForApp~~). To view delivery group details, pass `AppInstanceGroupId` and `ProductType` to [GetAppInstanceGroup](~~GetAppInstanceGroup~~).
1433
+ * The masked identities in the examples are for format demonstration purposes. Replace them with your actual identities when you invoke the operation.
1434
+ *
1435
+ * @param request - ListPublishedAppsRequest
1436
+ * @returns ListPublishedAppsResponse
1437
+ */
1438
+ listPublishedApps(request: $_model.ListPublishedAppsRequest): Promise<$_model.ListPublishedAppsResponse>;
1209
1439
  /**
1210
1440
  * Queries the regions supported by WUYING Cloud Application.
1211
1441
  *
@@ -1242,6 +1472,65 @@ export default class Client extends OpenApi {
1242
1472
  * @returns ListTagCloudResourcesResponse
1243
1473
  */
1244
1474
  listTagCloudResources(request: $_model.ListTagCloudResourcesRequest): Promise<$_model.ListTagCloudResourcesResponse>;
1475
+ /**
1476
+ * Queries tags bound to one or more delivery groups, or filters delivery groups that have specific tags bound by tag key-value pairs.
1477
+ *
1478
+ * @remarks
1479
+ * This operation complies with the Alibaba Cloud tagging standard and is used to query tags bound to Elastic Cloud Application (China) delivery groups. You can query tags bound to resources by resource ID, or filter resources that have specific tags bound by tag key-value pairs.
1480
+ * ## Before you begin
1481
+ * - A delivery group is created. You can call the ListAppInstanceGroup operation to obtain the delivery group ID.
1482
+ * - Tags are bound to the delivery group. You can bind tags by calling the TagResources operation, or by using the console or the Tag service.
1483
+ * ## Parameter description
1484
+ * - **ResourceType is required**. Only `APPINSTANCEGROUP` (delivery group) is supported. If you specify other values, the error code `InvalidResourceType.Invalid` is returned.
1485
+ * - **Specify at least one of ResourceId.N and Tag.N**. If neither is specified, the error code `MissingParameter.ResourceIdsOrTags` is returned.
1486
+ * - If only ResourceId.N is specified: all tags attached to the specified resources are returned.
1487
+ * - If only Tag.N is specified: all resources that have the specified tags attached and their matching tags are returned.
1488
+ * - If both are specified: only records of the specified resources that have the specified tags attached are returned.
1489
+ * - Tag.N.Key is required. If it is empty, the error code `InvalidTagPolicy.KeyInvalid` is returned. Tag.N.Value is optional. If it is not specified, the value of the tag key is not restricted, which means any tag value under the key is matched.
1490
+ * - Multiple Tag.N conditions have an AND relationship. A resource is returned only if it has all specified tags attached.
1491
+ * ## Response description
1492
+ * - Each record in the response corresponds to a resource-tag key-value pair. If a resource has multiple tags bound, multiple records are returned.
1493
+ * - TotalCount indicates the number of records returned.
1494
+ * - This operation returns all matching results at a time. An empty NextToken value indicates that no more data is available.
1495
+ * ## Invocation sequence
1496
+ * 1. Invoke the ListAppInstanceGroup operation to obtain the delivery group ID.
1497
+ * 2. Invoke the TagResources operation to attach tags to the delivery group.
1498
+ * 3. Invoke this operation to query tag bindings by resource ID or tag conditions.
1499
+ *
1500
+ * @param request - ListTagResourcesRequest
1501
+ * @param runtime - runtime options for this request RuntimeOptions
1502
+ * @returns ListTagResourcesResponse
1503
+ */
1504
+ listTagResourcesWithOptions(request: $_model.ListTagResourcesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListTagResourcesResponse>;
1505
+ /**
1506
+ * Queries tags bound to one or more delivery groups, or filters delivery groups that have specific tags bound by tag key-value pairs.
1507
+ *
1508
+ * @remarks
1509
+ * This operation complies with the Alibaba Cloud tagging standard and is used to query tags bound to Elastic Cloud Application (China) delivery groups. You can query tags bound to resources by resource ID, or filter resources that have specific tags bound by tag key-value pairs.
1510
+ * ## Before you begin
1511
+ * - A delivery group is created. You can call the ListAppInstanceGroup operation to obtain the delivery group ID.
1512
+ * - Tags are bound to the delivery group. You can bind tags by calling the TagResources operation, or by using the console or the Tag service.
1513
+ * ## Parameter description
1514
+ * - **ResourceType is required**. Only `APPINSTANCEGROUP` (delivery group) is supported. If you specify other values, the error code `InvalidResourceType.Invalid` is returned.
1515
+ * - **Specify at least one of ResourceId.N and Tag.N**. If neither is specified, the error code `MissingParameter.ResourceIdsOrTags` is returned.
1516
+ * - If only ResourceId.N is specified: all tags attached to the specified resources are returned.
1517
+ * - If only Tag.N is specified: all resources that have the specified tags attached and their matching tags are returned.
1518
+ * - If both are specified: only records of the specified resources that have the specified tags attached are returned.
1519
+ * - Tag.N.Key is required. If it is empty, the error code `InvalidTagPolicy.KeyInvalid` is returned. Tag.N.Value is optional. If it is not specified, the value of the tag key is not restricted, which means any tag value under the key is matched.
1520
+ * - Multiple Tag.N conditions have an AND relationship. A resource is returned only if it has all specified tags attached.
1521
+ * ## Response description
1522
+ * - Each record in the response corresponds to a resource-tag key-value pair. If a resource has multiple tags bound, multiple records are returned.
1523
+ * - TotalCount indicates the number of records returned.
1524
+ * - This operation returns all matching results at a time. An empty NextToken value indicates that no more data is available.
1525
+ * ## Invocation sequence
1526
+ * 1. Invoke the ListAppInstanceGroup operation to obtain the delivery group ID.
1527
+ * 2. Invoke the TagResources operation to attach tags to the delivery group.
1528
+ * 3. Invoke this operation to query tag bindings by resource ID or tag conditions.
1529
+ *
1530
+ * @param request - ListTagResourcesRequest
1531
+ * @returns ListTagResourcesResponse
1532
+ */
1533
+ listTagResources(request: $_model.ListTagResourcesRequest): Promise<$_model.ListTagResourcesResponse>;
1245
1534
  /**
1246
1535
  * Queries the configuration information of an administrator account, such as whether resource expiration reminders are enabled.
1247
1536
  *
@@ -1275,6 +1564,49 @@ export default class Client extends OpenApi {
1275
1564
  * @returns ListWuyingServerResponse
1276
1565
  */
1277
1566
  listWuyingServer(request: $_model.ListWuyingServerRequest): Promise<$_model.ListWuyingServerResponse>;
1567
+ /**
1568
+ * Queries the list of available zone IDs for a specified region, product type, and operating system type.
1569
+ *
1570
+ * @remarks
1571
+ * ## Operation description
1572
+ * This operation returns the list of available zone IDs for the current Alibaba Cloud account based on the specified region, product type, and operating system type. A typical use case is to check which zones are available before creating a resource that requires a vSwitch, and then select a vSwitch in one of those zones.
1573
+ * This operation only queries information. It does not create resources or incur fees.
1574
+ * ## Before you begin
1575
+ * - When calling this operation with a RAM user or STS credential, the `appstreaming:ListAppInstanceType` permission is required. If the permission is insufficient, the error code `Forbidden.NoPermission` is returned.
1576
+ * - **`ProductType`, `BizRegionId`, and `OsType` are all required.** If any of these parameters is missing, empty, or set to an unrecognized value, the error code `InvalidParameter.ValueInvalid` is returned.
1577
+ * - `BizRegionId` must be a region ID supported by WUYING Cloud Application. Call [ListRegions](~~ListRegions~~) first to obtain the supported region IDs.
1578
+ * ## Call sequence
1579
+ * 1. Call [ListRegions](~~ListRegions~~) to obtain the supported region IDs.
1580
+ * 2. Call this operation with the region ID, target product type, and operating system type, and read the returned `ListZonesModel.Zones`.
1581
+ * 3. When creating a resource that requires a vSwitch, select a vSwitch in one of the returned zones. For example, pass the corresponding vSwitch ID when calling [CreateAppInstanceGroup](~~CreateAppInstanceGroup~~) or [CreateWuyingServer](~~CreateWuyingServer~~).
1582
+ * The returned zone list is determined by the available resources in the current region and may change over time. Query the list in real time before creating resources instead of caching it for extended periods.
1583
+ *
1584
+ * @param request - ListZonesRequest
1585
+ * @param runtime - runtime options for this request RuntimeOptions
1586
+ * @returns ListZonesResponse
1587
+ */
1588
+ listZonesWithOptions(request: $_model.ListZonesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.ListZonesResponse>;
1589
+ /**
1590
+ * Queries the list of available zone IDs for a specified region, product type, and operating system type.
1591
+ *
1592
+ * @remarks
1593
+ * ## Operation description
1594
+ * This operation returns the list of available zone IDs for the current Alibaba Cloud account based on the specified region, product type, and operating system type. A typical use case is to check which zones are available before creating a resource that requires a vSwitch, and then select a vSwitch in one of those zones.
1595
+ * This operation only queries information. It does not create resources or incur fees.
1596
+ * ## Before you begin
1597
+ * - When calling this operation with a RAM user or STS credential, the `appstreaming:ListAppInstanceType` permission is required. If the permission is insufficient, the error code `Forbidden.NoPermission` is returned.
1598
+ * - **`ProductType`, `BizRegionId`, and `OsType` are all required.** If any of these parameters is missing, empty, or set to an unrecognized value, the error code `InvalidParameter.ValueInvalid` is returned.
1599
+ * - `BizRegionId` must be a region ID supported by WUYING Cloud Application. Call [ListRegions](~~ListRegions~~) first to obtain the supported region IDs.
1600
+ * ## Call sequence
1601
+ * 1. Call [ListRegions](~~ListRegions~~) to obtain the supported region IDs.
1602
+ * 2. Call this operation with the region ID, target product type, and operating system type, and read the returned `ListZonesModel.Zones`.
1603
+ * 3. When creating a resource that requires a vSwitch, select a vSwitch in one of the returned zones. For example, pass the corresponding vSwitch ID when calling [CreateAppInstanceGroup](~~CreateAppInstanceGroup~~) or [CreateWuyingServer](~~CreateWuyingServer~~).
1604
+ * The returned zone list is determined by the available resources in the current region and may change over time. Query the list in real time before creating resources instead of caching it for extended periods.
1605
+ *
1606
+ * @param request - ListZonesRequest
1607
+ * @returns ListZonesResponse
1608
+ */
1609
+ listZones(request: $_model.ListZonesRequest): Promise<$_model.ListZonesResponse>;
1278
1610
  /**
1279
1611
  * Logs off all sessions in a pay-as-you-go delivery group that has scheduled auto scaling enabled.
1280
1612
  *
@@ -1624,6 +1956,63 @@ export default class Client extends OpenApi {
1624
1956
  * @returns TagCloudResourcesResponse
1625
1957
  */
1626
1958
  tagCloudResources(request: $_model.TagCloudResourcesRequest): Promise<$_model.TagCloudResourcesResponse>;
1959
+ /**
1960
+ * Creates and binds tags to specified China Office (Chinese: Wuying) delivery groups in compliance with Alibaba Cloud tag specifications. If a tag key already exists on a resource, the tag value is updated to the value specified in the current request. Currently, only delivery group (`APPINSTANCEGROUP`) resource types are supported.
1961
+ *
1962
+ * @remarks
1963
+ * ## Before you begin
1964
+ * When you use a RAM user or Security Token Service (STS) credential to call this operation, you must have the `appstreaming:TagResources` permission.
1965
+ * The resources to which you want to bind tags must belong to the current Alibaba Cloud account. **This operation currently supports only delivery group resources.** You can set `ResourceType` only to `APPINSTANCEGROUP`. You can call [ListAppInstanceGroup](~~ListAppInstanceGroup~~) to obtain delivery group IDs.
1966
+ * ## Tag rules
1967
+ * - In a single request, you can bind up to **20 tags** to up to **50 resources**. Duplicate resource IDs are automatically deduplicated.
1968
+ * - A tag key must be 1 to 128 characters in length. A tag value must be 0 to 256 characters in length. Both are case-sensitive.
1969
+ * - A tag key cannot start with `aliyun` or `acs:` (case-insensitive). Neither tag keys nor tag values can contain `http://` or `https://`.
1970
+ * - Tag keys in the same request must be unique. Otherwise, the error code `InvalidTag.Duplicated` is returned.
1971
+ * - Each tag key on a resource can correspond to only one tag value. If the tag key already exists on the resource, the tag value is updated to the new value.
1972
+ * - A maximum of 20 custom tags can be bound to a single resource. If this limit is exceeded, the error code `ResourceTag.CustomTagCountExceed` is returned.
1973
+ * ## Results
1974
+ * - **If any specified delivery group does not exist or does not belong to the current account, the entire request fails.** The error code `InvalidAppInstanceGroup.NotFound` is returned, and no tags are bound to any resource.
1975
+ * - If the binding succeeds, the response contains only `RequestId` and does not return tag details.
1976
+ * - If multiple resources are specified and only some of them fail to be bound, the operation still returns a success response without failure details. Call `ListTagResources` to verify the binding results. If only one resource is specified and the binding fails, the operation returns the corresponding error code.
1977
+ * ## Call sequence
1978
+ * 1. Call [ListAppInstanceGroup](~~ListAppInstanceGroup~~) to obtain the IDs of the delivery groups to which you want to add tags.
1979
+ * 2. Call this operation with `ResourceType=APPINSTANCEGROUP`, `ResourceId.N`, and `Tag.N.Key`/`Tag.N.Value`.
1980
+ * 3. To view the tags bound to resources, call `ListTagResources`. To unbind tags, call `UntagResources`.
1981
+ * The masked identifiers in the examples are used to demonstrate the format. Replace them with your actual identifiers when you call the operation.
1982
+ *
1983
+ * @param request - TagResourcesRequest
1984
+ * @param runtime - runtime options for this request RuntimeOptions
1985
+ * @returns TagResourcesResponse
1986
+ */
1987
+ tagResourcesWithOptions(request: $_model.TagResourcesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.TagResourcesResponse>;
1988
+ /**
1989
+ * Creates and binds tags to specified China Office (Chinese: Wuying) delivery groups in compliance with Alibaba Cloud tag specifications. If a tag key already exists on a resource, the tag value is updated to the value specified in the current request. Currently, only delivery group (`APPINSTANCEGROUP`) resource types are supported.
1990
+ *
1991
+ * @remarks
1992
+ * ## Before you begin
1993
+ * When you use a RAM user or Security Token Service (STS) credential to call this operation, you must have the `appstreaming:TagResources` permission.
1994
+ * The resources to which you want to bind tags must belong to the current Alibaba Cloud account. **This operation currently supports only delivery group resources.** You can set `ResourceType` only to `APPINSTANCEGROUP`. You can call [ListAppInstanceGroup](~~ListAppInstanceGroup~~) to obtain delivery group IDs.
1995
+ * ## Tag rules
1996
+ * - In a single request, you can bind up to **20 tags** to up to **50 resources**. Duplicate resource IDs are automatically deduplicated.
1997
+ * - A tag key must be 1 to 128 characters in length. A tag value must be 0 to 256 characters in length. Both are case-sensitive.
1998
+ * - A tag key cannot start with `aliyun` or `acs:` (case-insensitive). Neither tag keys nor tag values can contain `http://` or `https://`.
1999
+ * - Tag keys in the same request must be unique. Otherwise, the error code `InvalidTag.Duplicated` is returned.
2000
+ * - Each tag key on a resource can correspond to only one tag value. If the tag key already exists on the resource, the tag value is updated to the new value.
2001
+ * - A maximum of 20 custom tags can be bound to a single resource. If this limit is exceeded, the error code `ResourceTag.CustomTagCountExceed` is returned.
2002
+ * ## Results
2003
+ * - **If any specified delivery group does not exist or does not belong to the current account, the entire request fails.** The error code `InvalidAppInstanceGroup.NotFound` is returned, and no tags are bound to any resource.
2004
+ * - If the binding succeeds, the response contains only `RequestId` and does not return tag details.
2005
+ * - If multiple resources are specified and only some of them fail to be bound, the operation still returns a success response without failure details. Call `ListTagResources` to verify the binding results. If only one resource is specified and the binding fails, the operation returns the corresponding error code.
2006
+ * ## Call sequence
2007
+ * 1. Call [ListAppInstanceGroup](~~ListAppInstanceGroup~~) to obtain the IDs of the delivery groups to which you want to add tags.
2008
+ * 2. Call this operation with `ResourceType=APPINSTANCEGROUP`, `ResourceId.N`, and `Tag.N.Key`/`Tag.N.Value`.
2009
+ * 3. To view the tags bound to resources, call `ListTagResources`. To unbind tags, call `UntagResources`.
2010
+ * The masked identifiers in the examples are used to demonstrate the format. Replace them with your actual identifiers when you call the operation.
2011
+ *
2012
+ * @param request - TagResourcesRequest
2013
+ * @returns TagResourcesResponse
2014
+ */
2015
+ tagResources(request: $_model.TagResourcesRequest): Promise<$_model.TagResourcesResponse>;
1627
2016
  /**
1628
2017
  * Unbinds secondary private IP addresses from a development host.
1629
2018
  *
@@ -1669,6 +2058,63 @@ export default class Client extends OpenApi {
1669
2058
  * @returns UntagCloudResourcesResponse
1670
2059
  */
1671
2060
  untagCloudResources(request: $_model.UntagCloudResourcesRequest): Promise<$_model.UntagCloudResourcesResponse>;
2061
+ /**
2062
+ * Unbinds tags from specified Wuying delivery groups in compliance with Alibaba Cloud tagging standards. You can unbind specific tags by tag key or unbind all custom tags from a resource at once by setting `All=true` without specifying tag keys. Currently, only the delivery group (`APPINSTANCEGROUP`) resource type is supported.
2063
+ *
2064
+ * @remarks
2065
+ * ## Before you begin
2066
+ * When calling this operation with a RAM user or STS credential, the `appstreaming:UntagResources` permission is required.
2067
+ * The resources from which you want to unbind tags must belong to the current Alibaba Cloud account. **This operation currently supports only delivery group resources.** You can set `ResourceType` only to `APPINSTANCEGROUP`. You can obtain delivery group IDs by calling [ListAppInstanceGroup](~~ListAppInstanceGroup~~), and query tags that are bound to a resource by calling [ListTagResources](~~ListTagResources~~).
2068
+ * ## Parameter description
2069
+ * - You can unbind tags from up to **50 resources** in a single request. Duplicate resource IDs are automatically deduplicated.
2070
+ * - **Specify at least one of `TagKey.N` and `All`.** If neither is specified, or if `TagKey.N` is not specified and `All` is set to `false`, the error code `InvalidParameter.TagKeyListOrAll` is returned.
2071
+ * - If `TagKey.N` is specified: only the tags that correspond to the specified tag keys are unbound. You can specify up to 20 tag keys at a time. The `All` parameter is ignored.
2072
+ * - If `TagKey.N` is not specified and `All=true`: all custom tags on the resource are unbound, including Wuying system tags that start with `System/` and were attached by calling [TagResources](~~TagResources~~).
2073
+ * - If a specified tag key does not exist on the resource, the tag key is skipped and no error is returned.
2074
+ * - Tag keys that start with `System/` are Wuying system tags. Only `System/Scheduler/GRAYSCALE` and `System/Scheduler/STOP_NEW_USER_CONNECTION` are supported. If you specify other tag keys that start with `System/`, the error code `InvalidTagPolicy.KeyInvalid` or `InvalidTag.SystemKeyNotAllow` is returned.
2075
+ * ## Execution results
2076
+ * - **If any specified delivery group does not exist or does not belong to the current account, the entire request fails** with the error code `InvalidAppInstanceGroup.NotFound`, and no tags are unbound from any resource.
2077
+ * - On success, the response contains only `RequestId` and does not return tag details.
2078
+ * - When multiple resources are specified and only some fail to have tags unbound, the operation still returns success and the response does not contain failure details. Call [ListTagResources](~~ListTagResources~~) to verify the unbinding results. When only one resource is specified and the unbinding fails, the operation returns the corresponding error code directly.
2079
+ * ## Call sequence
2080
+ * 1. Call [ListAppInstanceGroup](~~ListAppInstanceGroup~~) to obtain delivery group IDs. To check which tag keys are bound to a resource, call [ListTagResources](~~ListTagResources~~).
2081
+ * 2. Call this operation with `ResourceType=APPINSTANCEGROUP` and `ResourceId.N`, and specify `TagKey.N` or `All=true` to indicate the tags to unbind.
2082
+ * 3. To rebind tags, call [TagResources](~~TagResources~~).
2083
+ * The masked identifiers in the examples are for format demonstration purposes only. Replace them with your actual identifiers when making calls.
2084
+ *
2085
+ * @param request - UntagResourcesRequest
2086
+ * @param runtime - runtime options for this request RuntimeOptions
2087
+ * @returns UntagResourcesResponse
2088
+ */
2089
+ untagResourcesWithOptions(request: $_model.UntagResourcesRequest, runtime: $dara.RuntimeOptions): Promise<$_model.UntagResourcesResponse>;
2090
+ /**
2091
+ * Unbinds tags from specified Wuying delivery groups in compliance with Alibaba Cloud tagging standards. You can unbind specific tags by tag key or unbind all custom tags from a resource at once by setting `All=true` without specifying tag keys. Currently, only the delivery group (`APPINSTANCEGROUP`) resource type is supported.
2092
+ *
2093
+ * @remarks
2094
+ * ## Before you begin
2095
+ * When calling this operation with a RAM user or STS credential, the `appstreaming:UntagResources` permission is required.
2096
+ * The resources from which you want to unbind tags must belong to the current Alibaba Cloud account. **This operation currently supports only delivery group resources.** You can set `ResourceType` only to `APPINSTANCEGROUP`. You can obtain delivery group IDs by calling [ListAppInstanceGroup](~~ListAppInstanceGroup~~), and query tags that are bound to a resource by calling [ListTagResources](~~ListTagResources~~).
2097
+ * ## Parameter description
2098
+ * - You can unbind tags from up to **50 resources** in a single request. Duplicate resource IDs are automatically deduplicated.
2099
+ * - **Specify at least one of `TagKey.N` and `All`.** If neither is specified, or if `TagKey.N` is not specified and `All` is set to `false`, the error code `InvalidParameter.TagKeyListOrAll` is returned.
2100
+ * - If `TagKey.N` is specified: only the tags that correspond to the specified tag keys are unbound. You can specify up to 20 tag keys at a time. The `All` parameter is ignored.
2101
+ * - If `TagKey.N` is not specified and `All=true`: all custom tags on the resource are unbound, including Wuying system tags that start with `System/` and were attached by calling [TagResources](~~TagResources~~).
2102
+ * - If a specified tag key does not exist on the resource, the tag key is skipped and no error is returned.
2103
+ * - Tag keys that start with `System/` are Wuying system tags. Only `System/Scheduler/GRAYSCALE` and `System/Scheduler/STOP_NEW_USER_CONNECTION` are supported. If you specify other tag keys that start with `System/`, the error code `InvalidTagPolicy.KeyInvalid` or `InvalidTag.SystemKeyNotAllow` is returned.
2104
+ * ## Execution results
2105
+ * - **If any specified delivery group does not exist or does not belong to the current account, the entire request fails** with the error code `InvalidAppInstanceGroup.NotFound`, and no tags are unbound from any resource.
2106
+ * - On success, the response contains only `RequestId` and does not return tag details.
2107
+ * - When multiple resources are specified and only some fail to have tags unbound, the operation still returns success and the response does not contain failure details. Call [ListTagResources](~~ListTagResources~~) to verify the unbinding results. When only one resource is specified and the unbinding fails, the operation returns the corresponding error code directly.
2108
+ * ## Call sequence
2109
+ * 1. Call [ListAppInstanceGroup](~~ListAppInstanceGroup~~) to obtain delivery group IDs. To check which tag keys are bound to a resource, call [ListTagResources](~~ListTagResources~~).
2110
+ * 2. Call this operation with `ResourceType=APPINSTANCEGROUP` and `ResourceId.N`, and specify `TagKey.N` or `All=true` to indicate the tags to unbind.
2111
+ * 3. To rebind tags, call [TagResources](~~TagResources~~).
2112
+ * The masked identifiers in the examples are for format demonstration purposes only. Replace them with your actual identifiers when making calls.
2113
+ *
2114
+ * @param request - UntagResourcesRequest
2115
+ * @returns UntagResourcesResponse
2116
+ */
2117
+ untagResources(request: $_model.UntagResourcesRequest): Promise<$_model.UntagResourcesResponse>;
1672
2118
  /**
1673
2119
  * Updates the image of a delivery group.
1674
2120
  *