Decoupling from Azure #1837
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
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 yourREADME.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
The text was updated successfully, but these errors were encountered: