Azure Service BusterConfigure Service Bus Topics, Queues and subscriptions from VSTS. Getting StartedAzure's Message Queueing solution, Service Bus, is easily deployed using ARM templates. However, maintaining a complex or dynamic configuration of queues, topics and subscriptions in ARM templates quickly becomes unwieldy. A problem often occurs when a development group requests Service Bus changes and must wait for the Azure admins to modify the template/parameters and deploy the change. This solution uses Visual Studio Team Services to manage an Azure Service Bus through a specially formatted json file. It can be configured for CI/CD where changes to the json file trigger a release that deploys the changes to the Service Bus. This eliminates the middle-man and gives developers more control over the configuration. PrerequisitesThis extension assumes that the Service Bus namespace already exists in the specified subscription and resource group. It will not create the namespace if it doesn't already exist (however this would probably be an easy change to implement). ConfigurationAdd this extenion in the usual way as a release task. The only option is whether to delete any namespace resources that are not specifically defined in the configuration file. Selecting the option to Configuration file structureThe json configuration file should be configured using standard json syntax and structure. A sample is shown below.
Topic resource settingsAll topics will be created with default settings and the following options enabled. There is currently no way to override these settings.
Subscription resource settingsAll subscriptions will be created with default settings and the following options enabled. There is currently no way to override these settings.
Queue resource settingsAll topics will be created with default settings and the following options enabled. There is currently no way to override these settings.
ContributingPlease read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us. VersioningWe use SemVer for versioning. For the versions available, see the tags on this repository. Authors
See also the list of contributors who participated in this project. LicenseThis project is licensed under the MIT License - see the LICENSE.md file for details Acknowledgments
|