Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

* Always use x-ms-date for Hmac

* Try to fix phone number tests

* Still another error in phone number tests

* Update phoneNumber session records

* Update phone numbers node sessions

* Manually fix node record sessions for phone numbers

* Update missed session files

Co-authored-by: JP Chen <jiach@microsoft.com>

This PR makes three changes to our deployment template:

- Add networkAcls to the Managed HSM properties
- Remove the 60 second sleep after activation
- Speed up challenge auth tests for KV Keys by using methods that don't require creating and deleting keys.

The first is now needed, and without it deployment will fail.
The second is no longer needed, since it looks like the az cli appropriately waits before coming back.
Finally, the third is something I noticed - there's no reason to create and purge keys which takes a long time in order to test CAE.

## What

- Bump @opentelemetry/api to 0.20.0 in @azure/core-tracing
- Move all packages that are on core-http to the next core-tracing version 
- Remove version collision check from the tracer cache

## Why

This is part of our effort to move everyone to OTel 0.20.0 - but we have to stage it due to a transitive dependency and a 
breaking change in OTel. This PR updates core-tracing to use the latest OTel, fixes any breaking changes, and moves 
packages that we can move to the latest version of core-tracing.

Once core-rest-pipeline 1.1.0 is GA'd we'll be able to move the rest of the packages over to the latest core-tracing as well.

Removing the version collision came out of an offline discussion after these changes were reviewed - since it's a common 
source of pain and hasn't added much benefit (tracer conflicts incompatibility was never a problem) we decided to remove 
that logic and always grab a unique symbol per OT compatibility. 

## Callouts

The packages that are already on core-v2 will _not_ be upgraded at this time - we'll coordinate that with the GA of core-rest-pipeline 1.1.0

…-persistence (Azure#15384)

* [identity] Remove machine-code-dependent codepaths (Azure#15024)

* [identityg Remove machine-code-dependent codepaths

* Linter fixes

* Disable broken perf test

* Added missing import back

* [identity] Add extension registration API and default credential stack

* [identity-native] Introducing identity-native

* [identity] Rework extension API.

* Remove identity native

* Identity-persistence module

* Adding identity-vscode module

* Updated rush configuration

* Moved identity perf back to linking local identity

* Symbolic refactor of extension system

* Renamed MsalCredentialOptions to CacheableCredentialOptions

* Use Symbol.for instead of hacking around SymbolConstructor

* Improved identity-vscode samples

* Use persistence by default if a persistence provider has been registered.

* Improved identity-persistence samples

* Rename to identity-cache-persistence

* Feedback from arch board for mainline identity package

* Rename CredentialPersistenceOptions, format and lint

* Revert sanitization of scopes.

* Regenerated API.md for mainline identity

* Add tests and finalize @azure/identity-cache-persistence

* Record tests for identity-cache-persistence

* Renamed sample files.

* Some changes for testing in identity

* Updated identity-vscode

* Remove async version of useIdentityExtension

* Added a couple of tests for default no-extension behavior

* Fixed tests in recorder

* Removed errant console.log

* Added basic tests of identity-vscode

* Fixed a couple of tests that have started caching correctly

* Added browser shim for extensions/consumer.ts

* Mock keytar using sinon in live/playback environments

* Disable persistence tests on node !== 12

* Addressed feedback in identity-cache-persistence

* Restore perf-test

* Removed sanitizeScopeUrl from recorder

* Update sdk/identity/identity/src/credentials/visualStudioCodeCredential.ts

Co-authored-by: Jeff Fisher <xirzec@xirzec.com>

* Fix gitignores

* Feedback for identity-vscode

* Changelog entry for recorder changes.

* core-http -> core-auth

* setter methods instead of setter props

* Some changes to docs and keywords

* Fixed linter warning

* Switch persistence tests from 12 to 14.

* Make the tests even refuse to import msal-node-extensions on anything other than Node 14

* Reverted changes to recorder

* master -> main

* More master -> main

* [identity] Make the samples extract only part of the token data

Co-authored-by: Jeff Fisher <xirzec@xirzec.com>

…5850)

* Adding support for temporary redirect

* Lint

* Changes to create artifact in package directory

… fixing flaky tests to be more reliable. (Azure#15761)

Making changes to simplify a flaky test (and hopefully make it more reliable).

The main issue with the 'handle interrupted detach' method was that it relied on too many moving parts to work reliably. We could just eternally loop like we'd expect customers to do, but in the end we have a very simple test we're trying to perform - we want to receive, and while we're in the process of draining, cause a detach and have it early exit and reject/resolve immediately rather than waiting for the timeout.

I reworked the test to make that simpler by just removing the unneeded connection.idle() and just calling directly into the onDetached method. Because it happens prior to rhea even seeing that we're draining we should reliably win that race each time. 

There were a couple of other things changed for this PR as well:
- The max time per test was lowered accidentally. Bringing it back what's been used as the standard time in other libraries
- Fixed a spot in receiveMessages() where, if the link had been closed, we'd falsly return an empty array instead of throwing an exception indicating the link closed. This didn't appear to be related to the bug but it's incorrect and can hide bugs so I'd rather just throw the error than eat the condition and return an empty array. It's rare, but when it does happen the empty array response isn't right either - we're probably in the middle of a connection reset/change event.

Fixes Azure#13461

* Update links with master to use main

* Update ci.yml files

Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

* Update pipeline generation tool version

Consume latest changes from pipeline generation tool in Azure/azure-sdk-tools#1708

* Update tool version to include fix for public ci

Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>

Fixes Azure#15880

…ll anymore (Azure#15783)

I’ve got some customers writing to me directly with some confusion regarding getToken returning null. We’ve got some remnants of this type, but at this point, Identity doesn’t return null (except for ClientSecretCredential in the browser, which is generally unusable outside of our tests). This PR is to update these docs and to give a bit of clarity on what errors we’re throwing.

…zure#15897)

…ure#15883)

Now that `@opentelemetry/api` GA'd at [1.0.0](https://www.npmjs.com/package/@opentelemetry/api) we can bump our 
own dependency to `@opentelemetry/api@1.0.0`

Reminder: not _all_ packages are on the latest @opentelemetry/api... those that depend on @azure/core-rest-pipeline 
cannot be upgraded yet.

Fixes Azure#15891

This should allow our pipelines to pick these packages up for publication.

I recently added a few breaking changes to core-tracing which have impacted core-http but forgot to add changelog entries. This commit just addresses the changelog.

…5777)

and re-generate code.

* Don't set userAgentPrefix in convenience layer

* Update version constant prefix

* Use latest @autorest/typescript plugin

* arm-cosmosdb-release

* version update

## What

- Migrate @azure/keyvault-admin to core V2
- Migrate `KeyVaultBackupClient` and `KeyVaultAccessControlClient` to core CAE
- Bump our minimum `@azure/core-lro` version to 1.0.6

## Why

This PR proves out two important things: it demonstrates that core continuous access evaluation works for both container 
registry (already done) and Key Vault (this PR). It also demonstrates the migration path for Core V2 for Key Vault.

The change to core-lro addresses an issue where core-lro was incorrectly depending on core-http (Azure#15880)  That has been fixed on 1.0.6 
and allows package owners to migrate to core-rest-pipeline and remove core-http without seeing build breaks.


Resolves Azure#15522 
Resolves Azure#14306

* Move to @azure/msal-node-extensions 1.0.0-alpha.7

This version unpins the `keytar` dependency, resolving build issues for some developers, and allowing keytar 7.7.0 (which uses NAPI, reducing prebuild complexity).

* Update pnpm-lock

…tifications (Azure#15731)

* Feature: add sender display name within send typing notifications
* update Changelog
* update signaling package
* update swagger file

* Update ubuntu vm image

* Update vmImage names

* Update platform-matric.json

* Update platform-matric.json

NodeJS does not support directly passing typed arrays or ArrayBuffers to `http.ClientRequest` streams. This means we must correctly wrap these types in a `Buffer` for them to be serialized correctly.

* Migration Guide

* Update sdk/tables/data-tables/MigrationGuide.md

Co-authored-by: Christopher Scott <chriscott@hotmail.com>

* Update sdk/tables/data-tables/MigrationGuide.md

Co-authored-by: Christopher Scott <chriscott@hotmail.com>

* Update sdk/tables/data-tables/MigrationGuide.md

Co-authored-by: Christopher Scott <chriscott@hotmail.com>

* Update sdk/tables/data-tables/MigrationGuide.md

Co-authored-by: Christopher Scott <chriscott@hotmail.com>

* Update sdk/tables/data-tables/MigrationGuide.md

Co-authored-by: Christopher Scott <chriscott@hotmail.com>

* Fix typos

* Apply suggestions from code review

Co-authored-by: Matt Ellis <matt.ellis@microsoft.com>

* Address comments

Co-authored-by: Christopher Scott <chriscott@hotmail.com>
Co-authored-by: Matt Ellis <matt.ellis@microsoft.com>

## What

- Update `@azure/core-rest-pipeline` to 1.1.0 from beta
- Update dependencies to the latest version
- Update everyone to the same version of `@azure/core-tracing`

## Why

Now that we used the CAE capabilities added in core-rest-pipeline in both container registry and key vault it's time to GA this version! It also unblocks our efforts to get everyone upgraded to the latest core-tracing (and OTel by extension) versions.

* Support AAD Authentication

* Update changelog

* Update recordings

* fix format

* Update sdk/tables/data-tables/README.md

Co-authored-by: Matt Ellis <matt.ellis@microsoft.com>

* Address comments and add test

* Update release version

* Add Acknowledgments to changelog

* Fix link

* Remove breaking changes section

Co-authored-by: Matt Ellis <matt.ellis@microsoft.com>

…2938)

…rnal cache (Azure#15929)

Today we cache any opened links in the connectionContext. These links should be removed when the link itself is closed but, due to a mismatch in the values, we weren't. 

I've fixed this by just making an abstract method in LinkEntity (the base for all the link types) and just having each link properly remove itself from the cache.

Fixes Azure#15890

* arm-trafficmanager-release

* readme update

* update package.json

* arm-eventgrid-release

* update package.json

* Update sdk/eventgrid/arm-eventgrid/README.md

Co-authored-by: Ramya Rao <ramya.rao.a@outlook.com>

Co-authored-by: Wei Dong <40835867+dw511214992@users.noreply.github.com>
Co-authored-by: Ramya Rao <ramya.rao.a@outlook.com>

…lient-paging (Azure#15831)

* Prototype paging helper function

* Use paginate in farmbeats

* Updates

* Update farmbeats

* Address PR feedback

* Move paging to its own package

* Use REST Error

* Update types output

* update home page

* Explicit return RestError

* Move paging to its own file and update changelog and versions

…5934)

* Updating OpenTelemetry API to 1.0.0

* Updating version in Monitor Query

* lint fix

* Format

* rush update

* Add missing browser mappings

* Update changelog

In order for Tables to connect to Azurite and Storage emulator, the client needs to accept `allowInsecureConnection`. Also when using the emulator connection string shortcut, setting it by default.

* Check for API review status only if release date is set in changelog

* Change property name to ReleaseStatus

Co-authored-by: Praveen Kuttappan <praveen.kuttappan@gmail.com>

## What

- Update core-http to 2.0.0
- Update core-lro to 2.0.0
- Update packages to use latest version

## Why

This will support our last breaking change for core-tracing, and allow everyone to be on the same minimum version. This will also allow us to target ES2017 across the board.

…e#15031)

In this PR we're aligning the samples of Identity with other languages. The samples I'm adding in this PR are:

- Rolling certificates with ClientCertificateCredential ([.Net](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/identity/Azure.Identity/samples/ClientCertificateCredentialSamples.md#rolling-certificates)).
- ClientCertificateCredential with a Key Vault Certificate ([Python](Azure/azure-sdk-for-python#18109)) (decided not to use `@azure/keyvault-certificates` because of the possible issues converting certificates from one format to another in Node).
- Custom credentials ([.Net](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/identity/Azure.Identity/samples/DefiningCustomCredentialTypes.md#defining-custom-credential-types)).
- Using MSAL directly ([.Net](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/identity/Azure.Identity/samples/DefiningCustomCredentialTypes.md#authenticating-with-msal-directly)).
- On Behalf Of Flow ([.Net](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/identity/Azure.Identity/samples/DefiningCustomCredentialTypes.md#authenticating-with-the-on-behalf-of-flow)).

New samples related to the v2-specific features will be added after the Identity package is separated.

Related to Azure#14435

---

I’ve decided to use this opportunity to:

Fix Azure#15324

This PR also implicitly:

Fixes Azure#15573

This greatly improved my first open experience on my laptop. The only tradeoff is `node_modules` folders won't appear in the file tree of VS Code, but I think this is a pretty uncommon place to browse into manually.

Co-authored-by: Praveen Kuttappan <praveen.kuttappan@gmail.com>

* displayed links as  a list rather than a single line

* displayed links as  a list rather than a single line

* appconfiguration\Readme:  displayed links as a list rather than a single line

* attestation\Readme:  displayed links as a list rather than a single line #6449

* Apply suggestions from code review

Co-authored-by: Deyaaeldeen Almahallawi <dealmaha@microsoft.com>

Co-authored-by: Wes Haggard <Wes.Haggard@microsoft.com>

Adds the list test

Closes Azure#13981

Fixes Azure#15796
## Problem

The throttlingRetryPolicy in core-http has the potential to retry for an extended period if the service continues returning "retry after" headers on subsequent calls.

Here's the snippet of code that handles the "retry after" retries:

```typescript
  public async sendRequest(httpRequest: WebResource): Promise<HttpOperationResponse> {
    return this._nextPolicy.sendRequest(httpRequest.clone()).catch((err) => {
        // other code elided....
        return delay(delayInMs).then((_: any) => this.sendRequest(httpRequest.clone()));
```

## Solution
Update delay such that it respects abort signal.
Similar to what I had to do for app-config at Azure#15721

Followed the steps at https://github.com/Azure/azure-sdk-for-js/wiki/Samples-v2-Migration-Guide
/cc @willmtemple 

Note: I moved browserSamples and expressSamples into the generated v5 samples folder since dev-tool doesn't work with those.

to delete tags before delete the image as this is the recommended best
practice for the service.

* [Identity] Test improvements

* temporary node 16 fix

* Since unhandled promise rejections are not supported in Node 16, tickAsync can't be awaited

* fix the test

Co-authored-by: Harsha Nalluru <sanallur@microsoft.com>

## What

- Regenerate from 7.3-preview swagger
- Add `getRandomBytes` method

## Why

- For July we would like to add support for the RNG endpoint in a Managed HSM. While this is a customer ask for Java, we will add this to all languages at the same time.

As part of #7022, we will be moving the version of `@types/node` from 8 to 12
This PR has the changes required to fix the build errors that occurred when trying out this change
- The [Agent](https://nodejs.org/docs/latest-v12.x/api/http.html#http_class_http_agent) class in Node.js 12 has an extra property `maxTotalSockets`. The docs say there is a default value for this, but it it is still marked as a mandatory property in the types. We use our own interface for this class for the purposes of user providing their own custom agent. Am casting it in this PR to the expected type. If anyone has better ideas here, am all ears :)
- `global.URL` is not a thing as per the types for Node.js 12. We needed this to support Node.js 8
- Fixing the types for `port` in the parsed url

The actual move to v12 for `@types/node` will be done in a separate PR

* Use BufferEncoding as encoding is not a string in Node.js 12

* Fix typing issue for fsStat returning unknown

* adds simple background refresh

* Adds setInterval with unref

* cleanup

* wip prenock

* wip

* Removes recorder, fixes timeout in tests

* extract api

* fix lint

* format

* Adds flag

* lint

* Fix parition spelling

* modify endpoint check

* fix tests

* Comment proxy

* adds back copyright

* skip session spec

* Fix session token

* Fix session spec on emulator

* Support track2 management packages

Perf test packages should not be using the eslint plugin

Fixes the below error

```


ESLint couldn't find the plugin "@azure/eslint-plugin-azure-sdk".

(The package "@azure/eslint-plugin-azure-sdk" was not found when loaded as a Node module from the directory "/home/vsts/work/1/s/sdk".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

    npm install @azure/eslint-plugin-azure-sdk@latest --save-dev

The plugin "@azure/eslint-plugin-azure-sdk" was referenced from the config file in "../../../.eslintrc.json".

```

…est-pipeline (Azure#16045)

This PR updates the newly added `@azure-rest/core-client-paging` package to use the same version of `@azure/core-rest-pipeline` that the other packages use.

We recently GA'd (on main, not released yet) version 1.1.0 of `@azure/core-rest-pipeline` and want to keep everyone on the latest version.

Follow up for Azure#16046 to fix the resulting linter errors

…16010)

Update to latest core packages and improve pipeline robustness.

As part of the development of the new pipeline, event grid was hand
ported to use the new pipeline. Now that the code generator targets
the new pipeline, we can start using it to generate the code.

Since EventGrid includes the `/api/events` path segment in the
Endpoint, We need to do a small amount of post processing of the
generated code, to ensure `/api/events` is not appended to the
endpoint (we do this by setting an empty path in the operation spec,
which is as things were before moving over to the generator).

Fixes Azure#15823

…me environments (Azure#15937)

…dential (Azure#15856)

* [Identity] Add support for Bridge to Kubernetes to ManagedIdentityCredential

* one very simple test

* forgot this line

…ers (Azure#15932)

* [Monitor Exporter] Separate tests into internal and public folders

* fix build

* put tests in internal

* prettier

* console log for testing

* testing

* format

* console

* try flush processor

* format

* remove console logs

## What

- Adds warning filter to ignore known rollup warnings that are safe to ignore
- Ignore `this has been rewritten to undefined` in synapse
- Ignore circular dependencies in synapse

## Why

These are both known warnings, are safe to ignore, and add noise to the build output unnecessarily. 

The first is totally safe to ignore:

```
var __spreadArray = (this && this.__spreadArray) || function (to, from) {
```

Is emitted from TypeScript in the OTel ESM and is safe to use.
The second is a known issue in OTel 1.0.0 that is not harmful at runtime.

Finally, we have precedent for doing the exact same thing in other packages like service-bus.

The watchful eyes of @vishnureddy17 found that we still have reference to Node.js 8 in our Contributing Guide!!

This PR fixes that.

Related to #7022

* Update identity to 2.0.0-beta.4 for quantum jobs

* Fix CI Errors

* Fix CI Errors

Based on the Retry-After specification, 503 should also be supported when considering the Retry-After header.

This also aligns with upcoming Identity plans.

…ure#16049)

close Azure#13814

…5853)

This PR enables PKCE on the InteractiveBrowserCredential.

We don’t have tests for this yet. I’ll make sure to test it manually, at least.

Fixes Azure#15168

…ludeVisualization option. (Azure#16058)

* Big update to use the latest stable swagger files for all of the Log Analytics services. Each reference is by git commit ID this time to prevent any accidental drift.

Also, added in the includeRender header (via the `includeVisualization` option).

Fixes Azure#15771

* Fixing codeowners to reflect the proper owners for the package:
@KarishmaGhiya - main owner
@maorleger - backup owner

* Formatting!

…ease. (Azure#16072)

* Convenience Method to create a synonymmap object

* Update sdk/search/search-documents/src/synonymMapHelper.ts

Co-authored-by: Jeff Fisher <xirzec@xirzec.com>

* Fix for PR Comments

Co-authored-by: Jeff Fisher <xirzec@xirzec.com>

* [Identity] InteractiveBrowserCredential LoginHint

* formatting

* Update CHANGELOG.md

* Bring changes from JS docs metadata

* Move business logic inside Update-DocsMsMetadata.ps1

* Update with the latest changes in JS PR

* Update from latest PR feedback

* Add check for empty path to prevent crashes when creating relative paths

Co-authored-by: Daniel Jurek <djurek@microsoft.com>

This PR just updates the release dates for core releases that I plan to release:

- @azure/core-tracing
- @azure/core-http
- @azure/core-rest-pipeline
- @azure/core-client
- @azure/core-lro
- @azure/core-auth

- Switch to using rest instead of cli for querying work items
  as cli is limited to 1000 items only.
- Fix issues with Generated fields not being set.
- Correctly sort older workitems by version isntead of string.

Co-authored-by: Wes Haggard <Wes.Haggard@microsoft.com>

* [event-hubs] add AmqpAnnotatedMessage support

* undo experimental deletion of decode method from service bus

* address feedback

See Azure#16094 for details. This PR just updates core-client to 1.2.1 so I can release it

The release pipeline complains if there are empty sections in the changelog. Removing the empty section to correct this and unblock core-http release.