Back at the beginning of the ADP team, autorest was used from a branch called "azure-core", which was still the C# generator bu adapted for track2./
The point of this issue, is to regenerate any SDK that are still wrapping code from that period, with autorest.python v5.x.
This issue is NOT about making sure the latest autorest is used (though this could be useful), but to be sure we can archive the "azure-core" branch on the autorest repo, and there is no magic that was done at that time that we rely on in our current SDK.
This issue should start with an inventory of such SDK (I believe Storage at least), and regenerate them and re-test them.
Back at the beginning of the ADP team, autorest was used from a branch called "azure-core", which was still the C# generator bu adapted for track2./
The point of this issue, is to regenerate any SDK that are still wrapping code from that period, with autorest.python v5.x.
This issue is NOT about making sure the latest autorest is used (though this could be useful), but to be sure we can archive the "azure-core" branch on the autorest repo, and there is no magic that was done at that time that we rely on in our current SDK.
This issue should start with an inventory of such SDK (I believe Storage at least), and regenerate them and re-test them.