From 33ccf1cedbfaf593a9159939d1c08632ac3f3e46 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?McCoy=20Pati=C3=B1o?= <39780829+mccoyp@users.noreply.github.com> Date: Fri, 26 Jul 2024 17:39:49 -0700 Subject: [PATCH] Account for OS in PATH-setting (#36658) --- doc/dev/recording_migration_guide.md | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/doc/dev/recording_migration_guide.md b/doc/dev/recording_migration_guide.md index 9a24e471b9ba..1870bb113313 100644 --- a/doc/dev/recording_migration_guide.md +++ b/doc/dev/recording_migration_guide.md @@ -65,20 +65,28 @@ This script -- [`generate-assets-json.ps1`][generate_assets_json] -- should be r In a PowerShell window: 1. Add the test proxy executable to `PATH` if it's not already present. This can be done by adding the path to the - `.proxy` folder at the base of your Python repo. For example, if the Python repo is at `C:\azure-sdk-for-python`, - you can add the test proxy to `PATH` for the current session by running: + `.proxy` folder at the base of your Python repo. You can add the test proxy to `PATH` for the current session by + running the following: + - On Windows: ```PowerShell -$env:Path += ';C:\azure-sdk-for-python\.proxy' +$env:PATH += ';\azure-sdk-for-python\.proxy' ``` -2. Set your working directory to the root of the package you're migrating (`sdk/{service}/{package}`) -- for example: + - On Mac or Linux: +```PowerShell +$env:PATH += ':/azure-sdk-for-python/.proxy' +``` + +2. Run `echo $env:PATH` to inspect `PATH` and confirm that the proxy path was correctly appended. + +3. Set your working directory to the root of the package you're migrating (`sdk/{service}/{package}`) -- for example: ```PowerShell -cd C:\azure-sdk-for-python\sdk\keyvault\azure-keyvault-keys +cd \azure-sdk-for-python\sdk\keyvault\azure-keyvault-keys ``` -3. Run the following command: +4. Run the following command: ```PowerShell ..\..\..\eng\common\testproxy\onboarding\generate-assets-json.ps1 -InitialPush