Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New in 2012-02-12: service bus topic options that are missing #45

Closed
huguesv opened this issue Jun 18, 2012 · 2 comments
Closed

New in 2012-02-12: service bus topic options that are missing #45

huguesv opened this issue Jun 18, 2012 · 2 comments
Labels
feature-request This issue requires a new behavior in the product in order be resolved. Service Attention Workflow: This issue is responsible by Azure service team. Service Bus

Comments

@huguesv
Copy link
Contributor

huguesv commented Jun 18, 2012

According to http://msdn.microsoft.com/en-us/library/windowsazure/1b759576-0668-4018-8483-846e7bb193be#RESTAPI_2

Name: Xml Element Name
====================
MaximumNumberOfSubscriptions: MaxSubscriptionsPerTopic
MaximumNumberOfSqlFilters: MaxSqlFiltersPerTopic
MaximumNumberOfCorrelationFilters: MaxCorrelationFiltersPerTopic
EnableDeadLetteringOnFilterEvaluationExceptions: DeadLetteringOnFilterEvaluationExceptions
@weidongh
Copy link

The documentation has been changed recently. Node.js and Java have the same implementation as we do. According to https://github.com/WindowsAzure/azure-sdk-for-java/blob/master/microsoft-azure-api/src/main/resources/schemas.microsoft.com.netservices.2010.10.servicebus.connect.xsd, the implementation seems right.

@lmazuel
Copy link
Member

lmazuel commented Sep 14, 2016

The first one will be covered in ARM (package azure-arm-servicebus to come), the three others don't exist anymore even in the "classic" RestAPI:
https://msdn.microsoft.com/en-us/library/azure/hh780749.aspx

@lmazuel lmazuel closed this as completed Sep 14, 2016
@bsiegel bsiegel added the Service Attention Workflow: This issue is responsible by Azure service team. label Sep 26, 2018
azclibot pushed a commit to azclibot/azure-sdk-for-python that referenced this issue Dec 23, 2021
@smile37773 @leonard520
@ninpan-ms @zhoufenqin
CodeGen from PR 17141 in Azure/azure-rest-api-specs
c3d5c7f 
[Hub Generated] Add Microsoft.AppPlatform/Spring new pricing tier on API version 2022-01-01-preview (Azure#17141)

* copy from last api version

* Add system data and example

* Add availability zones change

* Configuration Service

* Service Registry

* Gateway

* API portal

* App and Deployment

* BuildServices/Builds/Builders/BuildResults

* BuildPackBindings

* fix swagger of build service (Azure#43)

* fix swagger of build service

* fix

* fix: add agentPool in BuildProperties (Azure#44)

* Add fqdn in service resource (Azure#45)

Co-authored-by: Xiaoyun Ding <[email protected]>

* Change appName to appResourceId (Azure#46)

* Change appName to appResourceId

* fix

* Add resource id to connect resources

* Change operatorRuntimeState to resourceRequest (Azure#49)

* Change appName to appResourceId

* rename sourceGateways to gatewayIds

* Change operatorRuntimeState to resourceRequest

* feat: update agent pool swagger (Azure#50)

* Update 201 descriptions about header

* add get build (Azure#51)

* Remove 202 for PUT

* List and Get supportedBuildpacks

* set active deployment should be async

* Update setActiveDeployments response body

* ContentCertificateProperties.content should be secret

* Add jvmOptions for Jar type

Co-authored-by: Qingyi Liu <[email protected]>
Co-authored-by: Xiaoyun Ding <[email protected]>
Co-authored-by: Xiaoyun Ding <[email protected]>
Co-authored-by: ninpan-ms <[email protected]>
Co-authored-by: zhoufenqin <[email protected]>
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-request This issue requires a new behavior in the product in order be resolved. Service Attention Workflow: This issue is responsible by Azure service team. Service Bus
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bsiegel @lmazuel @weidongh @huguesv