Package version
Authorization rules on the queue
Max idle time before entity is deleted. This is to be specified in ISO-8601 duration format such as "PT1M" for 1 minute, "PT5S" for 5 seconds.
More on ISO-8601 duration format: https://en.wikipedia.org/wiki/ISO_8601#Durations
Availability status of the messaging entity.
If it is enabled and a message expires, the Service Bus moves the message from the queue into the queue’s dead-letter sub-queue. If disabled, message will be permanently deleted from the queue. Settable only at queue creation time.
Depending on whether DeadLettering is enabled, a message is automatically moved to the dead-letter sub-queue or deleted if it has been stored in the queue for longer than the specified time. This value is overwritten by a TTL specified on the message if and only if the message TTL is smaller than the TTL set on the queue. This value is immutable after the Queue has been created. This is to be specified in ISO-8601 duration format such as "PT1M" for 1 minute, "PT5S" for 5 seconds.
More on ISO-8601 duration format: https://en.wikipedia.org/wiki/ISO_8601#Durations
Specifies the time span during which the Service Bus detects message duplication. This is to be specified in ISO-8601 duration format such as "PT1M" for 1 minute, "PT5S" for 5 seconds.
More on ISO-8601 duration format: https://en.wikipedia.org/wiki/ISO_8601#Durations
Specifies if batched operations should be allowed.
Specifies whether express entities are enabled on queue.
Specifies whether the queue should be partitioned.
Absolute URL or the name of the queue or topic the dead-lettered
messages are to be forwarded to.
For example, an absolute URL input would be of the form
sb://<your-service-bus-namespace-endpoint>/<queue-or-topic-name>
Absolute URL or the name of the queue or topic the
messages are to be forwarded to.
For example, an absolute URL input would be of the form
sb://<your-service-bus-namespace-endpoint>/<queue-or-topic-name>
Determines the amount of time in seconds in which a message should be locked for processing by a receiver. After this period, the message is unlocked and available for consumption by the next receiver. (If sessions are enabled, this lock duration is applicable for sessions and not for messages.)
This is to be specified in ISO-8601 duration format such as "PT1M" for 1 minute, "PT5S" for 5 seconds.
More on ISO-8601 duration format: https://en.wikipedia.org/wiki/ISO_8601#Durations
The maximum delivery count of messages after which if it is still not settled, gets moved to the dead-letter sub-queue.
The maximum message size in kilobytes for messages sent to this queue.
(Configurable only for Premium Tier Service Bus namespace.)
Specifies the maximum queue size in megabytes. Any attempt to enqueue a message that will cause the queue to exceed this value will fail.
If enabled, the topic will detect duplicate messages within the time span specified by the DuplicateDetectionHistoryTimeWindow property. Settable only at queue creation time.
If set to true, the queue will be session-aware and only SessionReceiver will be supported. Session-aware queues are not supported through REST. Settable only at queue creation time.
Status of the messaging entity.
The user provided metadata information associated with the queue. Used to specify textual content such as tags, labels, etc. Value must not exceed 1024 bytes encoded in utf-8.
Generated using TypeDoc
Represents settable options on a queue