Merge branch 'main' into hotfix/azure-ai-evaluation/1.13.1

Author: slister1001

.github/CODEOWNERS

@@ -320,6 +320,10 @@
 # PRLabel: %Operator Nexus - Network Cloud
 /sdk/networkcloud/                                                   @Azure/azure-sdk-write-networkcloud
 
+# ServiceLabel: %Planetary Computer
+# PRLabel: %Planetary Computer
+/sdk/planetarycomputer/                                              @mandarinamdar @chahibi
+
 # AzureSdkOwners: @annatisch
 # ServiceLabel: %Azure Projects
 # ServiceOwners: @annatisch

doc/dev/mgmt/sdk-breaking-changes-guide.md

@@ -205,16 +205,31 @@ op IotDpsResourceGetCustomized(
 );
 ```
 
-## 6. Removal of Unreferenced Models
+## 6. Common Types Upgrade
+
+**Changelog Pattern**:
+
+Multiple changes related to common infrastructure types such as `SystemData` and `IdentityType`:
+
+```md
+- Deleted or renamed model `IdentityType`
+```
+
+**Reason**: Common types are upgraded to their latest versions during TypeSpec migration.
+
+**Impact**: Low impact since these are common infrastructure types rarely used directly by users.
+
+**Resolution**: Accept these breaking changes.
+
+## 7. Removal of Unreferenced Models
 
 **Changelog Pattern**:
 
 Multiple removals of unreferenced models that are typically not used in the SDK:
 
 ```md
-- Deleted or renamed model `ReplicationUsageList`
-- Deleted or renamed model `VaultList`
-- Deleted or renamed model `VaultUsageList`
+- Deleted or renamed model `ProxyResourceWithoutSystemData`
+- Deleted or renamed model `Resource`
 ```
 
 **Reason**: Unreferenced models are removed during TypeSpec migration.
@@ -223,7 +238,27 @@ Multiple removals of unreferenced models that are typically not used in the SDK:
 
 **Resolution**: Accept these breaking changes.
 
-## 7. Parameters Changed to Keyword-only
+## 8. Removal of Pageable Models
+
+**Changelog Pattern**:
+
+Multiple removals of models following the pattern `xxxList`:
+
+```md
+- Deleted or renamed model `ElasticSanList`
+- Deleted or renamed model `SkuInformationList`
+- Deleted or renamed model `SnapshotList`
+- Deleted or renamed model `VolumeGroupList`
+- Deleted or renamed model `VolumeList`
+```
+
+**Reason**: Python will not expose pageable models for list APIs.
+
+**Impact**: Low impact since these models are typically not used directly by users.
+
+**Resolution**: Accept these breaking changes.
+
+## 9. Parameters Changed to Keyword-only
 
 **Changelog Pattern**:
 
@@ -239,7 +274,7 @@ Entries showing the usage of passing parameters positionally is disabled:
 
 **Resolution**: Accept these breaking changes.
 
-## 8. Removal of Parameter `if_match`
+## 10. Removal of Parameter `if_match`
 
 **Changelog Pattern**:
 
@@ -257,7 +292,7 @@ Removal of parameter `if_match` and addition of `etag/match_condition` for the s
 
 **Resolution**: Accept these breaking changes.
 
-## 9. Removal of multi-level flattened properties
+## 11. Removal of multi-level flattened properties
 
 **Changelog Pattern**:
 

doc/dev/test_proxy_troubleshooting.md

@@ -275,6 +275,9 @@ To run recorded tests successfully when recorded values are inconsistent or rand
 proxy provides a `variables` API. This makes it possible for a test to record the values of variables that were used
 during recording and use the same values in playback mode without a sanitizer.
 
+Note that the recorded variables **must** have string values. For example, trying to record an integer value for a
+variable will cause a test proxy error.
+
 For example, imagine that a test uses a randomized `table_uuid` variable when creating resources. The same random value
 for `table_uuid` can be used in playback mode by using this `variables` API.
 
@@ -293,14 +296,14 @@ class TestExample(AzureRecordedTestCase):
     @recorded_by_proxy
     def test_example(self, **kwargs):
         # In live mode, variables is an empty dictionary
-        # In playback mode, the value of variables is {"table_uuid": "random-value"}
+        # In playback mode, the value of variables is {"current_time": "<previously recorded time>"}
         variables = kwargs.pop("variables", {})
 
-        # To fetch variable values, use the `setdefault` method to look for a key ("table_uuid")
-        # and set a real value for that key if it's not present ("random-value")
-        table_uuid = variables.setdefault("table_uuid", "random-value")
+        # To fetch variable values, use the `setdefault` method to look for a key ("current_time")
+        # and set a real value for that key if it's not present (str(time.time()))
+        # Note that time.time() is converted from a float to a string to record it properly
+        current_time = variables.setdefault("current_time", str(time.time()))
 
-        # use variables["table_uuid"] when using the table UUID throughout the test
         ...
 
         # return the variables at the end of the test to record them

eng/ci_tools.txt

@@ -11,7 +11,7 @@ pkginfo==1.12.1.2
 pip==24.0
 typing-extensions==4.12.2
 pyproject-api==1.8.0
-cibuildwheel==2.16.5
+cibuildwheel==2.23.3
 importlib-metadata==8.5.0
 build==1.2.2.post1
 

eng/common/instructions/azsdk-tools/check-package-validation.instructions.md

@@ -0,0 +1,23 @@
+---
+description: 'Run the package validation checks for the SDK package.'
+---
+## Goal
+Run the validation checks for the SDK package by collecting the required information from the user and executing the `azsdk_package_run_check` tool.
+
+## Instructions
+1. **Collect Required Information**:
+    - Prompt the user for the absolute package path to the package directory for the SDK package they want to check.
+    - Prompt the user to specify values for each of the parameters required by the azsdk_package_run_check tool. Present the user with options to pick from for the allowed values specified by the parameter schema.
+
+2. **Execute Check**:
+    - Use the `azsdk_package_run_check` tool with the package path and check type.
+
+3. **Present Results**:
+    - If the package has passed all validation checks, highlight and finish
+    - If the package is not ready, display the specific check types that need to be fixed for each language.
+
+## Expected User Interaction Flow
+1. Ask: "What is the exact path of the package you want to check for validation?"
+2. Ask: "Please specify the check type you want to run (e.g., 'all', 'linting', 'format', etc.)"
+3. Execute the check using the provided information
+4. Display results and next steps

eng/common/instructions/azsdk-tools/verify-setup.instructions.md

@@ -0,0 +1,20 @@
+---
+description: 'Verify Setup'
+---
+
+## Goal
+This tool verifies the developer's environment for SDK development and release tasks. It returns what requirements are missing for the specified languages and repo.
+
+Your goal is to identify the project repo root, and pass in the `packagePath` to the Verify Setup tool. For a language repo, pass in the language of the repo.
+
+## Examples
+- in `azure-sdk-for-js`, run `azsdk_verify_setup` with `(langs=javascript, packagePath=<path>/azure-sdk-for-js)`.
+- in `azure-sdk-for-python`, run `azsdk_verify_setup` with `(langs=python, packagePath=<path>/azure-sdk-for-python, venvPath=<path-to-venv>)`.
+
+## Parameter Requirements
+WHENEVER Python is included in `langs`, BEFORE RUNNING `azsdk_verify_setup`, you MUST ASK THE USER TO SPECIFY WHICH virtual environment they want to check. DO NOT ASSUME THE VENV WITHOUT ASKING THE USER. After obtaining the `venvPath`, you can run the tool.
+
+The user can specify multiple languages to check. If the user wants to check all languages, pass in ALL supported languages and STILL ASK for a `venvPath`. Passing in no languages will only check the core requirements.
+
+## Output
+Display results in a user-friendly and concise format, highlighting any missing dependencies that need to be addressed.