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

Decoupling from Azure #1837

Closed
2 tasks done
SamuelMarks opened this issue Jul 14, 2021 · 3 comments
Closed
2 tasks done

Decoupling from Azure #1837

SamuelMarks opened this issue Jul 14, 2021 · 3 comments
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@SamuelMarks
Copy link

Is your feature request related to a problem? Please describe.
Looking through your repo, a large portion of it seems to be generic and thus useful for consuming other APIs; outside Microsoft's official Azure one.

Describe the solution you'd like
Auth, example input, example output, sequence diagrams coupled with mock API showing how this all works. All without needing to call any Azure APIs (e.g., have a little server in your test directory which serves a little API using simple sockets (Windows + POSIX, à la src/tiny_web_server.cpp#L118-L122 but fully C).

Describe alternatives you've considered
Write a new one from scratch (benefit: I could license it under (Apache-2.0 OR MIT); and [initially] wouldn't have to worry about backwards-compatibility; disadvantage: time, [maybe] would make alt decisions you made better ones for).

Additional context
Would be good to just have your insights here. Like if there's any reason it couldn't be decoupled, and if it were decoupled what parts would you want to keep in this repo, or if you're encouraging a fork instead. Or if you want to keep the az namespace but still allow it to be generic, e.g., implementations for other client libraries, with their code either contributions directly to this repo or just listed in the "Used by" section of your README.md.

Information Checklist
Please make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

  • Description Added
  • Expected solution specified
@ghost ghost added needs-triage This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jul 14, 2021
@RickWinter
Copy link
Member

Thank you for taking the time to use the SDK and provide feedback. It is true the SDK may appear general purpose and parts of it could in theory serve other purposes. However with that said, the repo and the SDK are designed for, provided, and maintained to enable developers targeting Azure. We have no current plans to general purpose any part of this repository.

@RickWinter RickWinter added Azure.Core Client This issue points to a problem in the data-plane of the library. issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. labels Jul 19, 2021
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Jul 19, 2021
@ghost
Copy link

ghost commented Jul 19, 2021

Hi @SamuelMarks. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

@ghost
Copy link

ghost commented Jul 26, 2021

Hi @SamuelMarks, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.

@ghost ghost closed this as completed Jul 26, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 26, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

2 participants