@volcengine/pulumi-volcenginecc 0.0.28 → 0.0.29

package/kafka/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";
 /**
- * Topic即消息的主题，用于分类消息。支持 Topic 级别的资源管理，即 Topic 的创建、查看与删除等操作。
+ * Topic refers to the message subject and is used to categorize messages. Supports resource management at the Topic level, including creating, viewing, and deleting Topics.
  *
  * ## Import
  *
@@ -28,56 +28,56 @@ export declare class Topic extends pulumi.CustomResource {
     static isInstance(obj: any): obj is Topic;
     readonly accessPolicies: pulumi.Output<outputs.kafka.TopicAccessPolicy[]>;
     /**
-     * 待创建的Topic默认是否对所有用户都开启读写权限。true：（默认）所有用户都具备此 Topic 的读写权限。false：并非所有用户都具备此 Topic 的读写权限。默认情况下，用户对于此 Topic 的权限沿用用户的默认权限，如果默认权限不满足需求，您也可以通过 AccessPolicies 指定某个用户对于此 Topic 的自定义权限。
+     * Whether read/write permissions are enabled by default for all users on the Topic to be created. true: (default) All users have read/write permissions for this Topic. false: Not all users have read/write permissions for this Topic. By default, users inherit their default permissions for this Topic. If the default permissions do not meet your requirements, you can specify custom permissions for a user on this Topic through AccessPolicies.
      */
     readonly allAuthority: pulumi.Output<boolean>;
     /**
-     * Topic 的消息清理策略，支持以下三种取值方式：[delete]：默认的消息清理策略。在磁盘容量充足的情况下，保留在最长保留时间范围内的消息；在磁盘容量不足时，将提前删除旧消息，以保证服务可用性。[compact]：COMPACT 消息清理策略针对每个消息的 Key 进行整合，对于有相同 Key 的消息，只保留最新的 value 值，旧的记录则会被清除。[delete,compact]：同时配置 DELETE 和 COMPACT 两种消息清理策略。只要消息满足任一条清理策略时，都将被清除。
+     * Topic message cleanup policy supports the following three options: [delete]: The default message cleanup policy. When disk space is sufficient, messages are retained within the maximum retention period; when disk space is insufficient, old messages are deleted early to ensure service availability. [compact]: The COMPACT message cleanup policy consolidates messages by Key, retaining only the latest value for messages with the same Key, and removing older records. [delete,compact]: Configures both DELETE and COMPACT message cleanup policies. Messages will be deleted as soon as they meet any of the cleanup criteria.
      */
     readonly cleanupPolicies: pulumi.Output<string[]>;
     /**
-     * Topic 的创建时间。
+     * Topic creation time.
      */
     readonly createdTime: pulumi.Output<string>;
     /**
-     * Topic 的描述信息。长度不超过 128 个字符。
+     * Topic description. Maximum length: 128 characters.
      */
     readonly description: pulumi.Output<string>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     readonly instanceId: pulumi.Output<string>;
     /**
-     * 消息保留时长，单位小时。Topic维度的消息保留时长，取值范围：1   - 2160小时（90天）。
+     * Message retention period, in hours. The retention period at the Topic level ranges from 1 to 2160 hours (90 days).
      */
     readonly logRetentionHours: pulumi.Output<number>;
     /**
-     * Topic 级别的参数配置。Parameters 参数说明 MinInsyncReplicaNumber:2：最小同步副本个数。当同步副本个数小于配置值时，消息将无法写入对应 Topic。配置值越大，数据可靠性增加，但是可用性将会降低。默认值为副本数减 1。考虑到 Topic 的可用性，建议设置为副本数减 1。MessageMaxByte:12：最大消息大小。单位为 MB，取值范围为 1～12。默认沿用实例的最大消息大小设置。LogRetentionHours:72：消息保留时长。单位为小时，取值范围为 0～2160，即消息最久保留 90 天。默认沿用实例的消息保留时长设置。
+     * Topic-level parameter configuration. Parameters description MinInsyncReplicaNumber:2: Minimum number of in-sync replicas. If the number of in-sync replicas is less than the configured value, messages cannot be written to the Topic. Higher values increase data reliability but reduce availability. The default is replica count minus 1. For Topic availability, it is recommended to set this to replica count minus 1. MessageMaxByte:12: Maximum message size, in MB, range 1–12. By default, inherits the instance's maximum message size setting. LogRetentionHours:72: Message retention period, in hours, range 0–2160 (up to 90 days). By default, inherits the instance's message retention period setting.
      */
     readonly parameters: pulumi.Output<string>;
     /**
-     * Topic 分区数。取值范围为 1~300，如果实例中已创建了其他 Topic，则所有 Topic 的分区数之和不超过该实例的分区数上限。如果分区数无法满足业务需求，您可以购买更多分区，提升实例的分区数量上限。
+     * Number of Topic partitions. The range is 1–300. If other Topics have already been created in the instance, the total number of partitions across all Topics must not exceed the partition limit of the instance. If the number of partitions does not meet your business needs, you can purchase more partitions to increase the partition limit of the instance.
      */
     readonly partitionNumber: pulumi.Output<number>;
     /**
-     * Topic 副本个数。可设置为为 2 或 3，默认值为 3。
+     * Number of Topic replicas. Can be set to 2 or 3; the default is 3.
      */
     readonly replicaNumber: pulumi.Output<number>;
     /**
-     * Topic 的状态。
+     * Topic status.
      */
     readonly status: pulumi.Output<string>;
     readonly tags: pulumi.Output<outputs.kafka.TopicTag[]>;
     /**
-     * 待创建的 Topic 名称。3～64 个字符。必须以英文或数字开头。支持的字符包括英文、数字、连字符（-）、下划线（_）和英文句号（.）。
+     * Name of the Topic to be created. 3–64 characters. Must start with a letter or number. Supported characters include letters, numbers, hyphens (-), underscores (_), and periods (.).
      */
     readonly topicName: pulumi.Output<string>;
     /**
-     * 当前 Topic 总数据量占实例总存储空间的比例，控制台页面显示为保留两位小数的百分数。
+     * The current Topic data size as a percentage of the instance's total storage space. Displayed on the console as a percentage with two decimal places.
      */
     readonly usedStoragePercentageInInstance: pulumi.Output<number>;
     /**
-     * 当前 Topic 已使用的总存储空间大小。
+     * Total storage space currently used by the Topic.
      */
     readonly usedStorageSpaceInBytes: pulumi.Output<number>;
     /**
@@ -95,56 +95,56 @@ export declare class Topic extends pulumi.CustomResource {
 export interface TopicState {
     accessPolicies?: pulumi.Input<pulumi.Input<inputs.kafka.TopicAccessPolicy>[]>;
     /**
-     * 待创建的Topic默认是否对所有用户都开启读写权限。true：（默认）所有用户都具备此 Topic 的读写权限。false：并非所有用户都具备此 Topic 的读写权限。默认情况下，用户对于此 Topic 的权限沿用用户的默认权限，如果默认权限不满足需求，您也可以通过 AccessPolicies 指定某个用户对于此 Topic 的自定义权限。
+     * Whether read/write permissions are enabled by default for all users on the Topic to be created. true: (default) All users have read/write permissions for this Topic. false: Not all users have read/write permissions for this Topic. By default, users inherit their default permissions for this Topic. If the default permissions do not meet your requirements, you can specify custom permissions for a user on this Topic through AccessPolicies.
      */
     allAuthority?: pulumi.Input<boolean>;
     /**
-     * Topic 的消息清理策略，支持以下三种取值方式：[delete]：默认的消息清理策略。在磁盘容量充足的情况下，保留在最长保留时间范围内的消息；在磁盘容量不足时，将提前删除旧消息，以保证服务可用性。[compact]：COMPACT 消息清理策略针对每个消息的 Key 进行整合，对于有相同 Key 的消息，只保留最新的 value 值，旧的记录则会被清除。[delete,compact]：同时配置 DELETE 和 COMPACT 两种消息清理策略。只要消息满足任一条清理策略时，都将被清除。
+     * Topic message cleanup policy supports the following three options: [delete]: The default message cleanup policy. When disk space is sufficient, messages are retained within the maximum retention period; when disk space is insufficient, old messages are deleted early to ensure service availability. [compact]: The COMPACT message cleanup policy consolidates messages by Key, retaining only the latest value for messages with the same Key, and removing older records. [delete,compact]: Configures both DELETE and COMPACT message cleanup policies. Messages will be deleted as soon as they meet any of the cleanup criteria.
      */
     cleanupPolicies?: pulumi.Input<pulumi.Input<string>[]>;
     /**
-     * Topic 的创建时间。
+     * Topic creation time.
      */
     createdTime?: pulumi.Input<string>;
     /**
-     * Topic 的描述信息。长度不超过 128 个字符。
+     * Topic description. Maximum length: 128 characters.
      */
     description?: pulumi.Input<string>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     instanceId?: pulumi.Input<string>;
     /**
-     * 消息保留时长，单位小时。Topic维度的消息保留时长，取值范围：1   - 2160小时（90天）。
+     * Message retention period, in hours. The retention period at the Topic level ranges from 1 to 2160 hours (90 days).
      */
     logRetentionHours?: pulumi.Input<number>;
     /**
-     * Topic 级别的参数配置。Parameters 参数说明 MinInsyncReplicaNumber:2：最小同步副本个数。当同步副本个数小于配置值时，消息将无法写入对应 Topic。配置值越大，数据可靠性增加，但是可用性将会降低。默认值为副本数减 1。考虑到 Topic 的可用性，建议设置为副本数减 1。MessageMaxByte:12：最大消息大小。单位为 MB，取值范围为 1～12。默认沿用实例的最大消息大小设置。LogRetentionHours:72：消息保留时长。单位为小时，取值范围为 0～2160，即消息最久保留 90 天。默认沿用实例的消息保留时长设置。
+     * Topic-level parameter configuration. Parameters description MinInsyncReplicaNumber:2: Minimum number of in-sync replicas. If the number of in-sync replicas is less than the configured value, messages cannot be written to the Topic. Higher values increase data reliability but reduce availability. The default is replica count minus 1. For Topic availability, it is recommended to set this to replica count minus 1. MessageMaxByte:12: Maximum message size, in MB, range 1–12. By default, inherits the instance's maximum message size setting. LogRetentionHours:72: Message retention period, in hours, range 0–2160 (up to 90 days). By default, inherits the instance's message retention period setting.
      */
     parameters?: pulumi.Input<string>;
     /**
-     * Topic 分区数。取值范围为 1~300，如果实例中已创建了其他 Topic，则所有 Topic 的分区数之和不超过该实例的分区数上限。如果分区数无法满足业务需求，您可以购买更多分区，提升实例的分区数量上限。
+     * Number of Topic partitions. The range is 1–300. If other Topics have already been created in the instance, the total number of partitions across all Topics must not exceed the partition limit of the instance. If the number of partitions does not meet your business needs, you can purchase more partitions to increase the partition limit of the instance.
      */
     partitionNumber?: pulumi.Input<number>;
     /**
-     * Topic 副本个数。可设置为为 2 或 3，默认值为 3。
+     * Number of Topic replicas. Can be set to 2 or 3; the default is 3.
      */
     replicaNumber?: pulumi.Input<number>;
     /**
-     * Topic 的状态。
+     * Topic status.
      */
     status?: pulumi.Input<string>;
     tags?: pulumi.Input<pulumi.Input<inputs.kafka.TopicTag>[]>;
     /**
-     * 待创建的 Topic 名称。3～64 个字符。必须以英文或数字开头。支持的字符包括英文、数字、连字符（-）、下划线（_）和英文句号（.）。
+     * Name of the Topic to be created. 3–64 characters. Must start with a letter or number. Supported characters include letters, numbers, hyphens (-), underscores (_), and periods (.).
      */
     topicName?: pulumi.Input<string>;
     /**
-     * 当前 Topic 总数据量占实例总存储空间的比例，控制台页面显示为保留两位小数的百分数。
+     * The current Topic data size as a percentage of the instance's total storage space. Displayed on the console as a percentage with two decimal places.
      */
     usedStoragePercentageInInstance?: pulumi.Input<number>;
     /**
-     * 当前 Topic 已使用的总存储空间大小。
+     * Total storage space currently used by the Topic.
      */
     usedStorageSpaceInBytes?: pulumi.Input<number>;
 }
@@ -154,36 +154,36 @@ export interface TopicState {
 export interface TopicArgs {
     accessPolicies?: pulumi.Input<pulumi.Input<inputs.kafka.TopicAccessPolicy>[]>;
     /**
-     * 待创建的Topic默认是否对所有用户都开启读写权限。true：（默认）所有用户都具备此 Topic 的读写权限。false：并非所有用户都具备此 Topic 的读写权限。默认情况下，用户对于此 Topic 的权限沿用用户的默认权限，如果默认权限不满足需求，您也可以通过 AccessPolicies 指定某个用户对于此 Topic 的自定义权限。
+     * Whether read/write permissions are enabled by default for all users on the Topic to be created. true: (default) All users have read/write permissions for this Topic. false: Not all users have read/write permissions for this Topic. By default, users inherit their default permissions for this Topic. If the default permissions do not meet your requirements, you can specify custom permissions for a user on this Topic through AccessPolicies.
      */
     allAuthority?: pulumi.Input<boolean>;
     /**
-     * Topic 的消息清理策略，支持以下三种取值方式：[delete]：默认的消息清理策略。在磁盘容量充足的情况下，保留在最长保留时间范围内的消息；在磁盘容量不足时，将提前删除旧消息，以保证服务可用性。[compact]：COMPACT 消息清理策略针对每个消息的 Key 进行整合，对于有相同 Key 的消息，只保留最新的 value 值，旧的记录则会被清除。[delete,compact]：同时配置 DELETE 和 COMPACT 两种消息清理策略。只要消息满足任一条清理策略时，都将被清除。
+     * Topic message cleanup policy supports the following three options: [delete]: The default message cleanup policy. When disk space is sufficient, messages are retained within the maximum retention period; when disk space is insufficient, old messages are deleted early to ensure service availability. [compact]: The COMPACT message cleanup policy consolidates messages by Key, retaining only the latest value for messages with the same Key, and removing older records. [delete,compact]: Configures both DELETE and COMPACT message cleanup policies. Messages will be deleted as soon as they meet any of the cleanup criteria.
      */
     cleanupPolicies?: pulumi.Input<pulumi.Input<string>[]>;
     /**
-     * Topic 的描述信息。长度不超过 128 个字符。
+     * Topic description. Maximum length: 128 characters.
      */
     description?: pulumi.Input<string>;
     /**
-     * 实例 ID。
+     * Instance ID.
      */
     instanceId: pulumi.Input<string>;
     /**
-     * Topic 级别的参数配置。Parameters 参数说明 MinInsyncReplicaNumber:2：最小同步副本个数。当同步副本个数小于配置值时，消息将无法写入对应 Topic。配置值越大，数据可靠性增加，但是可用性将会降低。默认值为副本数减 1。考虑到 Topic 的可用性，建议设置为副本数减 1。MessageMaxByte:12：最大消息大小。单位为 MB，取值范围为 1～12。默认沿用实例的最大消息大小设置。LogRetentionHours:72：消息保留时长。单位为小时，取值范围为 0～2160，即消息最久保留 90 天。默认沿用实例的消息保留时长设置。
+     * Topic-level parameter configuration. Parameters description MinInsyncReplicaNumber:2: Minimum number of in-sync replicas. If the number of in-sync replicas is less than the configured value, messages cannot be written to the Topic. Higher values increase data reliability but reduce availability. The default is replica count minus 1. For Topic availability, it is recommended to set this to replica count minus 1. MessageMaxByte:12: Maximum message size, in MB, range 1–12. By default, inherits the instance's maximum message size setting. LogRetentionHours:72: Message retention period, in hours, range 0–2160 (up to 90 days). By default, inherits the instance's message retention period setting.
      */
     parameters?: pulumi.Input<string>;
     /**
-     * Topic 分区数。取值范围为 1~300，如果实例中已创建了其他 Topic，则所有 Topic 的分区数之和不超过该实例的分区数上限。如果分区数无法满足业务需求，您可以购买更多分区，提升实例的分区数量上限。
+     * Number of Topic partitions. The range is 1–300. If other Topics have already been created in the instance, the total number of partitions across all Topics must not exceed the partition limit of the instance. If the number of partitions does not meet your business needs, you can purchase more partitions to increase the partition limit of the instance.
      */
     partitionNumber: pulumi.Input<number>;
     /**
-     * Topic 副本个数。可设置为为 2 或 3，默认值为 3。
+     * Number of Topic replicas. Can be set to 2 or 3; the default is 3.
      */
     replicaNumber?: pulumi.Input<number>;
     tags?: pulumi.Input<pulumi.Input<inputs.kafka.TopicTag>[]>;
     /**
-     * 待创建的 Topic 名称。3～64 个字符。必须以英文或数字开头。支持的字符包括英文、数字、连字符（-）、下划线（_）和英文句号（.）。
+     * Name of the Topic to be created. 3–64 characters. Must start with a letter or number. Supported characters include letters, numbers, hyphens (-), underscores (_), and periods (.).
      */
     topicName: pulumi.Input<string>;
 }

package/kafka/topic.js

@@ -6,7 +6,7 @@ exports.Topic = void 0;
 const pulumi = require("@pulumi/pulumi");
 const utilities = require("../utilities");
 /**
- * Topic即消息的主题，用于分类消息。支持 Topic 级别的资源管理，即 Topic 的创建、查看与删除等操作。
+ * Topic refers to the message subject and is used to categorize messages. Supports resource management at the Topic level, including creating, viewing, and deleting Topics.
  *
  * ## Import
  *

package/kms/getKey.d.ts

@@ -18,11 +18,11 @@ export interface GetKeyArgs {
  */
 export interface GetKeyResult {
     /**
-     * 密钥创建时间。
+     * Key creation time.
      */
     readonly createdTime: number;
     /**
-     * 密钥描述:长度为 0   - 8192 个字符。
+     * Key description: Length 0–8192 characters.
      */
     readonly description: string;
     /**
@@ -30,91 +30,91 @@ export interface GetKeyResult {
      */
     readonly id: string;
     /**
-     * 用户主密钥归档操作（用户输入1=归档，2=取消归档）
+     * User master key archive operation (enter 1 to archive, 2 to unarchive).
      */
     readonly keyArchiveOperation: number;
     /**
-     * 用户主密钥启用操作（用户输入1=启用，2=禁用）
+     * User master key enable operation (enter 1 to enable, 2 to disable).
      */
     readonly keyEnableOperation: number;
     /**
-     * 密钥唯一标识符，UUID形式。
+     * Key unique identifier in UUID format.
      */
     readonly keyId: string;
     /**
-     * 密钥材料过期时间，当值为空时表示不会过期。
+     * Key material expiration time. If empty, the key does not expire.
      */
     readonly keyMaterialExpireTime: string;
     /**
-     * 主密钥名称，长度为 2   - 31 个字符，合法字符：[a-zA-Z0-9-_]。
+     * Master key name. Length 2–31 characters. Valid characters: [a-zA-Z0-9-_].
      */
     readonly keyName: string;
     /**
-     * 用户主密钥轮转操作（用户输入1=开启，2=关闭）
+     * User master key rotation operation (enter 1 to enable, 2 to disable).
      */
     readonly keyRotationOperation: number;
     /**
-     * 对称密钥：SYMMETRIC*256，SYMMETRIC*128，非对称密钥：RSA*2048，RSA*3072，RSA*4096，EC*P256，EC*P256K，EC*P384，EC*P521，EC*SM2。
+     * Symmetric keys: SYMMETRIC*256, SYMMETRIC*128; asymmetric keys: RSA*2048, RSA*3072, RSA*4096, EC*P256, EC*P256K, EC*P384, EC*P521, EC*SM2.
      */
     readonly keySpec: string;
     /**
-     * 密钥状态：Enable，Disable，PendingDelete，Archived，PendingImport。
+     * Key status: Enable, Disable, PendingDelete, Archived, PendingImport.
      */
     readonly keyState: string;
     /**
-     * 密钥用途，取值：ENCRYPT*DECRYPT，SIGN*VERIFY，GENERATE*VERIFY*MAC。
+     * Key usage. Options: ENCRYPT*DECRYPT, SIGN*VERIFY, GENERATE*VERIFY*MAC.
      */
     readonly keyUsage: string;
     /**
-     * 密钥环名称，长度为 2   - 31 个字符，合法字符：[a-zA-Z0-9-_]。
+     * Key ring name. Length 2–31 characters. Valid characters: [a-zA-Z0-9-_].
      */
     readonly keyringName: string;
     /**
-     * 密钥最后轮转时间。
+     * Key last rotation time.
      */
     readonly lastRotationTime: string;
     /**
-     * 是否为 Multi-region 类型的主密钥。
+     * Is this a multi-region type master key.
      */
     readonly multiRegion: boolean;
     /**
-     * Multi-region key 配置信息。
+     * Multi-region key configuration information.
      */
     readonly multiRegionConfiguration: outputs.kms.GetKeyMultiRegionConfiguration;
     /**
-     * 密钥来源，取值：CloudKMS，External，ExternalKeyStore。
+     * Key source. Options: CloudKMS, External, ExternalKeyStore.
      */
     readonly origin: string;
     /**
-     * 密钥保护级别，取值：SOFTWARE，HSM。
+     * Key protection level. Options: SOFTWARE, HSM.
      */
     readonly protectionLevel: string;
     /**
-     * 密钥轮转周期，单位：天；取值范围：[90, 2560]。
+     * Key rotation period (days). Range: [90, 2560].
      */
     readonly rotateInterval: number;
     /**
-     * 密钥轮转状态，取值：Enable，Disable。
+     * Key rotation status. Options: Enable, Disable.
      */
     readonly rotateState: string;
     /**
-     * 密钥删除时间。
+     * Key deletion time.
      */
     readonly scheduleDeleteTime: string;
     /**
-     * 密钥轮转时间。
+     * Key rotation time.
      */
     readonly scheduleRotationTime: string;
     /**
-     * KMS密钥的标签信息
+     * KMS key label information.
      */
     readonly tags: outputs.kms.GetKeyTag[];
     /**
-     * 资源名称，格式应为 trn:${Service}:${Region}:${AccountID}:${ResourcePath}。
+     * Resource name. Format should be trn:${Service}:${Region}:${AccountID}:${ResourcePath}.
      */
     readonly trn: string;
     /**
-     * 密钥更新时间。
+     * Key update time.
      */
     readonly updatedTime: number;
 }

package/kms/getKeyRing.d.ts

@@ -17,11 +17,11 @@ export interface GetKeyRingArgs {
  */
 export interface GetKeyRingResult {
     /**
-     * 密钥环创建日期。
+     * Keyring creation date
      */
     readonly createDate: number;
     /**
-     * 密钥环描述，长度为 0   - 8192 个字符。
+     * Keyring description, length: 0–8192 characters
      */
     readonly description: string;
     /**
@@ -29,31 +29,31 @@ export interface GetKeyRingResult {
      */
     readonly id: string;
     /**
-     * 密钥环密钥次数。
+     * Number of keys in keyring
      */
     readonly keyCount: number;
     /**
-     * 密钥环唯一标识符，UUID形式。
+     * Keyring unique identifier, in UUID format
      */
     readonly keyRingId: string;
     /**
-     * 密钥环名称，长度为 2   - 31 个字符。合法字符：[a-zA-Z0-9-_]。
+     * Keyring name, length: 2–31 characters. Valid characters: [a-zA-Z0-9-_]
      */
     readonly keyringName: string;
     /**
-     * 密钥环类型，取值：CustomKeyring。
+     * Keyring type, value: CustomKeyring
      */
     readonly keyringType: string;
     /**
-     * 项目名称，默认值：default。
+     * Project name, default value: default
      */
     readonly projectName: string;
     /**
-     * 密钥环租户ID。
+     * Keyring tenant ID
      */
     readonly uid: string;
     /**
-     * 密钥环更新日期。
+     * Keyring update date
      */
     readonly updateDate: number;
 }