Previously dev-tool has been fixed to generate correct include path in samples
tsconfig.json but samples were not updated.
This PR fixes the samples tsconfig.json in one run; otherwise with the recent
branch protection policy changes, when individual packages re-publish samples,
js-core team would have to approve the tsconfig.json changes.
***NO_CI***
which only extends from tsconfig.json. There might be more customization for
packages in the early days but not any more.
This PR removes it and updates packages to extends tsconfig.json directly
***NO_CI***
It helps old JS runtimes that only support ES 5 but we moved to ES 6
long time ago
and now moved to ES2017. Most of our packages don't have this option.
This PR
removes its usage.
### Packages impacted by this PR
@azure/app-configuration
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Use managed identity credential in the live test pipeline. Remove Tenant
ID, Client ID from new test resource script
In an ESLint configuration object, if an `ignores` key is used without any other
keys, then the patterns act as global ignores. I added a `name` in my previous
PR which broke it.
This PR fixes the issue by removing the extraneous name. A pattern of
`*.config.{js,cjs,mjs}` is also add to global ignores because we don't need to
lint them.
Also in this PR
- move app-configuration package to use Flat Config format as a test.
- enable cosmosdb test config that was in legacy config format but missed in migration.
### Packages impacted by this PR
App Config
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Remove secret-based authentication from the test suite. Rerecord the
test suite
### Packages impacted by this PR
- @azure/app-configuration
- @azure/cosmos
- @azure/monitor-opentelemetry
- @azure/monitor-opentelemetry-exporter
### Issues associated with this PR
- #29219
### Describe the problem that is addressed by this PR
Updates to latest `nock`.
### 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)
These tests were added before we have the azsdk bot automation to
increment version numbers and keep them in sync. They are less useful
now.
I also noticed the app-config test failed to catch the mismatch because
of missing constant entry in package.json. So I changed the test to
verify that version in user-agent header matches sdk version, following
the pattern in the keyvault tests.
### Packages impacted by this PR
@azure/app-configuration
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Run the prepare release script for GA release & remove sample
### Packages impacted by this PR
`@azure-tools/test-perf`
### Describe the problem that is addressed by this PR
Making perf package public for consumption outside this repo.
This marks the initial release of the `@azure-tools/test-perf` library
to npm, providing a robust test utility framework that assists with the
performance testing of Azure SDKs for JS/TS.
### Key Concepts
1. **Introduction of PerfTest**: A test utility designed to execute
performance and stress tests for Azure SDK for JavaScript packages.
2. **Test Execution**: Tests are run asynchronously, influenced by
parameters like duration, iterations, and parallelism.
3. **Command Line Parameters**: Utilizes `minimist` for parsing command
line options into a `PerfOptionDictionary<string>` for test
configuration.
4. **Default Options**: Includes standard parameters such as `help`,
`no-cleanups`, `parallel`, `duration`, `warmup`, `iterations`,
`no-cleanup`, and `milliseconds-to-log`.
5. **Test Lifecycle**: Tests run repeatedly within the specified
`duration` and `iterations`, with a `warmup` period for runtime
optimization.
6. **Setup and Cleanup**: Features `globalSetup`/`globalCleanup` methods
for CPU-level preparation and `setup`/`cleanup` methods for
instance-specific state management.
Builds off of Matt's work on moving to tsx in #28801 by removing the
`use-esm-workaround` flag from packages that needed it before we moved to tsx.
There's additional cleanup to be had, but I am trying not to cause a
build storm.
We are at a point where we can delete `esm` globally!
Contributes to #28617 which can be completed with a no-ci change to
remove `esm` globally
****NO_CI****
### Packages impacted by this PR
- @azure/app-configuration
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Removes dependency on `ts-node` and `esm` and moves in favor of using
`tsx`
### 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)
### Packages impacted by this PR
@azure/app-configuration
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Run prepare release script with the correct version
Adds two new features to the App config SDK
- [x] Support etags in the list by page method
- [ ] ~~Tags filter for the listing methods~~ (Wait on service)
- [x] Tests/recordings
- [x] Changelog
---------
Co-authored-by: Minh-Anh Phan <minhanhphan@microsoft.com>
- Switch to use esm4mocha loader by default
- Add `--use-esm-workaround=true` to packages that need more work
(mostly due to usage of `__dirname` that is no longer available in ESM)
- Change some usage of `__dirname` to `"."` when possible
- [esm4mocha] only transform modules whose format is changed
- [load-testing-rest] update tsconfig.json to be consistent with other
packages
This change migrates every package to the latest major version of
identity in order to ensure we can catch any regressions earlier in the
development process.
I chose to upgrade the samples' package.json as well - but happy to
revert that if there are objections.
***NO_CI***
Our tests use the type `Mocha.Context` when they need to pass the test context
to test recorder. However, without a dev dependency on `@types/mocha`
compilation may fail when recorder constructor is changed from taking a
`Mocha.Test` to taking an interface that is compatible.
This change ensures the dev depedency on `@types/mocha` too if there's a dev
dependency on `mocha`.
***NO_CI***
***NO_CI***
Latest versions of prettier now correctly formats `tsconfig.json`, which results
in differences with previous version of 3.1.1 in pnpm-lock.yaml. This is failing
the automated rush update pipeline because `check-format` fails with version
3.2.4.
This includes changes of
- bumping prettier version to ^3.2.4
- running `rush format`
***NO_CI***
- remove dev dependency `prettier` from non-tool packages when possible and
update them to run vendored prettier for `check-format` and `format` scripts
- upgrade rest of packages to prettier v3
- run `rush format` for all rush packages
This is a follow-up to https://github.com/Azure/azure-sdk-for-js/pull/28127 to
move the rest of repo to prettier v3.
### Packages impacted by this PR
- @azure/app-configuration
### Issues associated with this PR
### Describe the problem that is addressed by this PR
Removes the UUID module in favor of @azure/core-util.
### 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
- [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)
### Packages impacted by this PR
@azure/eventgrid
**API View To Approve**
https://apiview.dev/Assemblies/Review/30d6488f3dd647a79d175e408d5d5303?diffRevisionId=20bf158c9f2341eba08c706d55a0aa4c&diffOnly=False&revisionId=f5dd29153bf946c0aa1d47886fcd5eaf&doc=true
### Issues associated with this PR
NA
### Describe the problem that is addressed by this PR
The EventGrid Service Team has added 2 new events. The SDK must be
regenerated to include the code changes related to these 2 new events.
The SDK minor version has been updated.
- `Microsoft.ResourceNotifications.Resources.CreatedOrUpdated`
- `Microsoft.ResourceNotifications.Resources.Deleted`
### 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?
There are no specific/complex design scenarios for this task. It is a
straightforward regenerate and some standard changes to the custom layer
of the code.
One of the important issues to note down is that this release does have
a breaking change. The data type of `tags` property has been changed
from `string` to object. So, this is a breaking change. Accordingly, the
major version has been updated.
### Are there test cases added in this PR? _(If not, why?)_
No. This item is standard and we need not add test cases for every new
events. The existing cases would be sufficient.
### Provide a list of related PRs _(if any)_
- https://github.com/Azure/azure-sdk-for-js/pull/27384 (This is the PR
that adds similar events to the SDK in the 4.15.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/26939 (This is the PR
that adds similar events to the SDK in the 4.14.0 release)
- https://github.com/Azure/azure-sdk-for-js/pull/26020 (This is the PR
that adds similar events to the SDK in the 4.13.0 release)
### Command used to generate this PR:**_(Applicable only to SDK release
request PRs)_
`autorest --typescript swagger\README.md`
### 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)_
- [X] Added a changelog (if necessary)
@xirzec Please review and approve the PR and API View. Thanks
Some files are not formated in commits that were merged without CI. This
PR updates them with the result from `rush format`, and also fixes
`format` script for ts-http-runtime