Add logic to support EventHub config

[yantang-msft]

Add logics so user can enable MA to EventHub from powershell

[markcowl]

tests?

[yantang-msft]

Hi Mark,

IIRC, today is the Code Complete date for powershell? What’s the exact time?
I’m adding test cases, but we want to get this change in for the April release, so we don’t want to miss the last chance of merging.

Thanks!
Yanming

From: Mark Cowlishaw [mailto:[email protected]]
Sent: Wednesday, March 23, 2016 12:30 AM
To: Azure/azure-powershell [email protected]
Cc: Yanming Tang [email protected]
Subject: Re: [azure-powershell] Add logic to support EventHub config (#1981)

tests?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//pull/1981#issuecomment-200227946

[markcowl]

@yantang-msft if you guys sign off on the functionality, it is ok to add the tests later this week. But please file an issue for this in GitHub and refer to it here.

[markcowl]

on demand run here: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/618/

[markcowl]

These should be attributed as check-in tests

[yantang-msft]

I only see BVT defined in this project which looks closer.
Here is what marked for DSC extension, [Trait(Category.Functional, Category.BVT)]. Should I follow this attribute or add "CheckIn" in the category?

[yantang-msft]

@markcowl Attribute added. See if it's correct.

[markcowl]

on demand run here: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/625/

[yantang-msft]

@markcowl The failed test case is irrelevant to this change, it will also fail before any of my commits.
However, I tested it will pass with current dev branch (and after merging my changes as well). So I assume there is some test framework change which fixed this issue, it's just that I branched before this fix.

[hovsepm]

new demand: http://azuresdkci.cloudapp.net/view/1-AzurePowerShell/job/powershell-demand/632/