### Packages impacted by this PR
- `@azure/template`
### Describe the problem that is addressed by this PR
Grants the "App Configuration Data Owner" when deploying the template
live test resources. This fixes some issues recording tests for the
template package (and possibly the live tests too).
Copied from the App Config test-resources.bicep
[here](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/appconfiguration/test-resources.bicep)
### Packages impacted by this PR
@azure-rest/ai-inference
### Issues associated with this PR
N/A
### Describe the problem that is addressed by this PR
`@azure/core-tracing` will release as 1.2.0 as per
https://github.com/Azure/azure-sdk-for-js/pull/31272/files
This PR prepares ai-inference to use the correct version of
`@azure/core-tracing` and get support for `addEvent`
### Packages impacted by this PR
- @azure/create-microsoft-playwright-testing
### Issues associated with this PR
### Describe the problem that is addressed by this PR
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
One of the template tests has been flaky on Mac OS. Given that template
is run as part of core and likely most PRs we decided to pend the test
for now and investigate it as part of #31296
### Packages impacted by this PR
@azure/dev-tool
### Issues associated with this PR
Resolves#29672
### Describe the problem that is addressed by this PR
With the move to ESM and tshy we've been running into issues using the
existing TS_NODE
based loader in dev-tool. Specifically we're seeing errors such as:
```
[run-samples] Error: Must use import to load ES Module: D:\a_work\1\s\sdk\template\template\samples-dev\getConfigurationSetting.ts
require() of ES modules is not supported.
require() of D:\a_work\1\s\sdk\template\template\samples-dev\getConfigurationSetting.ts from D:\a_work\1\s\common\tools\dev-tool\src\commands\samples\run.ts is an ES module file as it is a .ts file whose nearest parent package.json contains "type": "module" which defines all .ts files in that package scope as ES modules.
Instead change the requiring code to use import(), or remove "type": "module" from D:\a_work\1\s\sdk\template\template\package.json.
```
ts-node is being phased out for tsx, a modern alternative that handles
hybrid scenarios like us in much simpler manner.
This PR switches our loader from ts-node to tsx. Now we can run samples
again for both cjs and esm!
### Packages impacted by this PR
- `@azure-rest/core-client`
### Issues associated with this PR
- Fixes#30943
- Fixes#30944
### Describe the problem that is addressed by this PR
Adds support for passing in an object as a query or path parameter. At
present, this object allows for the user to specify a couple of
encoding-related options in addition to the value of the parameter:
- For path parameters: `allowReserved` can be set to true to indicate
that special characters appearing in the parameter should not be
URL-encoded. This allows for path parameters to contain characters like
`/`.
- For query parameters: `explode` can be set to true to change how
arrays are encoded. By default, array values are encoded as a single
query parameter, with each value separated by a comma (e.g. `foo=a,b,c`.
With `explode` set to true, each array value will be converted into a
single query parameter (e.g. `foo=a&foo=b&foo=c`).
***NO_CI***
Currently the rule only handles the case of
```ts
clientMethod(options: MethodOptions) {}
```
but not when the options bag parameter has a default value
```ts
clientMethod(options: MethodOptions = {}) {}
```
This change adds code to handle the latter.
- Add two unit tests
- Update the affected packages to suppress this rule as a warning
- react to the fix
### Packages impacted by this PR
@azure/opentelemetry-instrumentation-azure-sdk
### Issues associated with this PR
Resolves#31287
### Describe the problem that is addressed by this PR
Looks like Sinon's matchers are a little looser than vitest's - while we
are calling inject with 3 arguments we only care about the first in this
test.
This PR restores the tests and updates the assertion
### Packages impacted by this PR
- @azure/opentelemetry-instrumentation-azure-sdk
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Migrates the package to ESM and vitest. Note one issue with mocking with
the propagator object.
### What are the possible designs available to address the problem? If
there are more than one possible design, why was the one in this PR
chosen?
### Are there test cases added in this PR? _(If not, why?)_
### Provide a list of related PRs _(if any)_
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
### Checklists
- [ ] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Maor Leger <maorleger@users.noreply.github.com>
The baseline file suppresses errors and ideally should be empty. In this
PR, I'm trying to peel some of the low hanging fruit off like ensuring
our own team members are configured correctly and we're not assigning
issues to invalid labels.
### Packages impacted by this PR
@azure/dev-tool
### Issues associated with this PR
N/A - part of migrations
### Describe the problem that is addressed by this PR
A few quality-of-life improvements as I migrate keyvault packages to
ESM:
1. Allow skipping browser test configuration
2. Ensure linters are happy by appending an empty line to updated json files
3. Replace `tsc -p .` with `dev-tool run build-package` in the scripts section
4. Replace `@azure-tools/test-utils` with `@azure-tools/test-utils-vitest`
5. Remove `tshy` from the dependencies to add since `build-package` uses
a vendored tshy version
### Packages impacted by this PR
monitor-opentelemetry
### Describe the problem that is addressed by this PR
This PR adds live metrics filtering, for the metrics charts.
The change to fix the document spam bug is also here, but I will also
create a separate PR just for that.
There are a few things I didn't include in this PR that will be included
separate future PRs:
- filtering for documents on right hand pane. Currently this change just
emits all documents.
- changes to how CPU/Mem are to be collected for live metrics (per
process counters).
- Retry/caching logic for requests made to QuickPulse. Currently this PR
does not change this behavior, but for future parity with spec we should
consider caching live metrics data points when post requests fail &
reducing retries if there is a network error (considering ping/post
happens every few seconds anyway).
### Are there test cases added in this PR? _(If not, why?)_
Yes
### Checklists
- [x] Added impacted package name to the issue description
- [ ] Does this PR needs any fixes in the SDK Generator?** _(If so,
create an Issue in the
[Autorest/typescript](https://github.com/Azure/autorest.typescript)
repository and link it here)_
- [ ] Added a changelog (if necessary)
---------
Co-authored-by: Jackson Weber <jacksonweber@microsoft.com>
### Packages impacted by this PR
dev-tool
### Issues associated with this PR
### Describe the problem that is addressed by this PR
A few QoL additions as we aim to complete the ESM migration:
- output markdown
- Add verbose mode to output individual package status
I only focused on ESM migration as we plan to migrate ESM + Vitest in a
single commit. This all builds off of the work Matt started and allows us to
keep an up-to-date wiki for folks to follow the migration status
Azure SDK Bot
Timo van Veenendaal
Maor Leger
Matthew Podwysocki
Jeremy Meng
Jeff Fisher
Praven Kuttappan
cqnguy23
Jeremy Meng
ZiWei Chen
Harsimar Kaur
Hector Hernandez
Minh-Anh Phan