partitioned-queue

Partitioned Queue Example

Configuration in this directory creates a partitioned queue on the PubSub+ appliance leveraging the Queues & Endpoints Terraform module.

Module Configuration in the Example

Mandatory Inputs

• msg_vpn_name - Set to default in the example.
• endpoint_type - Set to queue in the example.
• endpoint_name - Set to testPQ in the example.
• permission - Set to consume in the example to enable the receiver app to remove consumed messages from the queue.

Optional Inputs

A partitioned queue is a queue with "non-exclusive" access type and greater than zero partition count. Configuration details are provided in the PubSub+ documentation.

• access_type: must be set to "non-exclusive"
• partition_count: greater than zero partitions needs to be specified
• partition_rebalance_delay and partition_rebalance_max_handoff_time are additional optional settings specifically related to partitioned queues

Optional module input variables have the same name as the attributes of the underlying provider resource. If omitted, then the default for the related resource attribute will be configured on the broker. For a list of attributes and the corresponding defaults, see the documentation of "solacebroker_msg_vpn_queue".

Output

The module provisioned_queue output refers to the created queue.

Created Resources

This example will create the following resources:

• solacebroker_msg_vpn_queue

Running the Example

Access to a PubSub+ Appliance

If you don't already have access to a broker, see the Developers page for options to get started.

Sample Source Code

The sample is available from the module GitHub repo:

git clone https:/SolaceProducts/terraform-solacebrokerappliance-queue-endpoint.git
cd examples/partitioned-queue

Adjust the Provider Configuration

Adjust the provider parameters in main.tf according to your broker. The example configuration shows settings for a local broker running in Docker.

Create the Resource

Tip: You can verify configuration changes on the broker, before and after, using the PubSub+ Broker Manager Web UI.

Execute from this folder:

terraform init
terraform plan
terraform apply

Run terraform destroy to clean up the created resources when they are no longer needed.

Additional Documentation

For more information, see Configuring Queues section in the PubSub+ documentation.