Spring Cloud Azure Stream Binder for Service Bus Queue by retrieving connecting string via Azure Resource Manager (ARM)
This code sample demonstrates how to use the Spring Cloud Stream binder for Azure Service Bus Queue by retrieving connection string via ARM.
You will build an application using Spring Cloud Stream to send and receive messages for Azure Service Bus Queue. This sample will
- Create a Service Bus queue and a service principal and assign the
Contributor
role of the service bus to the service principal. - Connect to the ARM using the service principal and retrieve the connection string of the service bus.
- Connect to the Service Bus queue to send and receive messages.
- An Azure subscription
- Terraform
- Azure CLI
- JDK8 or later
- Maven
- You can also import the code straight into your IDE:
This sample will create Azure resources using Terraform. If you choose to run it without using Terraform to provision resources, please pay attention to:
Important
If you choose to use a security principal to authenticate and authorize with Azure Active Directory for accessing an Azure resource please refer to Authorize access with Azure AD to make sure the security principal has been granted the sufficient permission to access the Azure resource.
Terraform must authenticate to Azure to create infrastructure.
In your terminal, use the Azure CLI tool to setup your account permissions locally.
az login
Your browser window will open and you will be prompted to enter your Azure login credentials. After successful authentication, your terminal will display your subscription information. You do not need to save this output as it is saved in your system for Terraform to use.
You have logged in. Now let us find all the subscriptions to which you have access...
[
{
"cloudName": "AzureCloud",
"homeTenantId": "home-Tenant-Id",
"id": "subscription-id",
"isDefault": true,
"managedByTenants": [],
"name": "Subscription-Name",
"state": "Enabled",
"tenantId": "0envbwi39-TenantId",
"user": {
"name": "[email protected]",
"type": "user"
}
}
]
If you have more than one subscription, specify the subscription-id you want to use with command below:
az account set --subscription <your-subscription-id>
After login Azure CLI with your account, now you can use the terraform script to create Azure Resources.
# In the root directory of the sample
# Initialize your Terraform configuration
terraform -chdir=./terraform init
# Apply your Terraform Configuration
terraform -chdir=./terraform apply -auto-approve
# In the root directory of the sample
# Initialize your Terraform configuration
terraform -chdir=terraform init
# Apply your Terraform Configuration
terraform -chdir=terraform apply -auto-approve
It may take a few minutes to run the script. After successful running, you will see prompt information like below:
azurecaf_name.resource_group: Creating...
azurecaf_name.azurecaf_name_servicebus: Creating...
azurecaf_name.azurecaf_name_servicebus: Creation complete ...
azurecaf_name.resource_group: Creation complete ...
azuread_application.servicebusqueuebinder: Creating...
azuread_application.servicebusqueuebinder: Creation complete ...
azuread_application_password.servicebusqueuebinder: Creating...
azuread_service_principal.servicebusqueuebinder: Creating...
azuread_service_principal.servicebusqueuebinder: Creation complete ...
azuread_application_password.servicebusqueuebinder: Creation complete ...
azurerm_resource_group.main: Creating...
azurerm_resource_group.main: Creation complete ...
azurerm_servicebus_namespace.servicebus_namespace: Creating...
...
azurerm_servicebus_namespace.servicebus_namespace: Creation complete ...
azurerm_role_assignment.role_servicebus_data_contributor: Creating...
azurerm_servicebus_queue.queue: Creating...
azurerm_servicebus_queue.queue: Creation complete ...
...
azurerm_role_assignment.role_servicebus_data_contributor: Creation complete ...
Apply complete! Resources: 9 added, 0 changed, 0 destroyed.
Outputs:
...
You can go to Azure portal in your web browser to check the resources you created.
Running the command below to export environment values:
source ./terraform/setup_env.sh
terraform\setup_env.ps1
If you want to run the sample in debug mode, you can save the output value.
AZURE_SERVICEBUS_NAMESPACE=...
AZURE_SERVICEBUS_QUEUE_NAME=...
AZURE_SERVICEBUS_SUBSCRIPTION_ID=...
AZURE_SERVICEBUS_RESOURCE_GROUP=...
AZURE_SERVICE_PRINCIPAL_CLIENT_ID=...
AZURE_SERVICE_PRINCIPAL_CLIENT_SECRET=...
AZURE_SERVICE_PRINCIPAL_TENANT_ID=...
In your terminal, run mvn clean spring-boot:run
.
mvn clean spring-boot:run
You can debug your sample by adding the saved output values to the tool's environment variables or the sample's application.yaml
file.
-
If your tool is
IDEA
, please refer to Debug your first Java application and add environment variables. -
If your tool is
ECLIPSE
, please refer to Debugging the Eclipse IDE for Java Developers and Eclipse Environment Variable Setup.
- Verify in your app’s logs that similar messages were posted:
...
New message received: 'Hello world, 2'
...
Message 'Hello world, 2' successfully checkpointed
...
...
New message received: 'Hello world, 3'
...
Message 'Hello world, 3' successfully checkpointed
...
...
After running the sample, if you don't want to run the sample, remember to destroy the Azure resources you created to avoid unnecessary billing.
The terraform destroy command terminates resources managed by your Terraform project.
To destroy the resources you created.
terraform -chdir=./terraform destroy -auto-approve
terraform -chdir=terraform destroy -auto-approve