Consider defining a single ARM crate with features for different services #1623
Labels
ARM
design-discussion
An area of design currently under discussion and open to team and community feedback.
feature-request
This issue requires a new behavior in the product in order be resolved.
Talking with @johanste, he brought up an idea we should consider: given the power of features for crates, could we introduce a new paradigm where we have a single ARM client but each service's models are behind a feature that just work with the ARM client? That ARM provides a universal pattern to CRUD resource operations is a benefit.
There is precedent: take the windows crate that Ryan Levick who also contributed a lot to the unofficial SDK created: different API sets are different features and you only pull those you need in. They may have dependencies on other features, but that is all implicit.
It's an interesting thought. We could have a single
azure::resourcemanager
with a client that can otherwise do it all given the right models, so long as those models can affect the endpoint - something we'd, little doubt, have to define ourselves.The text was updated successfully, but these errors were encountered: