1. Packages
  2. Tencentcloud Provider
  3. API Docs
  4. getTcmqSubscribe
tencentcloud 1.81.183 published on Wednesday, Apr 16, 2025 by tencentcloudstack

tencentcloud.getTcmqSubscribe

Explore with Pulumi AI

tencentcloud 1.81.183 published on Wednesday, Apr 16, 2025 by tencentcloudstack

Use this data source to query detailed information of tcmq subscribe

Using getTcmqSubscribe

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 getTcmqSubscribe(args: GetTcmqSubscribeArgs, opts?: InvokeOptions): Promise<GetTcmqSubscribeResult>
function getTcmqSubscribeOutput(args: GetTcmqSubscribeOutputArgs, opts?: InvokeOptions): Output<GetTcmqSubscribeResult>
Copy
def get_tcmq_subscribe(id: Optional[str] = None,
                       limit: Optional[float] = None,
                       offset: Optional[float] = None,
                       result_output_file: Optional[str] = None,
                       subscription_name: Optional[str] = None,
                       topic_name: Optional[str] = None,
                       opts: Optional[InvokeOptions] = None) -> GetTcmqSubscribeResult
def get_tcmq_subscribe_output(id: Optional[pulumi.Input[str]] = None,
                       limit: Optional[pulumi.Input[float]] = None,
                       offset: Optional[pulumi.Input[float]] = None,
                       result_output_file: Optional[pulumi.Input[str]] = None,
                       subscription_name: Optional[pulumi.Input[str]] = None,
                       topic_name: Optional[pulumi.Input[str]] = None,
                       opts: Optional[InvokeOptions] = None) -> Output[GetTcmqSubscribeResult]
Copy
func LookupTcmqSubscribe(ctx *Context, args *LookupTcmqSubscribeArgs, opts ...InvokeOption) (*LookupTcmqSubscribeResult, error)
func LookupTcmqSubscribeOutput(ctx *Context, args *LookupTcmqSubscribeOutputArgs, opts ...InvokeOption) LookupTcmqSubscribeResultOutput
Copy

> Note: This function is named LookupTcmqSubscribe in the Go SDK.

public static class GetTcmqSubscribe 
{
    public static Task<GetTcmqSubscribeResult> InvokeAsync(GetTcmqSubscribeArgs args, InvokeOptions? opts = null)
    public static Output<GetTcmqSubscribeResult> Invoke(GetTcmqSubscribeInvokeArgs args, InvokeOptions? opts = null)
}
Copy
public static CompletableFuture<GetTcmqSubscribeResult> getTcmqSubscribe(GetTcmqSubscribeArgs args, InvokeOptions options)
public static Output<GetTcmqSubscribeResult> getTcmqSubscribe(GetTcmqSubscribeArgs args, InvokeOptions options)
Copy
fn::invoke:
  function: tencentcloud:index/getTcmqSubscribe:getTcmqSubscribe
  arguments:
    # arguments dictionary
Copy

The following arguments are supported:

TopicName This property is required. string
Topic name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
Id string
Limit double
Number of topics to be returned per page in case of paginated return. If this parameter is not passed in, 20 will be used by default. Maximum value: 50.
Offset double
Starting position of the list of topics to be returned on the current page in case of paginated return. If a value is entered, limit is required. If this parameter is left empty, 0 will be used by default.
ResultOutputFile string
Used to save results.
SubscriptionName string
Fuzzy search by SubscriptionName.
TopicName This property is required. string
Topic name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
Id string
Limit float64
Number of topics to be returned per page in case of paginated return. If this parameter is not passed in, 20 will be used by default. Maximum value: 50.
Offset float64
Starting position of the list of topics to be returned on the current page in case of paginated return. If a value is entered, limit is required. If this parameter is left empty, 0 will be used by default.
ResultOutputFile string
Used to save results.
SubscriptionName string
Fuzzy search by SubscriptionName.
topicName This property is required. String
Topic name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id String
limit Double
Number of topics to be returned per page in case of paginated return. If this parameter is not passed in, 20 will be used by default. Maximum value: 50.
offset Double
Starting position of the list of topics to be returned on the current page in case of paginated return. If a value is entered, limit is required. If this parameter is left empty, 0 will be used by default.
resultOutputFile String
Used to save results.
subscriptionName String
Fuzzy search by SubscriptionName.
topicName This property is required. string
Topic name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id string
limit number
Number of topics to be returned per page in case of paginated return. If this parameter is not passed in, 20 will be used by default. Maximum value: 50.
offset number
Starting position of the list of topics to be returned on the current page in case of paginated return. If a value is entered, limit is required. If this parameter is left empty, 0 will be used by default.
resultOutputFile string
Used to save results.
subscriptionName string
Fuzzy search by SubscriptionName.
topic_name This property is required. str
Topic name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id str
limit float
Number of topics to be returned per page in case of paginated return. If this parameter is not passed in, 20 will be used by default. Maximum value: 50.
offset float
Starting position of the list of topics to be returned on the current page in case of paginated return. If a value is entered, limit is required. If this parameter is left empty, 0 will be used by default.
result_output_file str
Used to save results.
subscription_name str
Fuzzy search by SubscriptionName.
topicName This property is required. String
Topic name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id String
limit Number
Number of topics to be returned per page in case of paginated return. If this parameter is not passed in, 20 will be used by default. Maximum value: 50.
offset Number
Starting position of the list of topics to be returned on the current page in case of paginated return. If a value is entered, limit is required. If this parameter is left empty, 0 will be used by default.
resultOutputFile String
Used to save results.
subscriptionName String
Fuzzy search by SubscriptionName.

getTcmqSubscribe Result

The following output properties are available:

Id string
SubscriptionLists List<GetTcmqSubscribeSubscriptionList>
Set of subscription attributes.
TopicName string
Limit double
Offset double
ResultOutputFile string
SubscriptionName string
Subscription name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
Id string
SubscriptionLists []GetTcmqSubscribeSubscriptionList
Set of subscription attributes.
TopicName string
Limit float64
Offset float64
ResultOutputFile string
SubscriptionName string
Subscription name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id String
subscriptionLists List<GetTcmqSubscribeSubscriptionList>
Set of subscription attributes.
topicName String
limit Double
offset Double
resultOutputFile String
subscriptionName String
Subscription name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id string
subscriptionLists GetTcmqSubscribeSubscriptionList[]
Set of subscription attributes.
topicName string
limit number
offset number
resultOutputFile string
subscriptionName string
Subscription name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id str
subscription_lists Sequence[GetTcmqSubscribeSubscriptionList]
Set of subscription attributes.
topic_name str
limit float
offset float
result_output_file str
subscription_name str
Subscription name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.
id String
subscriptionLists List<Property Map>
Set of subscription attributes.
topicName String
limit Number
offset Number
resultOutputFile String
subscriptionName String
Subscription name, which must be unique in the same topic under the same account in the same region. It can contain up to 64 letters, digits, and hyphens and must begin with a letter.

Supporting Types

GetTcmqSubscribeSubscriptionList

BindingKeys This property is required. List<string>
Filtering policy for subscribing to and receiving messages.
CreateTime This property is required. double
Subscription creation time. A Unix timestamp accurate down to the millisecond will be returned.
Endpoint This property is required. string
Endpoint that receives notifications, which varies by protocol: for HTTP, the endpoint must start with http://, and the host can be a domain or IP; for queue, queueName should be entered.
FilterTags This property is required. List<string>
Filtering policy selected when a subscription is created:If filterType is 1, filterTag will be used for filtering. If filterType is 2, bindingKey will be used for filtering.
LastModifyTime This property is required. double
Time when the subscription attribute is last modified. A Unix timestamp accurate down to the millisecond will be returned.
MsgCount This property is required. double
Number of messages to be delivered in the subscription.
NotifyContentFormat This property is required. string
Push content format. Valid values: 1. JSON; 2. SIMPLIFIED, i.e., the raw format. If Protocol is queue, this value must be SIMPLIFIED. If Protocol is http, both options are acceptable, and the default value is JSON.
NotifyStrategy This property is required. string
CMQ push server retry policy in case an error occurs while pushing a message to Endpoint. Valid values: 1. BACKOFF_RETRY: backoff retry, which is to retry at a fixed interval, discard the message after a certain number of retries, and continue to push the next message; 2. EXPONENTIAL_DECAY_RETRY: exponential decay retry, which is to retry at an exponentially increasing interval, such as 1s, 2s, 4s, 8s, and so on. As a message can be retained in a topic for one day, failed messages will be discarded at most after one day of retry. Default value: EXPONENTIAL_DECAY_RETRY.
Protocol This property is required. string
Subscription protocol. Currently, two protocols are supported: HTTP and queue. To use the HTTP protocol, you need to build your own web server to receive messages. With the queue protocol, messages are automatically pushed to a CMQ queue and you can pull them concurrently.
SubscriptionId This property is required. string
Subscription ID, which will be used during monitoring data pull.
SubscriptionName This property is required. string
Fuzzy search by SubscriptionName.
TopicOwner This property is required. double
Subscription owner APPID.
BindingKeys This property is required. []string
Filtering policy for subscribing to and receiving messages.
CreateTime This property is required. float64
Subscription creation time. A Unix timestamp accurate down to the millisecond will be returned.
Endpoint This property is required. string
Endpoint that receives notifications, which varies by protocol: for HTTP, the endpoint must start with http://, and the host can be a domain or IP; for queue, queueName should be entered.
FilterTags This property is required. []string
Filtering policy selected when a subscription is created:If filterType is 1, filterTag will be used for filtering. If filterType is 2, bindingKey will be used for filtering.
LastModifyTime This property is required. float64
Time when the subscription attribute is last modified. A Unix timestamp accurate down to the millisecond will be returned.
MsgCount This property is required. float64
Number of messages to be delivered in the subscription.
NotifyContentFormat This property is required. string
Push content format. Valid values: 1. JSON; 2. SIMPLIFIED, i.e., the raw format. If Protocol is queue, this value must be SIMPLIFIED. If Protocol is http, both options are acceptable, and the default value is JSON.
NotifyStrategy This property is required. string
CMQ push server retry policy in case an error occurs while pushing a message to Endpoint. Valid values: 1. BACKOFF_RETRY: backoff retry, which is to retry at a fixed interval, discard the message after a certain number of retries, and continue to push the next message; 2. EXPONENTIAL_DECAY_RETRY: exponential decay retry, which is to retry at an exponentially increasing interval, such as 1s, 2s, 4s, 8s, and so on. As a message can be retained in a topic for one day, failed messages will be discarded at most after one day of retry. Default value: EXPONENTIAL_DECAY_RETRY.
Protocol This property is required. string
Subscription protocol. Currently, two protocols are supported: HTTP and queue. To use the HTTP protocol, you need to build your own web server to receive messages. With the queue protocol, messages are automatically pushed to a CMQ queue and you can pull them concurrently.
SubscriptionId This property is required. string
Subscription ID, which will be used during monitoring data pull.
SubscriptionName This property is required. string
Fuzzy search by SubscriptionName.
TopicOwner This property is required. float64
Subscription owner APPID.
bindingKeys This property is required. List<String>
Filtering policy for subscribing to and receiving messages.
createTime This property is required. Double
Subscription creation time. A Unix timestamp accurate down to the millisecond will be returned.
endpoint This property is required. String
Endpoint that receives notifications, which varies by protocol: for HTTP, the endpoint must start with http://, and the host can be a domain or IP; for queue, queueName should be entered.
filterTags This property is required. List<String>
Filtering policy selected when a subscription is created:If filterType is 1, filterTag will be used for filtering. If filterType is 2, bindingKey will be used for filtering.
lastModifyTime This property is required. Double
Time when the subscription attribute is last modified. A Unix timestamp accurate down to the millisecond will be returned.
msgCount This property is required. Double
Number of messages to be delivered in the subscription.
notifyContentFormat This property is required. String
Push content format. Valid values: 1. JSON; 2. SIMPLIFIED, i.e., the raw format. If Protocol is queue, this value must be SIMPLIFIED. If Protocol is http, both options are acceptable, and the default value is JSON.
notifyStrategy This property is required. String
CMQ push server retry policy in case an error occurs while pushing a message to Endpoint. Valid values: 1. BACKOFF_RETRY: backoff retry, which is to retry at a fixed interval, discard the message after a certain number of retries, and continue to push the next message; 2. EXPONENTIAL_DECAY_RETRY: exponential decay retry, which is to retry at an exponentially increasing interval, such as 1s, 2s, 4s, 8s, and so on. As a message can be retained in a topic for one day, failed messages will be discarded at most after one day of retry. Default value: EXPONENTIAL_DECAY_RETRY.
protocol This property is required. String
Subscription protocol. Currently, two protocols are supported: HTTP and queue. To use the HTTP protocol, you need to build your own web server to receive messages. With the queue protocol, messages are automatically pushed to a CMQ queue and you can pull them concurrently.
subscriptionId This property is required. String
Subscription ID, which will be used during monitoring data pull.
subscriptionName This property is required. String
Fuzzy search by SubscriptionName.
topicOwner This property is required. Double
Subscription owner APPID.
bindingKeys This property is required. string[]
Filtering policy for subscribing to and receiving messages.
createTime This property is required. number
Subscription creation time. A Unix timestamp accurate down to the millisecond will be returned.
endpoint This property is required. string
Endpoint that receives notifications, which varies by protocol: for HTTP, the endpoint must start with http://, and the host can be a domain or IP; for queue, queueName should be entered.
filterTags This property is required. string[]
Filtering policy selected when a subscription is created:If filterType is 1, filterTag will be used for filtering. If filterType is 2, bindingKey will be used for filtering.
lastModifyTime This property is required. number
Time when the subscription attribute is last modified. A Unix timestamp accurate down to the millisecond will be returned.
msgCount This property is required. number
Number of messages to be delivered in the subscription.
notifyContentFormat This property is required. string
Push content format. Valid values: 1. JSON; 2. SIMPLIFIED, i.e., the raw format. If Protocol is queue, this value must be SIMPLIFIED. If Protocol is http, both options are acceptable, and the default value is JSON.
notifyStrategy This property is required. string
CMQ push server retry policy in case an error occurs while pushing a message to Endpoint. Valid values: 1. BACKOFF_RETRY: backoff retry, which is to retry at a fixed interval, discard the message after a certain number of retries, and continue to push the next message; 2. EXPONENTIAL_DECAY_RETRY: exponential decay retry, which is to retry at an exponentially increasing interval, such as 1s, 2s, 4s, 8s, and so on. As a message can be retained in a topic for one day, failed messages will be discarded at most after one day of retry. Default value: EXPONENTIAL_DECAY_RETRY.
protocol This property is required. string
Subscription protocol. Currently, two protocols are supported: HTTP and queue. To use the HTTP protocol, you need to build your own web server to receive messages. With the queue protocol, messages are automatically pushed to a CMQ queue and you can pull them concurrently.
subscriptionId This property is required. string
Subscription ID, which will be used during monitoring data pull.
subscriptionName This property is required. string
Fuzzy search by SubscriptionName.
topicOwner This property is required. number
Subscription owner APPID.
binding_keys This property is required. Sequence[str]
Filtering policy for subscribing to and receiving messages.
create_time This property is required. float
Subscription creation time. A Unix timestamp accurate down to the millisecond will be returned.
endpoint This property is required. str
Endpoint that receives notifications, which varies by protocol: for HTTP, the endpoint must start with http://, and the host can be a domain or IP; for queue, queueName should be entered.
filter_tags This property is required. Sequence[str]
Filtering policy selected when a subscription is created:If filterType is 1, filterTag will be used for filtering. If filterType is 2, bindingKey will be used for filtering.
last_modify_time This property is required. float
Time when the subscription attribute is last modified. A Unix timestamp accurate down to the millisecond will be returned.
msg_count This property is required. float
Number of messages to be delivered in the subscription.
notify_content_format This property is required. str
Push content format. Valid values: 1. JSON; 2. SIMPLIFIED, i.e., the raw format. If Protocol is queue, this value must be SIMPLIFIED. If Protocol is http, both options are acceptable, and the default value is JSON.
notify_strategy This property is required. str
CMQ push server retry policy in case an error occurs while pushing a message to Endpoint. Valid values: 1. BACKOFF_RETRY: backoff retry, which is to retry at a fixed interval, discard the message after a certain number of retries, and continue to push the next message; 2. EXPONENTIAL_DECAY_RETRY: exponential decay retry, which is to retry at an exponentially increasing interval, such as 1s, 2s, 4s, 8s, and so on. As a message can be retained in a topic for one day, failed messages will be discarded at most after one day of retry. Default value: EXPONENTIAL_DECAY_RETRY.
protocol This property is required. str
Subscription protocol. Currently, two protocols are supported: HTTP and queue. To use the HTTP protocol, you need to build your own web server to receive messages. With the queue protocol, messages are automatically pushed to a CMQ queue and you can pull them concurrently.
subscription_id This property is required. str
Subscription ID, which will be used during monitoring data pull.
subscription_name This property is required. str
Fuzzy search by SubscriptionName.
topic_owner This property is required. float
Subscription owner APPID.
bindingKeys This property is required. List<String>
Filtering policy for subscribing to and receiving messages.
createTime This property is required. Number
Subscription creation time. A Unix timestamp accurate down to the millisecond will be returned.
endpoint This property is required. String
Endpoint that receives notifications, which varies by protocol: for HTTP, the endpoint must start with http://, and the host can be a domain or IP; for queue, queueName should be entered.
filterTags This property is required. List<String>
Filtering policy selected when a subscription is created:If filterType is 1, filterTag will be used for filtering. If filterType is 2, bindingKey will be used for filtering.
lastModifyTime This property is required. Number
Time when the subscription attribute is last modified. A Unix timestamp accurate down to the millisecond will be returned.
msgCount This property is required. Number
Number of messages to be delivered in the subscription.
notifyContentFormat This property is required. String
Push content format. Valid values: 1. JSON; 2. SIMPLIFIED, i.e., the raw format. If Protocol is queue, this value must be SIMPLIFIED. If Protocol is http, both options are acceptable, and the default value is JSON.
notifyStrategy This property is required. String
CMQ push server retry policy in case an error occurs while pushing a message to Endpoint. Valid values: 1. BACKOFF_RETRY: backoff retry, which is to retry at a fixed interval, discard the message after a certain number of retries, and continue to push the next message; 2. EXPONENTIAL_DECAY_RETRY: exponential decay retry, which is to retry at an exponentially increasing interval, such as 1s, 2s, 4s, 8s, and so on. As a message can be retained in a topic for one day, failed messages will be discarded at most after one day of retry. Default value: EXPONENTIAL_DECAY_RETRY.
protocol This property is required. String
Subscription protocol. Currently, two protocols are supported: HTTP and queue. To use the HTTP protocol, you need to build your own web server to receive messages. With the queue protocol, messages are automatically pushed to a CMQ queue and you can pull them concurrently.
subscriptionId This property is required. String
Subscription ID, which will be used during monitoring data pull.
subscriptionName This property is required. String
Fuzzy search by SubscriptionName.
topicOwner This property is required. Number
Subscription owner APPID.

Package Details

Repository
tencentcloud tencentcloudstack/terraform-provider-tencentcloud
License
Notes
This Pulumi package is based on the tencentcloud Terraform Provider.
tencentcloud 1.81.183 published on Wednesday, Apr 16, 2025 by tencentcloudstack