You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add enable-sync-stack: true to Code generation settings in respective swagger/autorest.md
Using this generation setting, autorest should generate sync equivalent overloads for all the API's.
Initialize the respective SDK sync client to use a service impl variable similar to what we do with the async client.
Use the initialized service impl directly to call into the respective Sync API rather than blocking the async client call. Example commit
Enable AssertingClient Testing, this makes sure sync call API's are running in completely synchronous call stack.
Validate the changes by running LIVE test pipeline on the PR.
Run Perf analysis and compare data to understand the impact of the changes.
Update the context for service API's that cannot be onboarded sync stack workflow as follows: private static final String HTTP_REST_PROXY_SYNC_PROXY_ENABLE = "com.azure.core.http.restproxy.syncproxy.enable"; context.addData(HTTP_REST_PROXY_SYNC_PROXY_ENABLE, false)
Known Issues when generating with the latest Autorest:
Make sure to use latest locally compiled autorest version. autorest --java --use=C:\~\Autorest\autorest.java --use:@autorest/modelerfour@4.23.7
Change from Mono<StreamResponse> to Mono<SomeObjectResponse> is intended.
Steps to onboard sync stack workflow for SDK's:
Add
enable-sync-stack: true
toCode generation settings
in respective swagger/autorest.mdUsing this generation setting, autorest should generate sync equivalent overloads for all the API's.
Initialize the respective SDK sync client to use a service impl variable similar to what we do with the async client.
Use the initialized service impl directly to call into the respective
Sync
API rather than blocking the async client call.Example commit
Enable AssertingClient Testing, this makes sure sync call API's are running in completely synchronous call stack.
Validate the changes by running LIVE test pipeline on the PR.
Run Perf analysis and compare data to understand the impact of the changes.
Known Issues when generating with the latest Autorest:
autorest --java --use=C:\~\Autorest\autorest.java --use:@autorest/modelerfour@4.23.7
Mono<StreamResponse>
toMono<SomeObjectResponse>
is intended.SDK's to be onboarded:
DPG Libraries - #33249
Partner team SDK's to be onboarded: - #33250
The text was updated successfully, but these errors were encountered: