Eventhub: Added Namespace properties for BYOK

[v-Ajnava]

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and have all been fixed in this PR.
• The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

• Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
• adding/removing APIs.
• adding/removing properties.
• adding/removing API-version.
• adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

• If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
  Please follow the link to find more details on API review process.

[openapi-sdkautomation]

In Testing, Please Ignore

[Logs] (Generated from 2128273, Iteration 3)

.NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]

• No packages generated.

Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]

• azure-mgmt-eventhub [Logs] [Instructions] [Generation PR] [Integration PR]
  • azure-mgmt-eventhub-3.0.0.zip
  • azure_mgmt_eventhub-3.0.0-py2.py3-none-any.whl

Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]

• eventhubs/resource-manager/v2015_08_01 [Logs]
• eventhubs/resource-manager/v2017_04_01 [Logs]
• eventhubs/resource-manager/v2018_01_01_preview [Logs] [Instructions] [Generation PR] [Integration PR]
  • pom.xml
  • azure-mgmt-eventhubs-1.0.0-beta-javadoc.jar
  • azure-mgmt-eventhubs-1.0.0-beta-sources.jar
  • azure-mgmt-eventhubs-1.0.0-beta.jar

Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]

• eventhub/mgmt/2015-08-01 [Logs]
• eventhub/mgmt/2017-04-01 [Logs] [Instructions] [Generation PR] [Integration PR]
  • eventhub.mgmt.2017-04-01.zip
• preview/eventhub/mgmt/2018-01-01-preview [Logs] [Instructions] [Generation PR] [Integration PR]
  • preview.eventhub.mgmt.2018-01-01-preview.zip

JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]

• @azure/arm-eventhub [Logs] [Instructions]
  • azure-arm-eventhub-3.2.0.tgz

Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]

• azure_sdk [Logs] [Instructions]
  • azure_sdk-0.19.7.gem

[AutorestCI]

Automation for azure-sdk-for-go

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-go#6008

[AutorestCI]

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#7821

[azuresdkci]

Can one of the admins verify this patch?

[KrisBash]

See comment about api version

[KrisBash]

Adding mutable properties in an API version is a concern with GET->PUT patterns, and is considered a breaking change. If a downlevel client does a GET, after these properties have been set, and then does a PUT - what happens to the resource configuration? PUT semantics would mandate that the properties are removed from the resource. This is a preview api, but it would still be better in a new API version.

[v-Ajnava]

@dsouzaarun, can you please take a look?

[ravbhatnagar]

Discussed this with Arun during office hours. The team agrees that this change will not be carried forward in the GA apiversion. And will be done in the recommended way by incrementing the api-version. However, to unblock this case and enable team to get partner feedback, approving this.
We do need to have more concrete guideline on preview api-versions.
Signing off from ARM side.

[zikalino]

@KrisBash could you please unblock this?