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
* 'main' of https://github.com/Azure/azure-sdk-for-python: (127 commits)
[tool]update llc-quick-start-tool for py3 only (Azure#22507)
[mgmt] update setupy for python3.6 (Azure#22505)
[pipeline] Upgrade python version to `python3.8` (Azure#22503)
[AutoRelease] t2-synapse-2022-01-11-70733 (Azure#22439)
Update tests.md (Azure#22500)
disable per Azure#22498 (Azure#22499)
[AnomalyDetector] Release 3.0.0b4 (Azure#22191)
[translation] update docs to include managed identity option (Azure#22366)
add back py3.6 (Azure#22478)
Add Python 3.6 support back to Storage packages (Azure#22483)
allow Python 3.6 with the sdk (Azure#22456)
remove hardcoded subscription ID (Azure#22481)
clean up tests/docs (Azure#22480)
Increment version for eventhub releases (Azure#22485)
[Cosmos] Remove support for Python27, set Python36 as minimum, and update cosmos emulator pipeline (Azure#22475)
Increment version for servicebus releases (Azure#22484)
add back py3.6 (Azure#22477)
[AutoRelease] t2-datafactory-2022-01-06-31864 (Azure#22362)
[AutoRelease] t2-apimanagement-2022-01-06-51326 (Azure#22361)
[AutoRelease] t2-netapp-2022-01-12-75881 (Azure#22467)
...
Copy file name to clipboardExpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ This repository is for active development of the Azure SDK for Python. For consu
6
6
7
7
## _Disclaimer_
8
8
9
-
_Azure SDK Python packages support for Python 2.7 is ending 01 January 2022. For more information and questions, please refer to https://github.com/Azure/azure-sdk-for-python/issues/20691_
9
+
_Azure SDK Python packages support for Python 2.7 has ended 01 January 2022. For more information and questions, please refer to https://github.com/Azure/azure-sdk-for-python/issues/20691_
Copy file name to clipboardExpand all lines: doc/dev/private_package/python_multiapi_configuration.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ the target tag should only contain files from one folder:
16
16
17
17

18
18
19
-
If your tag contains files from different folders, you need to define some split tags. For example: `ApplicationInsights` has [Tag: package-2021-11-01](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/applicationinsights/resource-manager#tag-package-2021-11-01), but it contains different folders. If you want to publish the package for the tag, you need to split it to different tags: [[applicationinsights\] python multiapi config by RAY-316 · Pull Request #16799 · Azure/azure-rest-api-specs (github.com)](https://github.com/Azure/azure-rest-api-specs/pull/16799/files)
19
+
If your tag contains files from different folders, you need to define some split tags. For example: `ApplicationInsights` has [Tag: package-2021-11-01](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/applicationinsights/resource-manager#tag-package-2021-11-01), but it contains different folders. If you want to publish the package for the tag, you need to split it to different tags: [sample](https://github.com/Azure/azure-rest-api-specs/pull/16799/files)
Copy file name to clipboardExpand all lines: doc/dev/tests.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -162,7 +162,7 @@ If your library has a management plane library, you can build a preparer specifi
162
162
163
163
1. Create an Azure Resource Management Template for your specific service and the configuration you need. This can be done in the portal by creating the resources and at the very last step (Review + Create) clicking "Download a template for automation". Save this template to a `test-resources.json` file under the directory that contains your library (`sdk/<my-library>/test-resources.json`).
164
164
2. Use the [`New-TestResources.ps1`](https://github.com/Azure/azure-sdk-for-python/tree/main/eng/common/TestResources#on-the-desktop) script to deploy those resources.
165
-
3. Set the environment variables returned from step 2 in your current shell or add them to your `.env` file at the root of the repo to save these secrets. If you choose the latter method, you will have to make sure all the key-value pairs are in the format `<key_name>=<value>`, rather than the `${env:<key_name>} = '<value>'` formatting used in PowerShell. The names of the environment variables should be in all capital letters, snake case, and be prefixed with the library name. Ie. `TABLES_PRIMARY_KEY`, `FORMRECOGNIZER_ACCOUNT_URL`, `EVENTHUBS_SECRET_KEY`.
165
+
3. Set the environment variables returned from step 2 in your current shell or add them to your `.env` file at the root of the repo to save these secrets. If you choose the latter method, you will have to make sure all the key-value pairs are in the format `<key_name>=<value>`, rather than the `${env:<key_name>} = '<value>'` formatting used in PowerShell. The names of the environment variables should be in all capital letters, snake case, and be prefixed with the library name. Ie. `TABLES_PRIMARY_KEY`, `FORMRECOGNIZER_ACCOUNT_URL`, `EVENTHUBS_SECRET_KEY`. If the name of the service is more than one word, like Form Recognizer, don't include an underscore between the words. Use `FORMRECOGNIZER_ACCOUNT_URL`, not `FORM_RECOGNIZER_ACCOUNT_URL`.
166
166
4. Create a partial implementation of the PowerShellPreparer to pass in your specific environment variables. An example implementation is shown below for schemaregistry
0 commit comments