Viewing docs for volcenginecc v0.0.32
published on Thursday, Apr 23, 2026 by Volcengine
published on Thursday, Apr 23, 2026 by Volcengine
Viewing docs for volcenginecc v0.0.32
published on Thursday, Apr 23, 2026 by Volcengine
published on Thursday, Apr 23, 2026 by Volcengine
Data Source schema for Volcengine::RocketMQ::Topic
Using getTopic
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getTopic(args: GetTopicArgs, opts?: InvokeOptions): Promise<GetTopicResult>
function getTopicOutput(args: GetTopicOutputArgs, opts?: InvokeOptions): Output<GetTopicResult>def get_topic(id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetTopicResult
def get_topic_output(id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetTopicResult]func LookupTopic(ctx *Context, args *LookupTopicArgs, opts ...InvokeOption) (*LookupTopicResult, error)
func LookupTopicOutput(ctx *Context, args *LookupTopicOutputArgs, opts ...InvokeOption) LookupTopicResultOutput> Note: This function is named LookupTopic in the Go SDK.
public static class GetTopic
{
public static Task<GetTopicResult> InvokeAsync(GetTopicArgs args, InvokeOptions? opts = null)
public static Output<GetTopicResult> Invoke(GetTopicInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetTopicResult> getTopic(GetTopicArgs args, InvokeOptions options)
public static Output<GetTopicResult> getTopic(GetTopicArgs args, InvokeOptions options)
fn::invoke:
function: volcenginecc:rocketmq/getTopic:getTopic
arguments:
# arguments dictionaryThe following arguments are supported:
- Id string
- Uniquely identifies the resource.
- Id string
- Uniquely identifies the resource.
- id String
- Uniquely identifies the resource.
- id string
- Uniquely identifies the resource.
- id str
- Uniquely identifies the resource.
- id String
- Uniquely identifies the resource.
getTopic Result
The following output properties are available:
- Access
Policies List<Volcengine.Get Topic Access Policy> - Permissions for each RocketMQ key on the current Topic, supports batch permission settings. If not set, each key retains its default permissions for the current Topic.
- Created
Time string - Topic creation time.
- Description string
- Topic description, length: 0–128 characters.
- Groups
Infos List<Volcengine.Get Topic Groups Info> - Consumer group information list.
- Id string
- Uniquely identifies the resource.
- Instance
Id string - Instance ID.
- Instance
Name string - Instance name.
- Message
Type int - 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.
- Queue
Number int - 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.
- Queues
Infos List<Volcengine.Get Topic Queues Info> - Queue information list.
- Read
Access List<Volcengine.Policies Get Topic Read Access Policy> - Permissions for each RocketMQ key on the current Topic, permission field
- Service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- Topic
Name string - 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: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- Access
Policies []GetTopic Access Policy - Permissions for each RocketMQ key on the current Topic, supports batch permission settings. If not set, each key retains its default permissions for the current Topic.
- Created
Time string - Topic creation time.
- Description string
- Topic description, length: 0–128 characters.
- Groups
Infos []GetTopic Groups Info - Consumer group information list.
- Id string
- Uniquely identifies the resource.
- Instance
Id string - Instance ID.
- Instance
Name string - Instance name.
- Message
Type int - 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.
- Queue
Number int - 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.
- Queues
Infos []GetTopic Queues Info - Queue information list.
- Read
Access []GetPolicies Topic Read Access Policy - Permissions for each RocketMQ key on the current Topic, permission field
- Service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- Topic
Name string - 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: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies List<GetTopic Access Policy> - Permissions for each RocketMQ key on the current Topic, supports batch permission settings. If not set, each key retains its default permissions for the current Topic.
- created
Time String - Topic creation time.
- description String
- Topic description, length: 0–128 characters.
- groups
Infos List<GetTopic Groups Info> - Consumer group information list.
- id String
- Uniquely identifies the resource.
- instance
Id String - Instance ID.
- instance
Name String - Instance name.
- message
Type Integer - 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.
- queue
Number Integer - 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.
- queues
Infos List<GetTopic Queues Info> - Queue information list.
- read
Access List<GetPolicies Topic Read Access Policy> - Permissions for each RocketMQ key on the current Topic, permission field
- service
Status String - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic
Name String - 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: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies GetTopic Access Policy[] - Permissions for each RocketMQ key on the current Topic, supports batch permission settings. If not set, each key retains its default permissions for the current Topic.
- created
Time string - Topic creation time.
- description string
- Topic description, length: 0–128 characters.
- groups
Infos GetTopic Groups Info[] - Consumer group information list.
- id string
- Uniquely identifies the resource.
- instance
Id string - Instance ID.
- instance
Name string - Instance name.
- message
Type number - 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.
- queue
Number number - 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.
- queues
Infos GetTopic Queues Info[] - Queue information list.
- read
Access GetPolicies Topic Read Access Policy[] - Permissions for each RocketMQ key on the current Topic, permission field
- service
Status string - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic
Name string - 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: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access_
policies Sequence[GetTopic Access Policy] - Permissions for each RocketMQ key on the current Topic, supports batch permission settings. If not set, each key retains its default permissions for the current Topic.
- created_
time str - Topic creation time.
- description str
- Topic description, length: 0–128 characters.
- groups_
infos Sequence[GetTopic Groups Info] - Consumer group information list.
- id str
- Uniquely identifies the resource.
- instance_
id str - Instance ID.
- instance_
name str - Instance name.
- message_
type int - 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.
- queue_
number int - 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.
- queues_
infos Sequence[GetTopic Queues Info] - Queue information list.
- read_
access_ Sequence[Getpolicies Topic Read Access Policy] - Permissions for each RocketMQ key on the current Topic, permission field
- service_
status str - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic_
name str - 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: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
- access
Policies List<Property Map> - Permissions for each RocketMQ key on the current Topic, supports batch permission settings. If not set, each key retains its default permissions for the current Topic.
- created
Time String - Topic creation time.
- description String
- Topic description, length: 0–128 characters.
- groups
Infos List<Property Map> - Consumer group information list.
- id String
- Uniquely identifies the resource.
- instance
Id String - Instance ID.
- instance
Name String - Instance name.
- message
Type Number - 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.
- queue
Number Number - 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.
- queues
Infos List<Property Map> - Queue information list.
- read
Access List<Property Map>Policies - Permissions for each RocketMQ key on the current Topic, permission field
- service
Status String - Service status. Creating: being created, Running: running, Deleting: being deleted, Abnormal: abnormal, Updating: being updated.
- topic
Name String - 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: RMQSYSTRANSOPHALFTOPIC, BenchmarkTest, TBW102, OFFSETMOVEDEVENT, SELFTESTTOPIC, RMQSYSTRANSHALFTOPIC, SCHEDULETOPICXXXX, RMQSYSTRACETOPIC. Special prefixes: rocketmq-broker-, %RETRY%, rmqsys_, %DLQ%.
Supporting Types
GetTopicAccessPolicy
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access_
key str - AccessKey of the RocketMQ key.
- str
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
GetTopicGroupsInfo
- Group
Id string - Group ID of the consumer group.
- Message
Model string - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- Sub
String string - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- Group
Id string - Group ID of the consumer group.
- Message
Model string - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- Sub
String string - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group
Id String - Group ID of the consumer group.
- message
Model String - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub
String String - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group
Id string - Group ID of the consumer group.
- message
Model string - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub
String string - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group_
id str - Group ID of the consumer group.
- message_
model str - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub_
string str - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
- group
Id String - Group ID of the consumer group.
- message
Model String - Consumption mode. The values are as follows: Clustering: cluster consumption mode. Broadcasting: broadcast consumption mode.
- sub
String String - Subscription rule. This field contains the exact string specified by the consumer group when subscribing to this Topic, usually * or TAG1 || TAG2.
GetTopicQueuesInfo
- End
Offset int - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- Last
Update intTimestamp - The time of the most recent message written to this queue.
- Message
Count int - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- Queue
Id string - Queue ID.
- Start
Offset int - The earliest message offset in the current queue.
- End
Offset int - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- Last
Update intTimestamp - The time of the most recent message written to this queue.
- Message
Count int - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- Queue
Id string - Queue ID.
- Start
Offset int - The earliest message offset in the current queue.
- end
Offset Integer - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last
Update IntegerTimestamp - The time of the most recent message written to this queue.
- message
Count Integer - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue
Id String - Queue ID.
- start
Offset Integer - The earliest message offset in the current queue.
- end
Offset number - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last
Update numberTimestamp - The time of the most recent message written to this queue.
- message
Count number - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue
Id string - Queue ID.
- start
Offset number - The earliest message offset in the current queue.
- end_
offset int - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last_
update_ inttimestamp - The time of the most recent message written to this queue.
- message_
count int - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue_
id str - Queue ID.
- start_
offset int - The earliest message offset in the current queue.
- end
Offset Number - The maximum offset of the current queue, which is the offset of the next message. The position of the latest message is EndOffset - 1.
- last
Update NumberTimestamp - The time of the most recent message written to this queue.
- message
Count Number - The number of messages in the current queue. EndOffset is the offset of the next message, so MessageCount = EndOffset - StartOffset.
- queue
Id String - Queue ID.
- start
Offset Number - The earliest message offset in the current queue.
GetTopicReadAccessPolicy
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- Access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key string - AccessKey of the RocketMQ key.
- string
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access_
key str - AccessKey of the RocketMQ key.
- str
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
- access
Key String - AccessKey of the RocketMQ key.
- String
- User access permissions for the current Topic. ALL: Publish and subscribe permissions. PUB: Publish permission. SUB: Subscribe permission. DENY: No publish or subscribe permissions.
Package Details
- Repository
- volcenginecc volcengine/pulumi-volcenginecc
- License
- MPL-2.0
- Notes
- This Pulumi package is based on the
volcengineccTerraform Provider.
Viewing docs for volcenginecc v0.0.32
published on Thursday, Apr 23, 2026 by Volcengine
published on Thursday, Apr 23, 2026 by Volcengine
