[Event Hubs Client] Migrate Code into Central Repository (#5448) #5501
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The goal of this set of changes is intended to perform the initial SDK root directory clean up, isolating the management library in a dedicated directory to allow for adoption of the client library in a future change set for the referenced issue.
This scope of this work is intended to be a focused reorganization, with the code and other artifacts otherwise left as they were in the standalone repository, including the existing code formatting and conventions.
Details
Repository Structure
management
.Last Upstream Rebase
Friday, March 22, 2019 05:20pm (EDT)
Related and Follow-Up Issues
[Objective] Event Hubs: Adopt Client Library into Central Repository (On-Boarding Event Hub to Central Repo #5447)
Event Hubs Client: Migrate Code into Central Repository ([Event Hubs] Migrate Client Code into Central Repository #5448)
Event Hubs Client: Enhance ReadMe ([Event Hubs Client] Enhance ReadMe #5449)
Event Hubs Client: Stabilize Live Tests ([Event Hubs Client] Stabilize Live Tests #5451)