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.

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

[Event Hubs] Migrate Client Code into Central Repository #5448

Closed
jsquire opened this issue Mar 14, 2019 · 1 comment
Closed

[Event Hubs] Migrate Client Code into Central Repository #5448

jsquire opened this issue Mar 14, 2019 · 1 comment
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Milestone

Comments

@jsquire
Copy link
Member

jsquire commented Mar 14, 2019

  • Perform the initial restructuring of the repository to isolate the management library.

  • Ensure that the management library can be built and that tests continue to pass after the restructure.

  • Migrate the Event Hubs client source into the central repository.

  • Restructure the client library to integrate with the engineering system, ensuring that it can be build and that tests continue to pass.

  • Remove, update, or create assets for the client library, such that there is clean integration with the established standards of the central repository.

  • Categorize each test from the client library test suite such that any tests which require connectivity to Azure in order to be valid are denoted with a trait named TestCategory and value of Live.

  • Ensure that the client library can be built and that tests continue to pass after the initial adoption.

@jsquire jsquire added this to the Sprint 151 milestone Mar 14, 2019
@jsquire jsquire self-assigned this Mar 14, 2019
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. Event Hubs labels Mar 14, 2019
jsquire added a commit to jsquire/azure-sdk-for-net that referenced this issue Mar 22, 2019
    Repository Structure
      - Reorganize the Event Hubs SDK root directory, moving the management library into an isolated directory.
jsquire added a commit that referenced this issue Mar 22, 2019
…cture

[Event Hubs Client] Migrate Code into Central Repository (#5448)
@jsquire jsquire changed the title [Event Hubs Client] Migrate Code into Central Repository [Event Hubs] Migrate Client Code into Central Repository Apr 5, 2019
@jsquire
Copy link
Member Author

jsquire commented Apr 17, 2019

Pending a decision on target frameworks for the project; the open proposal is to replace the Xamarin.iOS10 and uap10.0 targets with netstandard1.4, with hidden certificate authentication in order to conform to the limits of the Identity Model client for Azure Active Directory package used.

@jsquire jsquire closed this as completed Apr 26, 2019
mentat9 pushed a commit to mentat9/azure-sdk-for-net that referenced this issue Jun 10, 2019
    Repository Structure
      - Reorganize the Event Hubs SDK root directory, moving the management library into an isolated directory.
@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Development

No branches or pull requests

1 participant