Configuration in this directory creates a topic endpoint on the PubSub+ event broker leveraging the Queues & Endpoints Terraform module.
Important: The topic subscription that a topic endpoint will spool messages for is not specified when a topic endpoint is provisioned. For more information, see the PubSub+ documentation.
msg_vpn_name
- Set todefault
in the example.endpoint_type
- Set totopic_endpoint
in the example.endpoint_name
- Set totestTE
in the example.permission
- Set toconsume
in the example to enable the receiver app to remove consumed messages from the topic endpoint.
Note that the access_type
module input variable defines if a topic endpoint is "exclusive" or "non-exclusive". The default is "exclusive".
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_topic_endpoint".
The module provisioned_topic endpoint
output refers to the created topic endpoint.
This example will create the following resources:
solacebroker_msg_vpn_topic endpoint
If you don't already have access to a broker, see the Developers page for options to get started.
The sample is available from the module GitHub repo:
git clone https://github.com/SolaceProducts/terraform-solacebroker-queue-endpoint.git
cd examples/topic-endpoint
Adjust the provider parameters in main.tf
according to your broker. The example configuration shows settings for a local broker running in Docker.
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.
For more information, see Configuring Topic Endpoints section in the PubSub+ documentation.