diff --git a/sdk/batch/Microsoft.Azure.Management.Batch/README.md b/sdk/batch/Microsoft.Azure.Management.Batch/README.md index ec44899a7392..bf5c24a1c7d9 100644 --- a/sdk/batch/Microsoft.Azure.Management.Batch/README.md +++ b/sdk/batch/Microsoft.Azure.Management.Batch/README.md @@ -5,7 +5,8 @@ * Add new APIs as path-verb pairs in the Swagger specification. * Add/remove properties on existing entity types in the Swagger specification. 2. Regenerate the SDK based using [AutoRest](https://github.com/Azure/autorest) on the updated Swagger specification: - * `Start-AutoRestCodeGeneration -SdkRepoRootPath -ResourceProvider "batch/resource-manager" -AutoRestVersion "latest" -SdkGenerationDirectory "\sdk\batch\Microsoft.Azure.Management.Batch\src\generated" -ConfigFileTag "package-2020-03"` + * See this document for more information: https://github.com/Azure/adx-documentation-pr/blob/master/engineering/adx_netsdk_process.md#sdk-generation-from-updated-spec + * Run the command from the root of the repo: `sdk/batch/Microsoft.Azure.Management.Batch/src/generate.ps1` 3. Add new tests for your new models and APIs. There are two types of tests, "recorded" tests and unit tests: * Recorded tests are run live and the request/response payloads are recorded and then replayed for subsequent runs. * Unit tests are in-memory tests which never actually make a REST call. @@ -13,4 +14,4 @@ 4. Update the `CHANGELOG.md` file and the `Version` tag in `src/Microsoft.Azure.Management.Batch.csproj`. Ensure that if you are making a breaking change, you update the major version of the version number. 5. Re-record all of the recording tests against the new API version (see [here](https://github.com/Azure/azure-sdk-for-net/blob/master/doc/dev/Using-Azure-TestFramework.md) for details on how to use the recording framework). 6. Switch test mode back to `Playback` and ensure that all of the tests pass. -7. Open a PR to https://github.com/Azure/azure-sdk-for-net. \ No newline at end of file +7. Open a PR to https://github.com/Azure/azure-sdk-for-net.