regenerate services

[demoray]

ref: Azure/azure-rest-api-specs@7c906b1

[demoray]

The only manual configuration was to ignore a preview tag for defining an object twice.

[heaths]

I don't think this is a sustainable model. We don't build SDKs for all services. Each SDK that we do generate is done so when the service is updated. If we keep updating all sources like this, there will always be differences from generators thus clients won't be stable. Perhaps it's moot since we're not a stable version (and won't be until official, at the very least), but perhaps we need to rethink when/how we regenerate.

[demoray]

I don't think this is a sustainable model. We don't build SDKs for all services. Each SDK that we do generate is done so when the service is updated. If we keep updating all sources like this, there will always be differences from generators thus clients won't be stable. Perhaps it's moot since we're not a stable version (and won't be until official, at the very least), but perhaps we need to rethink when/how we regenerate.

I agree this isn't sustainable as is. The Go SDK used this model for some time and has since moved to the "sdk-release-request" model, which aligns to the idea you commented on, generating based on service update.

IMO, this is one of the multitude of things we will need to adjust to align to the SDK release process as part of the "becoming official" process.