Merge branch 'Azure:main' into main

Author: tvaron3

.github/CODEOWNERS

@@ -179,7 +179,7 @@
 /sdk/monitor/azure-monitor-ingestion/                                @pvaneck @Azure/azure-sdk-write-monitor-data-plane
 
 # PRLabel: %Monitor
-/sdk/monitor/azure-monitor-query/                                    @pvaneck @Azure/azure-sdk-write-monitor-data-plane
+/sdk/monitor/azure-monitor-query/                                    @Azure/azure-sdk-write-monitor-query-logs
 
 # PRLabel: %Monitor
 /sdk/monitor/azure-monitor-querymetrics/                             @Azure/azure-sdk-write-monitor-query-metrics

.github/workflows/azure-sdk-tools.yml

@@ -13,10 +13,10 @@ jobs:
     steps:
       - uses: actions/checkout@v2
 
-      - name: Set up Python 3.11
+      - name: Set up Python 3.13
         uses: actions/setup-python@v4
         with:
-          python-version: 3.11
+          python-version: 3.13
 
       - name: Install azure-sdk-tools
         run: |

.vscode/cspell.json

@@ -558,9 +558,9 @@
       ]
     },
     {
-      "filename": "doc/dev/test_proxy_migration_guide.md",
+      "filename": "doc/dev/credscan_process.md",
       "words": [
-        "pytestmarkparametrize"
+        "CSCAN"
       ]
     },
     {

doc/dev/credscan_process.md

@@ -67,21 +67,9 @@ Suppressing string values will disable warnings no matter where the string comes
 and inconvenient for lengthy strings. Suppressing warnings in a file is convenient for fake credential files, but
 strings in that file will still trigger warnings if present in another unsuppressed file.
 
-## Correct baselined warnings
-
-In addition to active warning that appear in the [python - aggregate-reports][aggregate_reports] pipeline ouput, there
-are also CredScan warnings that have been suppressed in [eng/python.gdnbaselines][baseline]. This file is a snapshot of
-the active warnings at one point in time; CredScan won't re-raise warnings that have been recorded here.
-
-Ultimately, we hope to remove this baseline file from the repository entirely. If you see any warnings for a package
-that you own in this file, please remove a few at a time from the file so that CredScan will output these warnings in
-the pipeline. Then, resolve them following the steps from the [Correct active warnings](#correct-active-warnings)
-section of this guide.
-
 
 [aggregate_reports]: https://dev.azure.com/azure-sdk/internal/_build?definitionId=1401&_a=summary
 [aggregate_reports_output]: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1411446&view=logs&j=9e400fad-ff47-5b38-f9dc-cae2431972da&t=8613334a-c306-55ea-63ff-80c6e8e0a0ca
-[baseline]: https://github.com/Azure/azure-sdk-for-python/blob/main/eng/python.gdnbaselines
 [ci_scan_output]: https://dev.azure.com/azure-sdk/public/_build/results?buildId=1426258&view=logs&jobId=b70e5e73-bbb6-5567-0939-8415943fadb9&j=bc67675d-56bf-581f-e0a2-208848ba68ca&t=7eee3a58-6120-518b-7fcb-7e943712aa81
 [credscan_doc]: https://aka.ms/credscan
 [devops_doc]: https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/413/Credential-Scan-Step-in-Pipeline

doc/dev/mgmt/generating-integration-test.md

@@ -96,11 +96,7 @@ You can rearrange sequence or disable particular tests.
 ## Running Test
 
 To run tests, refer to the documentation at
-[/doc/dev/mgmt/tests.md](https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/mgmt/tests.md). Most test
-suites in the Azure SDK have been migrated to use the Azure SDK test proxy, but some libraries that have inactive tests
-may still be using an older, deprecated system. The
-[test proxy migration guide](https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/test_proxy_migration_guide.md)
-describes the differences between the systems and their requirements.
+[/doc/dev/mgmt/tests.md](https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/mgmt/tests.md).
 
 ## Fixing Test
 

doc/dev/mgmt/multiapi.md

@@ -112,7 +112,7 @@ o
 
 If this is the same API version, since they will be packed together that's ok (for instance [compute](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2019-03-01/compute.json) and [runcommands](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2019-03-01/runCommands.json) shares `VirtualMachines_` but exists always in the same API version)
 
-If this is not the same API version, then we need to bend the rules a little: we need to understand the intent, and decide which API version we use as folder to ship both (example: [ACR 2019-05-01](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/stable/2019-05-01/containerregistry.json) and [registry build 2019-06-01-preview](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/preview/2019-06-01-preview) are shipped as [2019-06-01-preview](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/containerregistry/azure-mgmt-containerregistry/azure/mgmt/containerregistry/v2019_06_01_preview) because they share `BuildRegistry_` operation group).
+If this is not the same API version, then we need to bend the rules a little: we need to understand the intent, and decide which API version we use as folder to ship both (example: [ACR 2019-05-01](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/stable/2019-05-01/containerregistry.json) and [registry build 2019-06-01-preview](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/containerregistry/resource-manager/Microsoft.ContainerRegistry/preview/2019-06-01-preview) were shipped as [2019-06-01-preview](https://github.com/Azure/azure-sdk-for-python/tree/24e4a701802b82832d97f125c6c96567c8e4448e/sdk/containerregistry/azure-mgmt-containerregistry/azure/mgmt/containerregistry/v2019_06_01_preview) because they share `BuildRegistry_` operation group).
 
 ## Possible improvements
 

doc/dev/mgmt/tests.md

@@ -190,7 +190,7 @@ This simple test creates a resource group and checks that its name is assigned c
 
 Notes:
 1. This test inherits all necessary behavior for HTTP recording and playback described previously in this document from its `AzureMgmtRecordedTestCase` superclass. You don't need to do anything special to implement it.
-2. The `get_resource_name()` helper method of `AzureMgmtRecordedTestCase` creates a pseudorandom name based on the parameter and the names of the test file and method. This ensures that the name generated is the same for each run of the same test, ensuring reproducability and preventing name collisions if the tests are run live and the same parameter is used from several different tests.
+2. The `get_resource_name()` helper method of `AzureMgmtRecordedTestCase` creates a pseudorandom name based on the parameter and the names of the test file and method. This ensures that the name generated is the same for each run of the same test, ensuring reproducibility and preventing name collisions if the tests are run live and the same parameter is used from several different tests.
 3. The `create_mgmt_client()` helper method of `AzureMgmtRecordedTestCase` creates a client object using the credentials from `mgmt_settings_fake.py` or `mgmt_settings_real.py` as appropriate, with some checks to make sure it's created successfully and cause the unit test to fail if not. You should use it for any clients you create.
 4. While the test cleans up the resource group it creates, you will need to manually delete any resources you've created independent of the test framework. But if you need something like a resource group as a prerequisite for what you're actually trying to test, you should use a "preparer" as demonstrated in the following two examples. Preparers will create and clean up helper resources for you.
 
@@ -211,7 +211,7 @@ class TestMgmtSearch(AzureMgmtRecordedTestCase):
     @ResourceGroupPreparer()
     @recorded_by_proxy
     def test_search_services(self, resource_group, location):
-        account_name = self.get_resource_name(''ptvstestsearch')
+        account_name = self.get_resource_name('search')
 
         service = self.client.services.begin_create_or_update(
             resource_group.name,
@@ -327,7 +327,7 @@ class TestMgmtSearch(AzureMgmtRecordedTestCase):
     @ResourceGroupPreparer(client_kwargs={'base_url':_CUSTOM_ENDPOINT})
     @recorded_by_proxy
     def test_search_services(self, resource_group, location):
-        account_name = self.get_resource_name(''ptvstestsearch')
+        account_name = self.get_resource_name('search')
 
         service = self.client.services.begin_create_or_update(
             resource_group.name,
@@ -357,5 +357,5 @@ class TestMgmtSearch(AzureMgmtRecordedTestCase):
 [dev_setup]: https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/dev_setup.md
 [devtools_testutils]: https://github.com/Azure/azure-sdk-for-python/tree/main/tools/azure-sdk-tools/devtools_testutils
 [mgmt_settings_fake]: https://github.com/Azure/azure-sdk-for-python/blob/main/tools/azure-sdk-tools/devtools_testutils/mgmt_settings_fake.py
-[testproxy]: https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/test_proxy_migration_guide.md
+[testproxy]: https://github.com/Azure/azure-sdk-for-python/blob/main/doc/dev/tests.md#write-or-run-tests
 [pytest]: https://docs.pytest.org/en/latest/