@alicloud/config20200907 4.2.0 → 4.2.1

package/src/models/UpdateConfigDeliveryChannelRequest.ts

@@ -5,9 +5,9 @@ import * as $dara from '@darabonba/typescript';
 export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   /**
    * @remarks
-   * The client token that is used to ensure the idempotency of the request. You can use the client to generate the token, but you must ensure that the token is unique among different requests.
+   * A client token used to ensure the idempotence of the request. Use a client to generate the token, and make sure that the token is unique among different requests.
    * 
-   * The `token` can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see [How to ensure idempotence](https://help.aliyun.com/document_detail/25693.html).
+   * The `ClientToken` parameter can contain only ASCII characters and cannot exceed 64 characters in length. For more information, see [How to ensure idempotence](https://help.aliyun.com/document_detail/25693.html).
    * 
    * @example
    * 1594295238-f9361358-5843-4294-8d30-b5183fac****
@@ -15,10 +15,11 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   clientToken?: string;
   /**
    * @remarks
-   * Specifies whether to deliver scheduled compliant snapshots. Cloud Config delivers scheduled compliant snapshots at `04:00Z` and `16:00Z` to  Log Service every day. The time is displayed in UTC. Valid values:
+   * Specifies whether to deliver resource compliance snapshots. Cloud Config delivers resource compliance and non-compliance information to SLS. Valid values:
    * 
-   * *   true: Cloud Config delivers compliant snapshots.
-   * *   false (default): Cloud Config does not deliver scheduled compliant snapshots.
+   * - true: The resource compliance snapshots are delivered.
+   * 
+   * - false: The resource compliance snapshots are not delivered.
    * 
    * @example
    * false
@@ -29,10 +30,11 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   compliantSnapshot?: boolean;
   /**
    * @remarks
-   * Specifies whether to deliver resource change logs. If you set this parameter to true, Cloud Config delivers resource change logs to OSS, Log Service, or MNS when the configurations of the resources change. Valid values:
+   * Specifies whether to deliver the resource configuration history. Cloud Config delivers the resource configuration history to OSS, SLS, or MNS when the configuration of a resource changes. Valid values:
+   * 
+   * - true: The resource configuration history is delivered.
    * 
-   * *   true: Cloud Config delivers resource change logs.
-   * *   false (default): Cloud Config does not deliver resource change logs.
+   * - false (default): The resource configuration history is not delivered.
    * 
    * > This parameter is available for delivery channels of the OSS, SLS, and MNS types.
    * 
@@ -45,10 +47,11 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   configurationItemChangeNotification?: boolean;
   /**
    * @remarks
-   * Specifies whether to deliver scheduled resource snapshots. Cloud Config delivers scheduled resource snapshots at `04:00Z` and `16:00Z` to OSS, MNS, or Log Service every day. The time is displayed in UTC. Valid values:
+   * Specifies whether to deliver scheduled resource snapshots. Cloud Config delivers scheduled resource snapshots to OSS or SLS at `04:00Z` and `16:00Z` (UTC) every day. Valid values:
+   * 
+   * - true: The scheduled resource snapshots are delivered.
    * 
-   * *   true: Cloud Config delivers scheduled resource snapshots.
-   * *   false (default): Cloud Config does not deliver scheduled resource snapshots.
+   * - false (default): The scheduled resource snapshots are not delivered.
    * 
    * @example
    * false
@@ -59,25 +62,25 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   configurationSnapshot?: boolean;
   /**
    * @remarks
-   * The rule that you want to attach to the delivery channel. This parameter is available when you deliver data of all types to MNS or deliver snapshots to Log Service.
-   * 
-   * *   If the value of the DeliveryChannelType parameter is MNS, take note of the following settings of the lowest risk level and resource types of the events to which you subscribed:
-   * 
-   *     *   The setting of the lowest risk level for the events to which you want to subscribe is in the following format: `{"filterType":"RuleRiskLevel","value":"1","multiple":false}`.
+   * The rule that is attached to the delivery channel. This parameter is applicable to all deliveries to MNS and snapshot deliveries to SLS.
    * 
-   *         The `value` field indicates the lowest risk level of the events to which you want to subscribe. Valid values: 1, 2, and 3. The value 1 indicates the high risk level, the value 2 indicates the medium risk level, and the value 3 indicates the low risk level.
+   * - If you specify the minimum risk level of events and the resource types for an MNS subscription, use the following formats:
    * 
-   *     *   The setting of the resource types of the events to which you want to subscribe is in the following format: `{"filterType":"ResourceType","values":["ACS::ACK::Cluster","ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage"],"multiple":true}`.
+   *   - The minimum risk level of the subscribed events: `{"filterType":"RuleRiskLevel","value":"1","multiple":false}`.
    * 
-   *         The `values` field indicates the resource types of the events to which you want to subscribe. The value of the field is a JSON array. Examples:
+   *     `value` specifies the risk level. Valid values: 1 (high risk), 2 (medium risk), and 3 (low risk).
    * 
-   * `[{"filterType":"ResourceType","values":["ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage","ACS::CDN::Domain","ACS::CEN::CenBandwidthPackage","ACS::CEN::CenInstance","ACS::CEN::Flowlog","ACS::DdosCoo::Instance"],"multiple":true}]`
+   *   - The resource types of the subscribed events: `{"filterType":"ResourceType","values":["ACS::ACK::Cluster","ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage"],"multiple":true}`.
    * 
-   * *   If you set the DeliveryChannelType parameter to SLS, the setting of the resource types of the snapshots to which you want to deliver is in the following format: `{"filterType":"ResourceType","values":["ACS::ACK::Cluster","ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage"],"multiple":true}`.
+   *     `values` specifies the resource types of the subscribed events. The value is a JSON array.
+   *     Example:
+   *     `[{"filterType":"ResourceType","values":["ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage","ACS::CDN::Domain","ACS::CEN::CenBandwidthPackage","ACS::CEN::CenInstance","ACS::CEN::Flowlog","ACS::DdosCoo::Instance"],"multiple":true}]`
    * 
-   *     The `values` field specifies the resource types of the snapshots to which you want to deliver. The value of the field is a JSON array. Examples:
+   * - If you specify the resource types of snapshots delivered to SLS, use the following format: `{"filterType":"ResourceType","values":["ACS::ACK::Cluster","ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage"],"multiple":true}`.
    * 
-   * `[{"filterType":"ResourceType","values":["ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage","ACS::CDN::Domain","ACS::CEN::CenBandwidthPackage","ACS::CEN::CenInstance","ACS::CEN::Flowlog","ACS::DdosCoo::Instance"],"multiple":true}]`
+   *   `values` specifies the resource types of the snapshots to deliver. The value is a JSON array.
+   *   Example:
+   *   `[{"filterType":"ResourceType","values":["ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage","ACS::CDN::Domain","ACS::CEN::CenBandwidthPackage","ACS::CEN::CenInstance","ACS::CEN::Flowlog","ACS::DdosCoo::Instance"],"multiple":true}]`
    * 
    * @example
    * [{"filterType":"ResourceType","values":["ACS::ActionTrail::Trail","ACS::CBWP::CommonBandwidthPackage","ACS::CDN::Domain","ACS::CEN::CenBandwidthPackage","ACS::CEN::CenInstance","ACS::CEN::Flowlog","ACS::DdosCoo::Instance"],"multiple":true}]
@@ -87,7 +90,7 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
    * @remarks
    * The ID of the delivery channel.
    * 
-   * For more information about how to obtain the ID of a delivery channel, see [DescribeDeliveryChannels](https://help.aliyun.com/document_detail/429841.html).
+   * For more information about how to obtain the delivery channel ID, see [ListConfigDeliveryChannels](https://help.aliyun.com/document_detail/429841.html).
    * 
    * This parameter is required.
    * 
@@ -107,9 +110,11 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
    * @remarks
    * The Alibaba Cloud Resource Name (ARN) of the delivery destination. Valid values:
    * 
-   * *   `acs:oss:{RegionId}:{accountId}:{bucketName}` if your delivery destination is an OSS bucket. Example: `acs:oss:cn-shanghai:100931896542****:new-bucket`.
-   * *   `acs:mns:{RegionId}:{accountId}:/topics/{topicName}` if your delivery destination is an MNS topic. Example: `acs:mns:cn-shanghai:100931896542****:/topics/topic1`.
-   * *   `acs:log:{RegionId}:{accountId}:project/{projectName}/logstore/{logstoreName}` if your delivery destination is a Log Service Logstore. Example: `acs:log:cn-shanghai:100931896542****:project/project1/logstore/logstore1`.
+   * - If the delivery channel is Object Storage Service (OSS), the value is in the format of `acs:oss:{RegionId}:{accountId}:{bucketName}`. Example: `acs:oss:cn-shanghai:100931896542****:new-bucket`.
+   * 
+   * - If the delivery channel is MNS, the value is in the format of `acs:mns:{RegionId}:{accountId}:/topics/{topicName}`. Example: `acs:mns:cn-shanghai:100931896542****:/topics/topic1`.
+   * 
+   * - If the delivery channel is Simple Log Service (SLS), the value is in the format of `acs:log:{RegionId}:{accountId}:project/{projectName}/logstore/{logstoreName}`. Example: `acs:log:cn-shanghai:100931896542****:project/project1/logstore/logstore1`.
    * 
    * @example
    * acs:oss:cn-shanghai:100931896542****:new-bucket
@@ -117,11 +122,11 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   deliveryChannelTargetArn?: string;
   /**
    * @remarks
-   * The time when you want Cloud Config to deliver scheduled resource snapshots every day.
+   * The time of day when the scheduled resource snapshot is delivered.
    * 
-   * Format: `HH:mmZ`. This time is displayed in UTC.
+   * The value is in the `HH:mmZ` format. The time is in UTC.
    * 
-   * > When you enable the scheduled resource delivery feature, you can configure this parameter to specify a custom delivery time. If you do not configure this parameter, Cloud Config automatically delivers scheduled resource snapshots at `04:00Z` and `16:00Z` every day.
+   * > If you enable scheduled delivery of resource snapshots, use this parameter to specify a delivery time. If you do not specify this parameter, Cloud Config delivers the scheduled resource snapshots at `04:00Z` and `16:00Z` by default.
    * 
    * @example
    * 09:10Z
@@ -137,12 +142,13 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   description?: string;
   /**
    * @remarks
-   * Specifies whether to deliver resource non-compliance events. If you set this parameter to true, Cloud Config delivers resource non-compliance events to Log Service or MNS when resources are considered non-compliant. Valid values:
+   * Specifies whether to deliver resource non-compliance events. Cloud Config delivers resource non-compliance events to SLS or MNS when a resource is evaluated as non-compliant. Valid values:
    * 
-   * *   true: Cloud Config delivers resource non-compliance events.
-   * *   false (default): Cloud Config does not deliver resource non-compliance events.
+   * - true: The resource non-compliance events are delivered.
    * 
-   * > This parameter is available only for delivery channels of the SLS or MNS type.
+   * - false (default): The resource non-compliance events are not delivered.
+   * 
+   * > This parameter is available only for delivery channels of the SLS and MNS types.
    * 
    * @example
    * false
@@ -153,11 +159,11 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   nonCompliantNotification?: boolean;
   /**
    * @remarks
-   * The ARN of the OSS bucket to which you want to transfer the delivery data when the size of the data exceeds the specified upper limit of the delivery channel. Format: `acs:oss:{RegionId}:{accountId}:{bucketName}`.
+   * The ARN of the OSS bucket where data is delivered when the data size exceeds the limit of the delivery channel. The value is in the format of `acs:oss:{RegionId}:{accountId}:{bucketName}`.
    * 
-   * If you do not configure this parameter, Cloud Config delivers only summary data.
+   * If you do not specify this parameter, Cloud Config delivers only the summary of the data.
    * 
-   * > This parameter is available only for delivery channels of the SLS or MNS type. The maximum storage size of delivery channels of the SLS type is 1 MB, and the maximum storage size of delivery channels of the MNS type is 64 KB.
+   * > This parameter is available only for delivery channels of the SLS and MNS types. The maximum size of data that can be delivered to SLS is 1 MB. The maximum size of data that can be delivered to MNS is 64 KB.
    * 
    * @example
    * acs:oss:cn-shanghai:100931896542****:new-bucket
@@ -165,10 +171,11 @@ export class UpdateConfigDeliveryChannelRequest extends $dara.Model {
   oversizedDataOSSTargetArn?: string;
   /**
    * @remarks
-   * Specifies whether to enable the delivery channel. Valid values:
+   * The status of the delivery channel. Valid values:
+   * 
+   * - 0: The delivery channel is disabled. Cloud Config retains the most recent delivery configuration and stops delivering resource data.
    * 
-   * *   0: Cloud Config disables the delivery channel. Cloud Config retains the most recent delivery configuration and stops resource data delivery.
-   * *   1 (default): Cloud Config enables the delivery channel.
+   * - 1 (default): The delivery channel is enabled.
    * 
    * @example
    * 0

package/src/models/UpdateConfigRuleRequest.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class UpdateConfigRuleRequestExcludeTagsScope extends $dara.Model {
   /**
    * @remarks
-   * The key of the tag.
+   * The tag key.
    * 
    * @example
    * key-2
@@ -13,7 +13,7 @@ export class UpdateConfigRuleRequestExcludeTagsScope extends $dara.Model {
   tagKey?: string;
   /**
    * @remarks
-   * The value of the tag.
+   * The tag value.
    * 
    * @example
    * value-2
@@ -45,7 +45,7 @@ export class UpdateConfigRuleRequestExcludeTagsScope extends $dara.Model {
 export class UpdateConfigRuleRequestTag extends $dara.Model {
   /**
    * @remarks
-   * The key of tag N to add to the key pair. Valid values of N: 1 to 20. The tag key cannot be an empty string. The tag key can be up to 128 characters in length and cannot contain `http://` or `https://`. The tag key cannot start with `acs:` or `aliyun`.
+   * The tag key.
    * 
    * @example
    * key-1
@@ -53,7 +53,7 @@ export class UpdateConfigRuleRequestTag extends $dara.Model {
   key?: string;
   /**
    * @remarks
-   * The value of tag N. Valid values of N: **1 to 20**. The tag value can be an empty string. The tag value can be up to 128 characters in length and cannot contain `http://` or `https://`. The tag value cannot start with `aliyun` and `acs:`.
+   * The tag value.
    * 
    * @example
    * value-1
@@ -85,7 +85,7 @@ export class UpdateConfigRuleRequestTag extends $dara.Model {
 export class UpdateConfigRuleRequestTagsScope extends $dara.Model {
   /**
    * @remarks
-   * The key of the tag.
+   * The tag key.
    * 
    * @example
    * key-1
@@ -93,7 +93,7 @@ export class UpdateConfigRuleRequestTagsScope extends $dara.Model {
   tagKey?: string;
   /**
    * @remarks
-   * The value of the tag.
+   * The tag value.
    * 
    * @example
    * value-1
@@ -125,17 +125,25 @@ export class UpdateConfigRuleRequestTagsScope extends $dara.Model {
 export class UpdateConfigRuleRequest extends $dara.Model {
   /**
    * @remarks
-   * The client token that you want to use to ensure the idempotency of the request. You can use the client to generate the value, but you must make sure that the value is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.``
+   * A client token used to ensure the idempotence of the request. You can use a client to generate the token, but you must make sure that the token is unique for different requests. The `ClientToken` parameter can contain only ASCII characters and cannot be more than 64 characters in length.
    * 
    * @example
    * 1594295238-f9361358-5843-4294-8d30-b5183fac****
    */
   clientToken?: string;
+  /**
+   * @example
+   * {"ComplianceConditions":"{\"operator\":\"and\",\"children\":[{\"operator\":\"StringEquals\",\"featurePath\":\"$.Status\",\"desired\":\"1\",\"featureSource\":\"CONFIGURATION\"}]}"}
+   * 
+   * **if can be null:**
+   * true
+   */
+  conditions?: string;
   /**
    * @remarks
-   * The ID of the rule.
+   * The rule ID.
    * 
-   * For more information about how to query the ID of a rule, see [ListConfigRules](https://help.aliyun.com/document_detail/169607.html).
+   * For more information, see [ListConfigRules](https://help.aliyun.com/document_detail/169607.html).
    * 
    * This parameter is required.
    * 
@@ -147,20 +155,21 @@ export class UpdateConfigRuleRequest extends $dara.Model {
    * @remarks
    * The name of the rule.
    * 
-   * For more information about how to query the name of a rule, see [ListAggregateConfigRules](https://help.aliyun.com/document_detail/264148.html).
+   * For more information, see [ListAggregateConfigRules](https://help.aliyun.com/document_detail/264148.html).
    * 
    * @example
-   * The name of the rule.
+   * 存在所有指定标签
    */
   configRuleName?: string;
   /**
    * @remarks
    * The trigger type of the rule. Valid values:
    * 
-   * *   ConfigurationItemChangeNotification: The rule is triggered by configuration changes.
-   * *   ScheduledNotification: The rule is periodically triggered.
+   * - ConfigurationItemChangeNotification: The rule is triggered by configuration changes.
    * 
-   * >  This parameter applies only to custom rules.
+   * - ScheduledNotification: The rule is triggered on a regular basis.
+   * 
+   * > This parameter can be modified only for custom rules.
    * 
    * @example
    * ConfigurationItemChangeNotification
@@ -168,15 +177,15 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   configRuleTriggerTypes?: string;
   /**
    * @remarks
-   * The description of the rule. You can enter up to 500 characters.
+   * The description of the rule. The description can be up to 500 characters in length.
    * 
    * @example
-   * The description of the rule.
+   * 最多可以定义6组标签。如果资源同时具有指定的所有标签，则视为“合规”。
    */
   description?: string;
   /**
    * @remarks
-   * The IDs of the regions excluded from the compliance evaluations performed by the rule. Separate multiple region IDs with commas (,).
+   * The regions where the rule is not effective. The system does not evaluate resources in these regions. To specify multiple region IDs, separate them with a comma (,).
    * 
    * @example
    * cn-shanghai
@@ -184,7 +193,7 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   excludeRegionIdsScope?: string;
   /**
    * @remarks
-   * The IDs of the resource groups excluded from the compliance evaluations performed by the rule. Separate multiple resource group IDs with commas (,).
+   * The resource groups where the rule is not effective. The system does not evaluate resources in these resource groups. To specify multiple resource group IDs, separate them with a comma (,).
    * 
    * @example
    * rg-bnczc6r7rml****
@@ -192,9 +201,9 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   excludeResourceGroupIdsScope?: string;
   /**
    * @remarks
-   * The IDs of the resources excluded from the compliance evaluations performed by the rule. Separate multiple resource IDs with commas (,).
+   * The resources that are not evaluated by the rule. The system does not evaluate these resources. To specify multiple resource IDs, separate them with a comma (,).
    * 
-   * >  This parameter applies only to a managed rule.
+   * > This parameter applies only to managed rules.
    * 
    * @example
    * lb-t4nbowvtbkss7t326****
@@ -202,12 +211,12 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   excludeResourceIdsScope?: string;
   /**
    * @remarks
-   * The scope of the tag that is excluded.
+   * The tags that are used to exclude resources.
    */
   excludeTagsScope?: UpdateConfigRuleRequestExcludeTagsScope[];
   /**
    * @remarks
-   * Optional. The extended content of the resource. This parameter can be used together with the MaximumExecutionFrequency parameter when the MaximumExecutionFrequency parameter is set to TwentyFour_Hours to specify the trigger time.
+   * The extended content. This parameter is optional. You can use this parameter with a 24-hour trigger period to set the trigger time.
    * 
    * @example
    * {"fixedHour":"12"}
@@ -226,15 +235,19 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   inputParameters?: { [key: string]: any };
   /**
    * @remarks
-   * The interval at which the rule is triggered. Valid values:
+   * The frequency at which the rule is run. Valid values:
+   * 
+   * - One_Hour: 1 hour.
+   * 
+   * - Three_Hours: 3 hours.
+   * 
+   * - Six_Hours: 6 hours.
    * 
-   * *   One_Hour
-   * *   Three_Hours
-   * *   Six_Hours
-   * *   Twelve_Hours
-   * *   TwentyFour_Hours (default)
+   * - Twelve_Hours: 12 hours.
    * 
-   * >  This parameter is required if the `ConfigRuleTriggerTypes` parameter is set to `ScheduledNotification`.
+   * - TwentyFour_Hours (default): 24 hours.
+   * 
+   * > This parameter is required when `ConfigRuleTriggerTypes` is set to `ScheduledNotification`.
    * 
    * @example
    * One_Hour
@@ -242,9 +255,9 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   maximumExecutionFrequency?: string;
   /**
    * @remarks
-   * The IDs of the regions to which the rule applies. Separate multiple region IDs with commas (,).
+   * The regions where the rule is effective. The rule evaluates only resources in these regions. To specify multiple region IDs, separate them with a comma (,).
    * 
-   * >  This parameter applies only to a managed rule.
+   * > This parameter applies only to managed rules.
    * 
    * @example
    * cn-hangzhou
@@ -252,9 +265,9 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   regionIdsScope?: string;
   /**
    * @remarks
-   * The IDs of the resource groups to which the rule applies. Separate multiple resource group IDs with commas (,).
+   * The resource groups where the rule is effective. The rule evaluates only resources in these resource groups. To specify multiple resource group IDs, separate them with a comma (,).
    * 
-   * >  This parameter applies only to a managed rule.
+   * > This parameter applies only to managed rules.
    * 
    * @example
    * rg-aekzc7r7rhx****
@@ -262,7 +275,7 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   resourceGroupIdsScope?: string;
   /**
    * @remarks
-   * The IDs of the resources to which the rule applies. Separate multiple resource IDs with commas (,).
+   * The resources that the rule evaluates. To specify multiple resource IDs, separate them with a comma (,).
    * 
    * @example
    * lb-5cmbowstbkss9ta03****
@@ -270,7 +283,7 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   resourceIdsScope?: string;
   /**
    * @remarks
-   * The names of the resource to which the rule applies.
+   * The names of the resources that the rule evaluates.
    * 
    * @example
    * i-xxx
@@ -281,7 +294,7 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   resourceNameScope?: string;
   /**
    * @remarks
-   * The type of the resource to be evaluated by the rule. Separate multiple resource types with commas (,).
+   * The resource types that the rule evaluates. To specify multiple resource types, separate them with a comma (,).
    * 
    * @example
    * ACS::ECS::Instance
@@ -289,11 +302,13 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   resourceTypesScope?: string[];
   /**
    * @remarks
-   * The risk level of the resources that do not comply with the rule. Valid values:
+   * The risk level of the rule. Valid values:
+   * 
+   * - 1: high risk.
+   * 
+   * - 2: medium risk.
    * 
-   * *   1: high
-   * *   2: medium
-   * *   3: low
+   * - 3: low risk.
    * 
    * @example
    * 3
@@ -301,24 +316,24 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   riskLevel?: number;
   /**
    * @remarks
-   * The tags of the resource.
+   * The tags of the resource. This parameter is deprecated. The value that you specify for this parameter does not take effect.
    * 
-   * You can add up to 20 tags to a resource.
+   * You can add up to 20 tags.
    * 
    * @deprecated
    */
   tag?: UpdateConfigRuleRequestTag[];
   /**
    * @remarks
-   * The logical relationship when parameter `TagsScope` takes multiple values, for example: When the parameter `TagsScope` is `"TagsScope.1.TagKey":"a", "TagsScope.1.TagValue":"a", "TagsScope.2.TagKey":"b", "TagsScope.2.TagValue":"b"`, if this parameter is set to` AND`, it means that the rule only applies to resources bound with both tags `a:a` and `b:b`. If not specified, the default logic is `OR`.
+   * The logical relationship for the tags that you specify for the `TagsScope` parameter. For example, if you set the `TagsScope` parameter to `"TagsScope.1.TagKey":"a","TagsScope.1.TagValue":"a","TagsScope.2.TagKey":"b","TagsScope.2.TagValue":"b"` and set this parameter to `AND`, the rule applies only to resources that have both the `a:a` and `b:b` tags. If you do not specify this parameter, the `OR` logic is used by default.
    * 
-   * It can also be used for the deprecated field `TagKeyScope` (not recommended), for example: When the parameter `TagKeyScope` has a value of `ECS`,`OSS`, if this parameter is set to `AND`, it means that the rule only applies to resources bound with both labels `ECS` and `OSS`.
+   * This parameter also applies to the deprecated `TagKeyScope` parameter, but this is not recommended. For example, if you set the `TagKeyScope` parameter to `ECS,OSS` and set this parameter to `AND`, the rule applies only to resources that have both the `ECS` and `OSS` tags.
    * 
-   * Values:
+   * Valid values:
    * 
-   *  - AND: And.
+   * - AND
    * 
-   *  - OR: Or.
+   * - OR
    * 
    * @example
    * AND
@@ -326,11 +341,11 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   tagKeyLogicScope?: string;
   /**
    * @remarks
-   * This parameter is deprecated. We recommend that you use the `TagsScope` parameter.
+   * This parameter is deprecated. Use the `TagsScope` parameter instead.
    * 
-   * The tag key used to filter resources. The rule applies only to the resources with the specified tag key.
+   * The rule is effective only for resources that have the specified tag.
    * 
-   * >  This parameter applies only to a managed rule. You must configure the `TagKeyScope` and `TagValueScope` parameters at the same time.
+   * > This parameter applies only to managed rules. The `TagKeyScope` and `TagValueScope` parameters must be specified at the same time.
    * 
    * @example
    * ECS
@@ -340,11 +355,11 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   tagKeyScope?: string;
   /**
    * @remarks
-   * This parameter is deprecated. We recommend that you use the `TagsScope` parameter.
+   * This parameter is deprecated. Use the `TagsScope` parameter instead.
    * 
-   * The tag value used to filter resources. The rule applies only to the resources that use the specified tag value.
+   * The rule is effective only for resources that have the specified tag.
    * 
-   * >  This parameter applies only to a managed rule. You must configure the `TagKeyScope` and `TagValueScope` parameters at the same time.
+   * > This parameter applies only to managed rules. The `TagKeyScope` and `TagValueScope` parameters must be specified at the same time.
    * 
    * @example
    * test
@@ -354,12 +369,13 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   tagValueScope?: string;
   /**
    * @remarks
-   * The tag scope.
+   * The tags that are used to filter resources.
    */
   tagsScope?: UpdateConfigRuleRequestTagsScope[];
   static names(): { [key: string]: string } {
     return {
       clientToken: 'ClientToken',
+      conditions: 'Conditions',
       configRuleId: 'ConfigRuleId',
       configRuleName: 'ConfigRuleName',
       configRuleTriggerTypes: 'ConfigRuleTriggerTypes',
@@ -388,6 +404,7 @@ export class UpdateConfigRuleRequest extends $dara.Model {
   static types(): { [key: string]: any } {
     return {
       clientToken: 'string',
+      conditions: 'string',
       configRuleId: 'string',
       configRuleName: 'string',
       configRuleTriggerTypes: 'string',

package/src/models/UpdateConfigRuleResponseBody.ts

@@ -5,7 +5,7 @@ import * as $dara from '@darabonba/typescript';
 export class UpdateConfigRuleResponseBody extends $dara.Model {
   /**
    * @remarks
-   * The ID of the rule.
+   * The rule ID.
    * 
    * @example
    * cr-a260626622af0005****
@@ -13,7 +13,7 @@ export class UpdateConfigRuleResponseBody extends $dara.Model {
   configRuleId?: string;
   /**
    * @remarks
-   * The ID of the request.
+   * The request ID.
    * 
    * @example
    * 6EC7AED1-172F-42AE-9C12-295BC2ADB751