Azure.KeyVault SDK models lacks serialization methods

• azure_keyvault_keys:
• 4.3.1:
• Linux:
• 3.8.5:

Describe the bug Latest version of Azure.Keyvault SDKs don’t have serialization in the models.

Models in this file don’t inherit msrest, so there is no easy serialization available. https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/keyvault/azure-keyvault-keys/azure/keyvault/keys/_models.py

Same goes to Secrets and Certificates.

To Reproduce Steps to reproduce the behavior: 1.

Expected behavior Azure Python SDK has consistent experience and all models have serialization available.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context Add any other context about the problem here.

[logachev]

@annatisch I’ll need a few days to try this approach, but it looks promising… 😃

Also, I think part of my feedback is lack of consistency… I know Track 2 was supposed to bring unified approach to the SDKs and for some things I feel like it is amazing… However, end users don’t really follow what models are handcrafted and what models are autogenerated… It would be great if there was some baseline that is consistent across mgmt and data plane SDKs!

[logachev]

Yeah, this is an update scenario from prior azure-keyvault package… https://github.com/cloud-custodian/cloud-custodian

Primarily we need it to transform resource to the dict for further usage. The tool itself doesn’t know details about KeyVault objects, but it requires common representation for all Azure resource objects and dict suits this for out use case.

Another scenario is just saving Azure object info into a file. At the moment, json.dumps() can’t handle KeyVault objects.