@volcengine/pulumi-volcenginecc 0.0.28 → 0.0.30

package/rocketmq/instance.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 import * as inputs from "../types/input";
 import * as outputs from "../types/output";
 /**
- * 消息队列 RocketMQ版是基于 Apache RocketMQ 构建的分布式消息中间件服务，完全兼容开源 RocketMQ 的各个组件与概念，同时具备低延迟、弹性高可靠、高吞吐等特性优势，业务代码无需改造，帮助用户快速迁移上云。
+ * RocketMQ Message Queue is a distributed messaging middleware service built on Apache RocketMQ. It is fully compatible with all open-source RocketMQ components and concepts, offering low latency, high elasticity and high reliability, and high throughput. No changes to business code are required, enabling users to quickly migrate to the cloud.
  *
  * ## Import
  *
@@ -27,125 +27,125 @@ export declare class Instance extends pulumi.CustomResource {
      */
     static isInstance(obj: any): obj is Instance;
     /**
-     * 实例所属的账号 ID。
+     * Account ID to which the instance belongs.
      */
     readonly accountId: pulumi.Output<string>;
     /**
-     * 实例绑定的白名单 ID 列表。绑定白名单后，仅配置在白名单中的 IP 地址与地址段才能访问此实例。如果实例未绑定任何白名单，表示禁止所有 IP 地址访问该实例。
+     * List of allowlist IDs bound to the instance. After binding an allowlist, only IP addresses and address ranges configured in the allowlist can access this instance. If no allowlist is bound to the instance, all IP addresses are denied access to the instance.
      */
     readonly allowListIds: pulumi.Output<string[]>;
     /**
-     * 是否已开启私网域名支持公网解析功能。true：已开启false：已关闭
+     * Whether private network domain name supports public resolution. true: enabled false: disabled
      */
     readonly applyPrivateDnsToPublic: pulumi.Output<boolean>;
     /**
-     * 实例规格更改时，是否自动创建队列。
+     * Whether to automatically create queues when the instance specification changes.
      */
     readonly autoScaleQueue: pulumi.Output<boolean>;
     /**
-     * 剩余可创建的分区数量。
+     * Remaining number of partitions that can be created.
      */
     readonly availableQueueNumber: pulumi.Output<number>;
     /**
-     * 实例的计费方式等计费信息。
+     * Billing method and related billing information for the instance.
      */
     readonly chargeDetail: pulumi.Output<outputs.rocketmq.InstanceChargeDetail>;
     /**
-     * 实例的计算规格。您可以在产品规格中查看目前在售的计算规格列表。
+     * Instance compute specification. You can view the currently available compute specifications in the product specifications list.
      */
     readonly computeSpec: pulumi.Output<string>;
     readonly connectionInfos: pulumi.Output<outputs.rocketmq.InstanceConnectionInfo[]>;
     /**
-     * 实例的创建时间。时间显示格式为YYYY-MM-DD'T'HH:MM:SS'Z'。
+     * Instance creation time. The time format is YYYY-MM-DD'T'HH:MM:SS'Z'.
      */
     readonly createTime: pulumi.Output<string>;
     /**
-     * EIP 的 ID。指定 EipId 表示开启实例的公网访问。EIP 提供独立的公网 IP 资源，包括公网 IP 地址与公网出口带宽服务。指定此参数开启公网访问后，公网地址将绑定您的弹性公网IP（EIP），费用由EIP收取。
+     * EIP ID. Specifying EipId enables public access for the instance. EIP provides independent public IP resources, including public IP addresses and outbound bandwidth services. After enabling public access by specifying this parameter, the public address will be bound to your Elastic IP (EIP), and fees will be charged for the EIP resource.
      */
     readonly eipId: pulumi.Output<string>;
     /**
-     * 是否使用 SSL 加密。
+     * Whether to use SSL encryption.
      */
     readonly enableSsl: pulumi.Output<boolean>;
     /**
-     * 消息在消息队列 RocketMQ版服务端的保留时长，超过保留时长的消息将被过期清理。单位为小时，取值范围为 1~72 小时。
+     * Message retention period on the RocketMQ Message Queue server. Messages exceeding the retention period will be expired and cleaned up. Unit: hours. Value range: 1–72 hours.
      */
     readonly fileReservedTime: pulumi.Output<number>;
     /**
-     * 实例的简单描述。长度范围为 1~128 个字符。
+     * Brief description of the instance. Length range: 1–128 characters.
      */
     readonly instanceDescription: pulumi.Output<string>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     readonly instanceId: pulumi.Output<string>;
     /**
-     * 实例的名称。 需满足以下要求：只能包含中文、字母、数字、下划线（_）和连字符（-）。不能以数字和连字符（-）开头。长度范围为 1~128 个字符。如果创建实例时未指定名称，则默认将实例 ID 作为实例名称。
+     * Instance name. Must meet the following requirements: can only contain Chinese characters, letters, numbers, underscores (_), and hyphens (-); cannot start with a number or hyphen (-); length must be 1–128 characters. If no name is specified when creating the instance, the instance ID will be used as the default name.
      */
     readonly instanceName: pulumi.Output<string>;
     /**
-     * 实例状态。
+     * Instance status.
      */
     readonly instanceStatus: pulumi.Output<string>;
     /**
-     * IP 版本， 可选直为 IPv4 或者 DualStack。
+     * IP version. Options are IPv4 or DualStack.
      */
     readonly ipVersionType: pulumi.Output<string>;
     /**
-     * 实例网络类型，固定为 PrivateNetwork。
+     * Instance network type, fixed as PrivateNetwork.
      */
     readonly networkTypes: pulumi.Output<string>;
     /**
-     * 产品配置信息。说明仅 RocketMQ 5.x 版本实例支持调整实例的 TPS 占比。
+     * Product configuration information. Note: Only RocketMQ 5.x instances support adjusting the TPS ratio for the instance.
      */
     readonly productInfo: pulumi.Output<outputs.rocketmq.InstanceProductInfo>;
     /**
-     * 当前创建的实例所属的 IAM 项目。若未设置，则会将新实例绑定到名为 default 的 IAM 项目中。
+     * The IAM project to which the newly created instance belongs. If not set, the new instance will be bound to the IAM project named 'default'.
      */
     readonly projectName: pulumi.Output<string>;
     /**
-     * 实例所在的地域 ID。
+     * Region ID where the instance is located.
      */
     readonly regionId: pulumi.Output<string>;
     /**
-     * 实例的公网连接策略，仅在开启公网访问时需要设置。支持设置为：enforcing：通过公网访问实例时，必须经由 SSL 认证。SSL 认证可实现数据的加密传输，相较于普通公网访问方式具备更高的安全性，但性能会有所下降。permissive：通过公网访问实例时，可以选择是否经由 SSL 认证。创建实例后，公网访问为开启状态时，不能修改 SSL 连接策略。如需修改，需要为实例关闭并重新开启公网访问，在重新开启时再次设置 SSL 连接策略。详细说明请参考设置公网访问与 SSL 认证策略。
+     * The instance's public network connection policy only needs to be set when public access is enabled. Supported settings are: enforcing: When accessing the instance via the public network, SSL authentication is required. SSL authentication enables encrypted data transmission, offering higher security compared to standard public access, but may reduce performance. permissive: When accessing the instance via the public network, SSL authentication is optional. After the instance is created and public access is enabled, the SSL connection policy cannot be modified. To change it, you must disable and re-enable public access for the instance, and set the SSL connection policy again when re-enabling. For details, see Setting Public Access and SSL Authentication Policy.
      */
     readonly sslMode: pulumi.Output<string>;
     /**
-     * 实例的存储空间。单位为 GiB，必须指定为 100 的倍数。取值范围取决于当前指定的计算规格。
+     * Instance storage space, measured in GiB and must be specified in multiples of 100. The value range depends on the currently selected compute specification.
      */
     readonly storageSpace: pulumi.Output<number>;
     /**
-     * 实例所在的 VPC 子网 ID。实例创建完成后，不可修改对应的私有网络和子网。创建实例时请谨慎操作。您可以调用私有网络（VPC）的 DescribeVpcs 接口查询可用的VPC和子网列表。
+     * VPC subnet ID where the instance resides. After the instance is created, the associated VPC and subnet cannot be modified. Please operate carefully when creating the instance. You can call the DescribeVpcs API of the VPC to query the available VPC and subnet list.
      */
     readonly subnetId: pulumi.Output<string>;
     readonly tags: pulumi.Output<outputs.rocketmq.InstanceTag[]>;
     /**
-     * 当前实例已经创建的消费组（Group）个数。
+     * Number of consumer groups (Group) currently created for the instance.
      */
     readonly usedGroupNumber: pulumi.Output<number>;
     /**
-     * 实例已经使用的队列数。
+     * Number of queues already used by the instance.
      */
     readonly usedQueueNumber: pulumi.Output<number>;
     /**
-     * 实例已用储空间。单位为 GiB。
+     * Used storage space for the instance, in GiB.
      */
     readonly usedStorageSpace: pulumi.Output<number>;
     /**
-     * 当前实例已创建的 Topic 个数。
+     * Number of topics created in the current instance.
      */
     readonly usedTopicNumber: pulumi.Output<number>;
     /**
-     * 支持的 RocketMQ 版本。当前支持的版本包括：4.8：兼容 RocketMQ 4.x 版本系列。5.x：兼容 RocketMQ 5.x 版本系列。目前 5.x 版本处于加白阶段，如需使用请联系技术支持申请开白。
+     * Supported RocketMQ versions. Currently supported versions include: 4.8: compatible with RocketMQ 4.x series. 5.x: compatible with RocketMQ 5.x series. The 5.x version is currently available by whitelist application. To use it, contact technical support to apply for access.
      */
     readonly version: pulumi.Output<string>;
     /**
-     * 实例所在的私有网络（VPC） ID。实例创建完成后，不可修改对应的私有网络和子网。创建实例时请谨慎操作。您可以调用私有网络（VPC）的 DescribeVpcs 接口查询可用的VPC和子网列表。
+     * VPC ID where the instance resides. After the instance is created, the associated VPC and subnet cannot be modified. Please operate carefully when creating the instance. You can call the DescribeVpcs API of the VPC to query the available VPC and subnet list.
      */
     readonly vpcId: pulumi.Output<string>;
     /**
-     * 实例所在的可用区 ID。消息队列 RocketMQ版实例支持跨 AZ 部署，查看指定可用区下提供哪些计算规格时，可以指定多个可用区。多个可用区 ID 之间以逗号（,）间隔。您可以调用 DescribeAvailabilityZones 查询当前提供服务的可用区列表。
+     * Availability zone ID where the instance is located. RocketMQ Message Queue instances support cross-AZ deployment. When viewing available compute specifications in a specified availability zone, you can specify multiple zones. Separate multiple availability zone IDs with commas (,). You can call DescribeAvailabilityZones to query the list of currently available zones.
      */
     readonly zoneId: pulumi.Output<string>;
     /**
@@ -162,125 +162,125 @@ export declare class Instance extends pulumi.CustomResource {
  */
 export interface InstanceState {
     /**
-     * 实例所属的账号 ID。
+     * Account ID to which the instance belongs.
      */
     accountId?: pulumi.Input<string>;
     /**
-     * 实例绑定的白名单 ID 列表。绑定白名单后，仅配置在白名单中的 IP 地址与地址段才能访问此实例。如果实例未绑定任何白名单，表示禁止所有 IP 地址访问该实例。
+     * List of allowlist IDs bound to the instance. After binding an allowlist, only IP addresses and address ranges configured in the allowlist can access this instance. If no allowlist is bound to the instance, all IP addresses are denied access to the instance.
      */
     allowListIds?: pulumi.Input<pulumi.Input<string>[]>;
     /**
-     * 是否已开启私网域名支持公网解析功能。true：已开启false：已关闭
+     * Whether private network domain name supports public resolution. true: enabled false: disabled
      */
     applyPrivateDnsToPublic?: pulumi.Input<boolean>;
     /**
-     * 实例规格更改时，是否自动创建队列。
+     * Whether to automatically create queues when the instance specification changes.
      */
     autoScaleQueue?: pulumi.Input<boolean>;
     /**
-     * 剩余可创建的分区数量。
+     * Remaining number of partitions that can be created.
      */
     availableQueueNumber?: pulumi.Input<number>;
     /**
-     * 实例的计费方式等计费信息。
+     * Billing method and related billing information for the instance.
      */
     chargeDetail?: pulumi.Input<inputs.rocketmq.InstanceChargeDetail>;
     /**
-     * 实例的计算规格。您可以在产品规格中查看目前在售的计算规格列表。
+     * Instance compute specification. You can view the currently available compute specifications in the product specifications list.
      */
     computeSpec?: pulumi.Input<string>;
     connectionInfos?: pulumi.Input<pulumi.Input<inputs.rocketmq.InstanceConnectionInfo>[]>;
     /**
-     * 实例的创建时间。时间显示格式为YYYY-MM-DD'T'HH:MM:SS'Z'。
+     * Instance creation time. The time format is YYYY-MM-DD'T'HH:MM:SS'Z'.
      */
     createTime?: pulumi.Input<string>;
     /**
-     * EIP 的 ID。指定 EipId 表示开启实例的公网访问。EIP 提供独立的公网 IP 资源，包括公网 IP 地址与公网出口带宽服务。指定此参数开启公网访问后，公网地址将绑定您的弹性公网IP（EIP），费用由EIP收取。
+     * EIP ID. Specifying EipId enables public access for the instance. EIP provides independent public IP resources, including public IP addresses and outbound bandwidth services. After enabling public access by specifying this parameter, the public address will be bound to your Elastic IP (EIP), and fees will be charged for the EIP resource.
      */
     eipId?: pulumi.Input<string>;
     /**
-     * 是否使用 SSL 加密。
+     * Whether to use SSL encryption.
      */
     enableSsl?: pulumi.Input<boolean>;
     /**
-     * 消息在消息队列 RocketMQ版服务端的保留时长，超过保留时长的消息将被过期清理。单位为小时，取值范围为 1~72 小时。
+     * Message retention period on the RocketMQ Message Queue server. Messages exceeding the retention period will be expired and cleaned up. Unit: hours. Value range: 1–72 hours.
      */
     fileReservedTime?: pulumi.Input<number>;
     /**
-     * 实例的简单描述。长度范围为 1~128 个字符。
+     * Brief description of the instance. Length range: 1–128 characters.
      */
     instanceDescription?: pulumi.Input<string>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     instanceId?: pulumi.Input<string>;
     /**
-     * 实例的名称。 需满足以下要求：只能包含中文、字母、数字、下划线（_）和连字符（-）。不能以数字和连字符（-）开头。长度范围为 1~128 个字符。如果创建实例时未指定名称，则默认将实例 ID 作为实例名称。
+     * Instance name. Must meet the following requirements: can only contain Chinese characters, letters, numbers, underscores (_), and hyphens (-); cannot start with a number or hyphen (-); length must be 1–128 characters. If no name is specified when creating the instance, the instance ID will be used as the default name.
      */
     instanceName?: pulumi.Input<string>;
     /**
-     * 实例状态。
+     * Instance status.
      */
     instanceStatus?: pulumi.Input<string>;
     /**
-     * IP 版本， 可选直为 IPv4 或者 DualStack。
+     * IP version. Options are IPv4 or DualStack.
      */
     ipVersionType?: pulumi.Input<string>;
     /**
-     * 实例网络类型，固定为 PrivateNetwork。
+     * Instance network type, fixed as PrivateNetwork.
      */
     networkTypes?: pulumi.Input<string>;
     /**
-     * 产品配置信息。说明仅 RocketMQ 5.x 版本实例支持调整实例的 TPS 占比。
+     * Product configuration information. Note: Only RocketMQ 5.x instances support adjusting the TPS ratio for the instance.
      */
     productInfo?: pulumi.Input<inputs.rocketmq.InstanceProductInfo>;
     /**
-     * 当前创建的实例所属的 IAM 项目。若未设置，则会将新实例绑定到名为 default 的 IAM 项目中。
+     * The IAM project to which the newly created instance belongs. If not set, the new instance will be bound to the IAM project named 'default'.
      */
     projectName?: pulumi.Input<string>;
     /**
-     * 实例所在的地域 ID。
+     * Region ID where the instance is located.
      */
     regionId?: pulumi.Input<string>;
     /**
-     * 实例的公网连接策略，仅在开启公网访问时需要设置。支持设置为：enforcing：通过公网访问实例时，必须经由 SSL 认证。SSL 认证可实现数据的加密传输，相较于普通公网访问方式具备更高的安全性，但性能会有所下降。permissive：通过公网访问实例时，可以选择是否经由 SSL 认证。创建实例后，公网访问为开启状态时，不能修改 SSL 连接策略。如需修改，需要为实例关闭并重新开启公网访问，在重新开启时再次设置 SSL 连接策略。详细说明请参考设置公网访问与 SSL 认证策略。
+     * The instance's public network connection policy only needs to be set when public access is enabled. Supported settings are: enforcing: When accessing the instance via the public network, SSL authentication is required. SSL authentication enables encrypted data transmission, offering higher security compared to standard public access, but may reduce performance. permissive: When accessing the instance via the public network, SSL authentication is optional. After the instance is created and public access is enabled, the SSL connection policy cannot be modified. To change it, you must disable and re-enable public access for the instance, and set the SSL connection policy again when re-enabling. For details, see Setting Public Access and SSL Authentication Policy.
      */
     sslMode?: pulumi.Input<string>;
     /**
-     * 实例的存储空间。单位为 GiB，必须指定为 100 的倍数。取值范围取决于当前指定的计算规格。
+     * Instance storage space, measured in GiB and must be specified in multiples of 100. The value range depends on the currently selected compute specification.
      */
     storageSpace?: pulumi.Input<number>;
     /**
-     * 实例所在的 VPC 子网 ID。实例创建完成后，不可修改对应的私有网络和子网。创建实例时请谨慎操作。您可以调用私有网络（VPC）的 DescribeVpcs 接口查询可用的VPC和子网列表。
+     * VPC subnet ID where the instance resides. After the instance is created, the associated VPC and subnet cannot be modified. Please operate carefully when creating the instance. You can call the DescribeVpcs API of the VPC to query the available VPC and subnet list.
      */
     subnetId?: pulumi.Input<string>;
     tags?: pulumi.Input<pulumi.Input<inputs.rocketmq.InstanceTag>[]>;
     /**
-     * 当前实例已经创建的消费组（Group）个数。
+     * Number of consumer groups (Group) currently created for the instance.
      */
     usedGroupNumber?: pulumi.Input<number>;
     /**
-     * 实例已经使用的队列数。
+     * Number of queues already used by the instance.
      */
     usedQueueNumber?: pulumi.Input<number>;
     /**
-     * 实例已用储空间。单位为 GiB。
+     * Used storage space for the instance, in GiB.
      */
     usedStorageSpace?: pulumi.Input<number>;
     /**
-     * 当前实例已创建的 Topic 个数。
+     * Number of topics created in the current instance.
      */
     usedTopicNumber?: pulumi.Input<number>;
     /**
-     * 支持的 RocketMQ 版本。当前支持的版本包括：4.8：兼容 RocketMQ 4.x 版本系列。5.x：兼容 RocketMQ 5.x 版本系列。目前 5.x 版本处于加白阶段，如需使用请联系技术支持申请开白。
+     * Supported RocketMQ versions. Currently supported versions include: 4.8: compatible with RocketMQ 4.x series. 5.x: compatible with RocketMQ 5.x series. The 5.x version is currently available by whitelist application. To use it, contact technical support to apply for access.
      */
     version?: pulumi.Input<string>;
     /**
-     * 实例所在的私有网络（VPC） ID。实例创建完成后，不可修改对应的私有网络和子网。创建实例时请谨慎操作。您可以调用私有网络（VPC）的 DescribeVpcs 接口查询可用的VPC和子网列表。
+     * VPC ID where the instance resides. After the instance is created, the associated VPC and subnet cannot be modified. Please operate carefully when creating the instance. You can call the DescribeVpcs API of the VPC to query the available VPC and subnet list.
      */
     vpcId?: pulumi.Input<string>;
     /**
-     * 实例所在的可用区 ID。消息队列 RocketMQ版实例支持跨 AZ 部署，查看指定可用区下提供哪些计算规格时，可以指定多个可用区。多个可用区 ID 之间以逗号（,）间隔。您可以调用 DescribeAvailabilityZones 查询当前提供服务的可用区列表。
+     * Availability zone ID where the instance is located. RocketMQ Message Queue instances support cross-AZ deployment. When viewing available compute specifications in a specified availability zone, you can specify multiple zones. Separate multiple availability zone IDs with commas (,). You can call DescribeAvailabilityZones to query the list of currently available zones.
      */
     zoneId?: pulumi.Input<string>;
 }
@@ -289,80 +289,80 @@ export interface InstanceState {
  */
 export interface InstanceArgs {
     /**
-     * 实例绑定的白名单 ID 列表。绑定白名单后，仅配置在白名单中的 IP 地址与地址段才能访问此实例。如果实例未绑定任何白名单，表示禁止所有 IP 地址访问该实例。
+     * List of allowlist IDs bound to the instance. After binding an allowlist, only IP addresses and address ranges configured in the allowlist can access this instance. If no allowlist is bound to the instance, all IP addresses are denied access to the instance.
      */
     allowListIds?: pulumi.Input<pulumi.Input<string>[]>;
     /**
-     * 实例规格更改时，是否自动创建队列。
+     * Whether to automatically create queues when the instance specification changes.
      */
     autoScaleQueue?: pulumi.Input<boolean>;
     /**
-     * 实例的计费方式等计费信息。
+     * Billing method and related billing information for the instance.
      */
     chargeDetail: pulumi.Input<inputs.rocketmq.InstanceChargeDetail>;
     /**
-     * 实例的计算规格。您可以在产品规格中查看目前在售的计算规格列表。
+     * Instance compute specification. You can view the currently available compute specifications in the product specifications list.
      */
     computeSpec: pulumi.Input<string>;
     /**
-     * EIP 的 ID。指定 EipId 表示开启实例的公网访问。EIP 提供独立的公网 IP 资源，包括公网 IP 地址与公网出口带宽服务。指定此参数开启公网访问后，公网地址将绑定您的弹性公网IP（EIP），费用由EIP收取。
+     * EIP ID. Specifying EipId enables public access for the instance. EIP provides independent public IP resources, including public IP addresses and outbound bandwidth services. After enabling public access by specifying this parameter, the public address will be bound to your Elastic IP (EIP), and fees will be charged for the EIP resource.
      */
     eipId?: pulumi.Input<string>;
     /**
-     * 是否使用 SSL 加密。
+     * Whether to use SSL encryption.
      */
     enableSsl?: pulumi.Input<boolean>;
     /**
-     * 消息在消息队列 RocketMQ版服务端的保留时长，超过保留时长的消息将被过期清理。单位为小时，取值范围为 1~72 小时。
+     * Message retention period on the RocketMQ Message Queue server. Messages exceeding the retention period will be expired and cleaned up. Unit: hours. Value range: 1–72 hours.
      */
     fileReservedTime: pulumi.Input<number>;
     /**
-     * 实例的简单描述。长度范围为 1~128 个字符。
+     * Brief description of the instance. Length range: 1–128 characters.
      */
     instanceDescription?: pulumi.Input<string>;
     /**
-     * 实例的名称。 需满足以下要求：只能包含中文、字母、数字、下划线（_）和连字符（-）。不能以数字和连字符（-）开头。长度范围为 1~128 个字符。如果创建实例时未指定名称，则默认将实例 ID 作为实例名称。
+     * Instance name. Must meet the following requirements: can only contain Chinese characters, letters, numbers, underscores (_), and hyphens (-); cannot start with a number or hyphen (-); length must be 1–128 characters. If no name is specified when creating the instance, the instance ID will be used as the default name.
      */
     instanceName?: pulumi.Input<string>;
     /**
-     * IP 版本， 可选直为 IPv4 或者 DualStack。
+     * IP version. Options are IPv4 or DualStack.
      */
     ipVersionType?: pulumi.Input<string>;
     /**
-     * 实例网络类型，固定为 PrivateNetwork。
+     * Instance network type, fixed as PrivateNetwork.
      */
     networkTypes: pulumi.Input<string>;
     /**
-     * 产品配置信息。说明仅 RocketMQ 5.x 版本实例支持调整实例的 TPS 占比。
+     * Product configuration information. Note: Only RocketMQ 5.x instances support adjusting the TPS ratio for the instance.
      */
     productInfo?: pulumi.Input<inputs.rocketmq.InstanceProductInfo>;
     /**
-     * 当前创建的实例所属的 IAM 项目。若未设置，则会将新实例绑定到名为 default 的 IAM 项目中。
+     * The IAM project to which the newly created instance belongs. If not set, the new instance will be bound to the IAM project named 'default'.
      */
     projectName?: pulumi.Input<string>;
     /**
-     * 实例的公网连接策略，仅在开启公网访问时需要设置。支持设置为：enforcing：通过公网访问实例时，必须经由 SSL 认证。SSL 认证可实现数据的加密传输，相较于普通公网访问方式具备更高的安全性，但性能会有所下降。permissive：通过公网访问实例时，可以选择是否经由 SSL 认证。创建实例后，公网访问为开启状态时，不能修改 SSL 连接策略。如需修改，需要为实例关闭并重新开启公网访问，在重新开启时再次设置 SSL 连接策略。详细说明请参考设置公网访问与 SSL 认证策略。
+     * The instance's public network connection policy only needs to be set when public access is enabled. Supported settings are: enforcing: When accessing the instance via the public network, SSL authentication is required. SSL authentication enables encrypted data transmission, offering higher security compared to standard public access, but may reduce performance. permissive: When accessing the instance via the public network, SSL authentication is optional. After the instance is created and public access is enabled, the SSL connection policy cannot be modified. To change it, you must disable and re-enable public access for the instance, and set the SSL connection policy again when re-enabling. For details, see Setting Public Access and SSL Authentication Policy.
      */
     sslMode?: pulumi.Input<string>;
     /**
-     * 实例的存储空间。单位为 GiB，必须指定为 100 的倍数。取值范围取决于当前指定的计算规格。
+     * Instance storage space, measured in GiB and must be specified in multiples of 100. The value range depends on the currently selected compute specification.
      */
     storageSpace: pulumi.Input<number>;
     /**
-     * 实例所在的 VPC 子网 ID。实例创建完成后，不可修改对应的私有网络和子网。创建实例时请谨慎操作。您可以调用私有网络（VPC）的 DescribeVpcs 接口查询可用的VPC和子网列表。
+     * VPC subnet ID where the instance resides. After the instance is created, the associated VPC and subnet cannot be modified. Please operate carefully when creating the instance. You can call the DescribeVpcs API of the VPC to query the available VPC and subnet list.
      */
     subnetId: pulumi.Input<string>;
     tags?: pulumi.Input<pulumi.Input<inputs.rocketmq.InstanceTag>[]>;
     /**
-     * 支持的 RocketMQ 版本。当前支持的版本包括：4.8：兼容 RocketMQ 4.x 版本系列。5.x：兼容 RocketMQ 5.x 版本系列。目前 5.x 版本处于加白阶段，如需使用请联系技术支持申请开白。
+     * Supported RocketMQ versions. Currently supported versions include: 4.8: compatible with RocketMQ 4.x series. 5.x: compatible with RocketMQ 5.x series. The 5.x version is currently available by whitelist application. To use it, contact technical support to apply for access.
      */
     version: pulumi.Input<string>;
     /**
-     * 实例所在的私有网络（VPC） ID。实例创建完成后，不可修改对应的私有网络和子网。创建实例时请谨慎操作。您可以调用私有网络（VPC）的 DescribeVpcs 接口查询可用的VPC和子网列表。
+     * VPC ID where the instance resides. After the instance is created, the associated VPC and subnet cannot be modified. Please operate carefully when creating the instance. You can call the DescribeVpcs API of the VPC to query the available VPC and subnet list.
      */
     vpcId: pulumi.Input<string>;
     /**
-     * 实例所在的可用区 ID。消息队列 RocketMQ版实例支持跨 AZ 部署，查看指定可用区下提供哪些计算规格时，可以指定多个可用区。多个可用区 ID 之间以逗号（,）间隔。您可以调用 DescribeAvailabilityZones 查询当前提供服务的可用区列表。
+     * Availability zone ID where the instance is located. RocketMQ Message Queue instances support cross-AZ deployment. When viewing available compute specifications in a specified availability zone, you can specify multiple zones. Separate multiple availability zone IDs with commas (,). You can call DescribeAvailabilityZones to query the list of currently available zones.
      */
     zoneId: pulumi.Input<string>;
 }

package/rocketmq/instance.js

@@ -6,7 +6,7 @@ exports.Instance = void 0;
 const pulumi = require("@pulumi/pulumi");
 const utilities = require("../utilities");
 /**
- * 消息队列 RocketMQ版是基于 Apache RocketMQ 构建的分布式消息中间件服务，完全兼容开源 RocketMQ 的各个组件与概念，同时具备低延迟、弹性高可靠、高吞吐等特性优势，业务代码无需改造，帮助用户快速迁移上云。
+ * RocketMQ Message Queue is a distributed messaging middleware service built on Apache RocketMQ. It is fully compatible with all open-source RocketMQ components and concepts, offering low latency, high elasticity and high reliability, and high throughput. No changes to business code are required, enabling users to quickly migrate to the cloud.
  *
  * ## Import
  *

package/rocketmq/topic.d.ts

@@ -2,7 +2,7 @@ import * as pulumi from "@pulumi/pulumi";
 import * as inputs from "../types/input";
 import * as outputs from "../types/output";
 /**
- * 在RocketMQ 实例中，Topic 是消息发送与接收的基本单元，消息队列 RocketMQ版通过 Topic 对各类消息进行分类管理。消息的生产者将消息发送到 RocketMQ Topic 中，而消息的消费者则通过订阅该 RocketMQ Topic 来消费消息。
+ * In a RocketMQ instance, a Topic is the basic unit for sending and consuming messages. RocketMQ Message Queue categorizes and manages different types of messages using Topics. Producers send messages to RocketMQ Topics, and consumers consume messages by subscribing to those Topics.
  *
  * ## Import
  *
@@ -28,38 +28,38 @@ export declare class Topic extends pulumi.CustomResource {
     static isInstance(obj: any): obj is Topic;
     readonly accessPolicies: pulumi.Output<outputs.rocketmq.TopicAccessPolicy[]>;
     /**
-     * Topic 创建时间。
+     * Topic creation time.
      */
     readonly createdTime: pulumi.Output<string>;
     /**
-     * Topic 的描述信息，长度为 0~128 个字符。
+     * Topic description, length: 0–128 characters.
      */
     readonly description: pulumi.Output<string>;
     readonly groupsInfos: pulumi.Output<outputs.rocketmq.TopicGroupsInfo[]>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     readonly instanceId: pulumi.Output<string>;
     /**
-     * 实例名称。
+     * Instance name.
      */
     readonly instanceName: pulumi.Output<string>;
     /**
-     * 消息类型。设置此参数表示根据指定的消息类型筛选 Topic 列表。取值说明如下：0：普通消息。1：事务消息。2：分区顺序消息。3：全局顺序消息。4：延时消息。
+     * Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
      */
     readonly messageType: pulumi.Output<number>;
     /**
-     * 设置当前 Topic 的队列数量，最大不可超过当前实例剩余可用队列数。每个实例规格的队列数量限制请参考产品规格。在 4.x 版本实例中创建 Topic 时，请参考以下说明设置队列数：全局顺序类型的 Topic 队列数默认为 1。其他类型 Topic 的队列数和计算规格有关，n3 及以下规格的队列数默认为 6，n3 以上规格的队列数默认是 broker 组数的两倍。队列数建议设置为计算节点数的倍数，否则可能造成不同 Broker 之间数据不均衡。例如规格 rocketmq.n3.x2.medium 的计算节点数为 3，队列数建议设置为 3 的倍数，即 3、6、9 等。在 5.x 版本实例中创建 Topic 时，请参考以下说明设置队列数：全局顺序类型的 Topic 队列数默认为 1。其他类型 Topic 的队列数默认是 broker 组数的两倍。非顺序场景性能不受队列个数影响，更多队列仅用于提升顺序消费并发性能。
+     * Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
      */
     readonly queueNumber: pulumi.Output<number>;
     readonly queuesInfos: pulumi.Output<outputs.rocketmq.TopicQueuesInfo[]>;
     readonly readAccessPolicies: pulumi.Output<outputs.rocketmq.TopicReadAccessPolicy[]>;
     /**
-     * 服务状态。Creating：创建中，Running：运行中，Deleting：删除中，Abnormal：异常，Updating：更新中。
+     * Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
      */
     readonly serviceStatus: pulumi.Output<string>;
     /**
-     * Topic 的名称。命名规则如下：长度为 3~100 个字符。只能包含英文、数字、连字符（-）以及下划线（*）。Topic 名称中不可包含以下保留字符或特殊前缀。保留字符：RMQ*SYS*TRANS*OP*HALF*TOPIC、BenchmarkTest、TBW102、OFFSET*MOVED*EVENT、SELF*TEST*TOPIC、RMQ*SYS*TRANS*HALF*TOPIC、SCHEDULE*TOPIC*XXXX、RMQ*SYS*TRACE*TOPIC。特殊前缀：rocketmq-broker-、%RETRY%、rmq*sys_、%DLQ%。
+     * Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores (*) are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQ*SYS*TRANS*OP*HALF*TOPIC, BenchmarkTest, TBW102, OFFSET*MOVED*EVENT, SELF*TEST*TOPIC, RMQ*SYS*TRANS*HALF*TOPIC, SCHEDULE*TOPIC*XXXX, RMQ*SYS*TRACE*TOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmq*sys_, %DLQ%.
      */
     readonly topicName: pulumi.Output<string>;
     /**
@@ -77,38 +77,38 @@ export declare class Topic extends pulumi.CustomResource {
 export interface TopicState {
     accessPolicies?: pulumi.Input<pulumi.Input<inputs.rocketmq.TopicAccessPolicy>[]>;
     /**
-     * Topic 创建时间。
+     * Topic creation time.
      */
     createdTime?: pulumi.Input<string>;
     /**
-     * Topic 的描述信息，长度为 0~128 个字符。
+     * Topic description, length: 0–128 characters.
      */
     description?: pulumi.Input<string>;
     groupsInfos?: pulumi.Input<pulumi.Input<inputs.rocketmq.TopicGroupsInfo>[]>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     instanceId?: pulumi.Input<string>;
     /**
-     * 实例名称。
+     * Instance name.
      */
     instanceName?: pulumi.Input<string>;
     /**
-     * 消息类型。设置此参数表示根据指定的消息类型筛选 Topic 列表。取值说明如下：0：普通消息。1：事务消息。2：分区顺序消息。3：全局顺序消息。4：延时消息。
+     * Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
      */
     messageType?: pulumi.Input<number>;
     /**
-     * 设置当前 Topic 的队列数量，最大不可超过当前实例剩余可用队列数。每个实例规格的队列数量限制请参考产品规格。在 4.x 版本实例中创建 Topic 时，请参考以下说明设置队列数：全局顺序类型的 Topic 队列数默认为 1。其他类型 Topic 的队列数和计算规格有关，n3 及以下规格的队列数默认为 6，n3 以上规格的队列数默认是 broker 组数的两倍。队列数建议设置为计算节点数的倍数，否则可能造成不同 Broker 之间数据不均衡。例如规格 rocketmq.n3.x2.medium 的计算节点数为 3，队列数建议设置为 3 的倍数，即 3、6、9 等。在 5.x 版本实例中创建 Topic 时，请参考以下说明设置队列数：全局顺序类型的 Topic 队列数默认为 1。其他类型 Topic 的队列数默认是 broker 组数的两倍。非顺序场景性能不受队列个数影响，更多队列仅用于提升顺序消费并发性能。
+     * Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
      */
     queueNumber?: pulumi.Input<number>;
     queuesInfos?: pulumi.Input<pulumi.Input<inputs.rocketmq.TopicQueuesInfo>[]>;
     readAccessPolicies?: pulumi.Input<pulumi.Input<inputs.rocketmq.TopicReadAccessPolicy>[]>;
     /**
-     * 服务状态。Creating：创建中，Running：运行中，Deleting：删除中，Abnormal：异常，Updating：更新中。
+     * Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
      */
     serviceStatus?: pulumi.Input<string>;
     /**
-     * Topic 的名称。命名规则如下：长度为 3~100 个字符。只能包含英文、数字、连字符（-）以及下划线（*）。Topic 名称中不可包含以下保留字符或特殊前缀。保留字符：RMQ*SYS*TRANS*OP*HALF*TOPIC、BenchmarkTest、TBW102、OFFSET*MOVED*EVENT、SELF*TEST*TOPIC、RMQ*SYS*TRANS*HALF*TOPIC、SCHEDULE*TOPIC*XXXX、RMQ*SYS*TRACE*TOPIC。特殊前缀：rocketmq-broker-、%RETRY%、rmq*sys_、%DLQ%。
+     * Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores (*) are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQ*SYS*TRANS*OP*HALF*TOPIC, BenchmarkTest, TBW102, OFFSET*MOVED*EVENT, SELF*TEST*TOPIC, RMQ*SYS*TRANS*HALF*TOPIC, SCHEDULE*TOPIC*XXXX, RMQ*SYS*TRACE*TOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmq*sys_, %DLQ%.
      */
     topicName?: pulumi.Input<string>;
 }
@@ -118,23 +118,23 @@ export interface TopicState {
 export interface TopicArgs {
     accessPolicies?: pulumi.Input<pulumi.Input<inputs.rocketmq.TopicAccessPolicy>[]>;
     /**
-     * Topic 的描述信息，长度为 0~128 个字符。
+     * Topic description, length: 0–128 characters.
      */
     description?: pulumi.Input<string>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     instanceId: pulumi.Input<string>;
     /**
-     * 消息类型。设置此参数表示根据指定的消息类型筛选 Topic 列表。取值说明如下：0：普通消息。1：事务消息。2：分区顺序消息。3：全局顺序消息。4：延时消息。
+     * Message type. Set this parameter to filter the Topic list by the specified message type. Value description: 0: Normal message. 1: Transaction message. 2: Partitioned ordered message. 3: Globally ordered message. 4: Delayed message.
      */
     messageType: pulumi.Input<number>;
     /**
-     * 设置当前 Topic 的队列数量，最大不可超过当前实例剩余可用队列数。每个实例规格的队列数量限制请参考产品规格。在 4.x 版本实例中创建 Topic 时，请参考以下说明设置队列数：全局顺序类型的 Topic 队列数默认为 1。其他类型 Topic 的队列数和计算规格有关，n3 及以下规格的队列数默认为 6，n3 以上规格的队列数默认是 broker 组数的两倍。队列数建议设置为计算节点数的倍数，否则可能造成不同 Broker 之间数据不均衡。例如规格 rocketmq.n3.x2.medium 的计算节点数为 3，队列数建议设置为 3 的倍数，即 3、6、9 等。在 5.x 版本实例中创建 Topic 时，请参考以下说明设置队列数：全局顺序类型的 Topic 队列数默认为 1。其他类型 Topic 的队列数默认是 broker 组数的两倍。非顺序场景性能不受队列个数影响，更多队列仅用于提升顺序消费并发性能。
+     * Set the number of queues for the current Topic. The maximum cannot exceed the remaining available queues for the current instance. For queue limits per instance specification, refer to the product specifications. When creating a Topic in a 4.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the queue number depends on the compute specification. For n3 and below, the default is 6; for above n3, the default is twice the number of broker groups. It is recommended to set the queue number as a multiple of the number of compute nodes to avoid data imbalance across Brokers. For example, for the rocketmq.n3.x2.medium specification with 3 compute nodes, set the queue number to a multiple of 3, such as 3, 6, or 9. When creating a Topic in a 5.x version instance, set the number of queues as follows: For globally ordered Topics, the default queue number is 1. For other Topic types, the default is twice the number of broker groups. In non-ordered scenarios, performance is not affected by the number of queues; more queues only improve concurrent performance for ordered consumption.
      */
     queueNumber: pulumi.Input<number>;
     /**
-     * Topic 的名称。命名规则如下：长度为 3~100 个字符。只能包含英文、数字、连字符（-）以及下划线（*）。Topic 名称中不可包含以下保留字符或特殊前缀。保留字符：RMQ*SYS*TRANS*OP*HALF*TOPIC、BenchmarkTest、TBW102、OFFSET*MOVED*EVENT、SELF*TEST*TOPIC、RMQ*SYS*TRANS*HALF*TOPIC、SCHEDULE*TOPIC*XXXX、RMQ*SYS*TRACE*TOPIC。特殊前缀：rocketmq-broker-、%RETRY%、rmq*sys_、%DLQ%。
+     * Topic name. Naming rules: Length must be 3–100 characters. Only English letters, numbers, hyphens (-), and underscores (*) are allowed. Topic names cannot contain the following reserved characters or special prefixes. Reserved characters: RMQ*SYS*TRANS*OP*HALF*TOPIC, BenchmarkTest, TBW102, OFFSET*MOVED*EVENT, SELF*TEST*TOPIC, RMQ*SYS*TRANS*HALF*TOPIC, SCHEDULE*TOPIC*XXXX, RMQ*SYS*TRACE*TOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmq*sys_, %DLQ%.
      */
     topicName: pulumi.Input<string>;
 }

package/rocketmq/topic.js

@@ -6,7 +6,7 @@ exports.Topic = void 0;
 const pulumi = require("@pulumi/pulumi");
 const utilities = require("../utilities");
 /**
- * 在RocketMQ 实例中，Topic 是消息发送与接收的基本单元，消息队列 RocketMQ版通过 Topic 对各类消息进行分类管理。消息的生产者将消息发送到 RocketMQ Topic 中，而消息的消费者则通过订阅该 RocketMQ Topic 来消费消息。
+ * In a RocketMQ instance, a Topic is the basic unit for sending and consuming messages. RocketMQ Message Queue categorizes and manages different types of messages using Topics. Producers send messages to RocketMQ Topics, and consumers consume messages by subscribing to those Topics.
  *
  * ## Import
  *