-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AutoPR @azure/arm-peering] Peering api 2021-06-01 #4970
Commits on Jun 18, 2021
-
Configuration menu - View commit details
-
Copy full SHA for d769b84 - Browse repository at this point
Copy the full SHA d769b84View commit details -
Fix hard-coded master (Azure#15843)
Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>
Configuration menu - View commit details
-
Copy full SHA for 1d0b3dd - Browse repository at this point
Copy the full SHA 1d0b3ddView commit details -
[Communication]: Always use x-ms-date for Hmac (Azure#15807)
* 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>
Configuration menu - View commit details
-
Copy full SHA for ddf4714 - Browse repository at this point
Copy the full SHA ddf4714View commit details -
Configuration menu - View commit details
-
Copy full SHA for c075155 - Browse repository at this point
Copy the full SHA c075155View commit details -
[KeyVault] - Add networkAcls to MHSM ARM template (Azure#15830)
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.
Configuration menu - View commit details
-
Copy full SHA for bdff63d - Browse repository at this point
Copy the full SHA bdff63dView commit details -
[Core] - Move core-tracing to @opentelemetry/api 0.20.0 (Azure#15672)
## 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
Configuration menu - View commit details
-
Copy full SHA for d023204 - Browse repository at this point
Copy the full SHA d023204View commit details
Commits on Jun 21, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 37d1df4 - Browse repository at this point
Copy the full SHA 37d1df4View commit details -
[identity] Adding extensions API, identity-vscode, and identity-cache…
…-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>
Configuration menu - View commit details
-
Copy full SHA for 4471210 - Browse repository at this point
Copy the full SHA 4471210View commit details -
[AzureMonitorExporter] Adding support for temporary redirect (Azure#1…
…5850) * Adding support for temporary redirect * Lint
Configuration menu - View commit details
-
Copy full SHA for 919e856 - Browse repository at this point
Copy the full SHA 919e856View commit details -
Package artifact path (Azure#15512)
* Changes to create artifact in package directory
Configuration menu - View commit details
-
Copy full SHA for f9efdf4 - Browse repository at this point
Copy the full SHA f9efdf4View commit details -
[service-bus] Closing some open areas where we could mask errors, and…
… 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
Configuration menu - View commit details
-
Copy full SHA for d4d2c75 - Browse repository at this point
Copy the full SHA d4d2c75View commit details -
Sync eng/common directory with azure-sdk-tools for PR 1716 (Azure#15876)
* Update links with master to use main * Update ci.yml files Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>
Configuration menu - View commit details
-
Copy full SHA for 5da2922 - Browse repository at this point
Copy the full SHA 5da2922View commit details -
Sync eng/common directory with azure-sdk-tools for PR 1719 (Azure#15885)
* 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>
Configuration menu - View commit details
-
Copy full SHA for 450f924 - Browse repository at this point
Copy the full SHA 450f924View commit details
Commits on Jun 22, 2021
-
Configuration menu - View commit details
-
Copy full SHA for b26a218 - Browse repository at this point
Copy the full SHA b26a218View commit details -
[Identity] Comment improvements. Identity generally doesn't return nu…
…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.
Configuration menu - View commit details
-
Copy full SHA for 53d6089 - Browse repository at this point
Copy the full SHA 53d6089View commit details -
Configuration menu - View commit details
-
Copy full SHA for 8ab9b83 - Browse repository at this point
Copy the full SHA 8ab9b83View commit details -
[core] Update @azure/core-tracing to use @opentelemetry/api@1.0.0 (Az…
…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.
Configuration menu - View commit details
-
Copy full SHA for ac8d65c - Browse repository at this point
Copy the full SHA ac8d65cView commit details -
Configuration menu - View commit details
-
Copy full SHA for a64747c - Browse repository at this point
Copy the full SHA a64747cView commit details -
Configuration menu - View commit details
-
Copy full SHA for bf5cd3e - Browse repository at this point
Copy the full SHA bf5cd3eView commit details -
[identity] Add publication metadata for extension pacakges (Azure#15900)
This should allow our pipelines to pick these packages up for publication.
Configuration menu - View commit details
-
Copy full SHA for 0f4ae0c - Browse repository at this point
Copy the full SHA 0f4ae0cView commit details -
Configuration menu - View commit details
-
Copy full SHA for c7f3a2a - Browse repository at this point
Copy the full SHA c7f3a2aView commit details -
[core] - added changelog entries for recent changes (Azure#15902)
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.
Configuration menu - View commit details
-
Copy full SHA for 0eeb81a - Browse repository at this point
Copy the full SHA 0eeb81aView commit details
Commits on Jun 23, 2021
-
[ContainerRegistry] switch to use official TS code generator (Azure#1…
…5777) and re-generate code. * Don't set userAgentPrefix in convenience layer * Update version constant prefix * Use latest @autorest/typescript plugin
Configuration menu - View commit details
-
Copy full SHA for 556da80 - Browse repository at this point
Copy the full SHA 556da80View commit details -
Arm cosmosdb release (Azure#15789)
* arm-cosmosdb-release * version update
Configuration menu - View commit details
-
Copy full SHA for 63bc1fd - Browse repository at this point
Copy the full SHA 63bc1fdView commit details -
[KeyVault] - Migrate Key Vault Admin package to Core V2 (Azure#15881)
## 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
Configuration menu - View commit details
-
Copy full SHA for b499bfb - Browse repository at this point
Copy the full SHA b499bfbView commit details -
Configuration menu - View commit details
-
Copy full SHA for 56c7442 - Browse repository at this point
Copy the full SHA 56c7442View commit details -
Move to @azure/msal-node-extensions 1.0.0-alpha.7 (Azure#15908)
* 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
Configuration menu - View commit details
-
Copy full SHA for 5728f70 - Browse repository at this point
Copy the full SHA 5728f70View commit details -
[Communication]Feature: add sender display name within send typing no…
…tifications (Azure#15731) * Feature: add sender display name within send typing notifications * update Changelog * update signaling package * update swagger file
Configuration menu - View commit details
-
Copy full SHA for 023db76 - Browse repository at this point
Copy the full SHA 023db76View commit details -
Update ubuntu VM image (Azure#15706)
* Update ubuntu vm image * Update vmImage names * Update platform-matric.json * Update platform-matric.json
Configuration menu - View commit details
-
Copy full SHA for a1f909d - Browse repository at this point
Copy the full SHA a1f909dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6c59958 - Browse repository at this point
Copy the full SHA 6c59958View commit details -
Fix handling of typed arrays in request bodies (Azure#15904)
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.
Configuration menu - View commit details
-
Copy full SHA for 137c671 - Browse repository at this point
Copy the full SHA 137c671View commit details -
[Tables] Migration Guide (Azure#15857)
* 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>
Configuration menu - View commit details
-
Copy full SHA for 65a90e5 - Browse repository at this point
Copy the full SHA 65a90e5View commit details -
[core] - GA core-rest-pipeline 1.1.0 (Azure#15923)
## 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.
Configuration menu - View commit details
-
Copy full SHA for 99d53b6 - Browse repository at this point
Copy the full SHA 99d53b6View commit details -
[Tables] Support AAD Authentication (Azure#15852)
* 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>
Configuration menu - View commit details
-
Copy full SHA for 2d2c656 - Browse repository at this point
Copy the full SHA 2d2c656View commit details
Commits on Jun 24, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 46078e3 - Browse repository at this point
Copy the full SHA 46078e3View commit details -
[service-bus] Fixing issue where links were not removed from our inte…
…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
Configuration menu - View commit details
-
Copy full SHA for 58b1993 - Browse repository at this point
Copy the full SHA 58b1993View commit details -
arm-trafficmanager-release (Azure#15695)
* arm-trafficmanager-release * readme update * update package.json
Configuration menu - View commit details
-
Copy full SHA for bb833fc - Browse repository at this point
Copy the full SHA bb833fcView commit details -
arm-eventgrid-release (Azure#15791)
* 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>
Configuration menu - View commit details
-
Copy full SHA for b77a2a4 - Browse repository at this point
Copy the full SHA b77a2a4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 93d102b - Browse repository at this point
Copy the full SHA 93d102bView commit details -
[Core Rest] Add pagination helper for rest clients @azure-rest/core-c…
…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
Configuration menu - View commit details
-
Copy full SHA for 23bb270 - Browse repository at this point
Copy the full SHA 23bb270View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5f71ecd - Browse repository at this point
Copy the full SHA 5f71ecdView commit details -
[Azure Monitor Exporter] Updating OpenTelemetry API to 1.0.0 (Azure#1…
…5934) * Updating OpenTelemetry API to 1.0.0 * Updating version in Monitor Query * lint fix * Format * rush update
Configuration menu - View commit details
-
Copy full SHA for 24302c8 - Browse repository at this point
Copy the full SHA 24302c8View commit details -
[Tables] Add missing browser mappings (Azure#15944)
* Add missing browser mappings * Update changelog
Configuration menu - View commit details
-
Copy full SHA for 1f6b914 - Browse repository at this point
Copy the full SHA 1f6b914View commit details -
Configuration menu - View commit details
-
Copy full SHA for d3c3f90 - Browse repository at this point
Copy the full SHA d3c3f90View commit details -
[Tables] Expose client option allowInsecureConnection (Azure#15938)
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.
Configuration menu - View commit details
-
Copy full SHA for cbaa410 - Browse repository at this point
Copy the full SHA cbaa410View commit details -
Sync eng/common directory with azure-sdk-tools for PR 1729 (Azure#15927)
* 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>
Configuration menu - View commit details
-
Copy full SHA for 3c21c59 - Browse repository at this point
Copy the full SHA 3c21c59View commit details -
[core] - Bump core-http to 2.0.0 and core-lro to 2.0.0 (Azure#15925)
## 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.
Configuration menu - View commit details
-
Copy full SHA for 5903b7c - Browse repository at this point
Copy the full SHA 5903b7cView commit details -
[Identity] Samples aligned with other languages (v1 compatible) (Azur…
…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
Configuration menu - View commit details
-
Copy full SHA for 9b9a9d1 - Browse repository at this point
Copy the full SHA 9b9a9d1View commit details -
Tweak workspace settings for VS Code startup perf (Azure#15956)
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.
Configuration menu - View commit details
-
Copy full SHA for aa8db15 - Browse repository at this point
Copy the full SHA aa8db15View commit details -
Add Ubuntu 20 to local dns bypass template (Azure#15951)
Co-authored-by: Praveen Kuttappan <praveen.kuttappan@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 4ff4cef - Browse repository at this point
Copy the full SHA 4ff4cefView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8afa5cf - Browse repository at this point
Copy the full SHA 8afa5cfView commit details -
Attestation\README listing links as a list (Azure#15914)
* 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>
Configuration menu - View commit details
-
Copy full SHA for d9066a2 - Browse repository at this point
Copy the full SHA d9066a2View commit details
Commits on Jun 25, 2021
-
Update references from master to main (Azure#15977)
Co-authored-by: Wes Haggard <Wes.Haggard@microsoft.com>
Configuration menu - View commit details
-
Copy full SHA for c6b82ee - Browse repository at this point
Copy the full SHA c6b82eeView commit details -
[App config] Perf tests (Azure#15763)
Adds the list test Closes Azure#13981
Configuration menu - View commit details
-
Copy full SHA for 35739ab - Browse repository at this point
Copy the full SHA 35739abView commit details -
[core-http] Throttling retry policy fix in core-http (Azure#15832)
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
Configuration menu - View commit details
-
Copy full SHA for bb9896d - Browse repository at this point
Copy the full SHA bb9896dView commit details -
Configuration menu - View commit details
-
Copy full SHA for d76e6f6 - Browse repository at this point
Copy the full SHA d76e6f6View commit details -
[event-hubs] migrate samples to v2 (Azure#15053)
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.
Configuration menu - View commit details
-
Copy full SHA for 2f90a87 - Browse repository at this point
Copy the full SHA 2f90a87View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9440254 - Browse repository at this point
Copy the full SHA 9440254View commit details -
[ContainerRegistry] Update delete image sample (Azure#16002)
to delete tags before delete the image as this is the recommended best practice for the service.
Configuration menu - View commit details
-
Copy full SHA for ca61eb9 - Browse repository at this point
Copy the full SHA ca61eb9View commit details -
[Identity] Test improvements (Azure#15999)
* [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>
Configuration menu - View commit details
-
Copy full SHA for 4ccc8d9 - Browse repository at this point
Copy the full SHA 4ccc8d9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 63b6236 - Browse repository at this point
Copy the full SHA 63b6236View commit details -
[KeyVault] - Add support for getRandomBytes operation (Azure#15955)
## 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.
Configuration menu - View commit details
-
Copy full SHA for f3a8efe - Browse repository at this point
Copy the full SHA f3a8efeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 4784937 - Browse repository at this point
Copy the full SHA 4784937View commit details -
Prepare to move to @types/node v12 (Azure#16012)
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
Configuration menu - View commit details
-
Copy full SHA for 82085ff - Browse repository at this point
Copy the full SHA 82085ffView commit details -
Configuration menu - View commit details
-
Copy full SHA for b729674 - Browse repository at this point
Copy the full SHA b729674View commit details
Commits on Jun 26, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 1a5d100 - Browse repository at this point
Copy the full SHA 1a5d100View commit details -
Configuration menu - View commit details
-
Copy full SHA for b8da289 - Browse repository at this point
Copy the full SHA b8da289View commit details
Commits on Jun 28, 2021
-
Prepare Storage packages to move to @types/node v12 (Azure#16020)
* Use BufferEncoding as encoding is not a string in Node.js 12 * Fix typing issue for fsStat returning unknown
Configuration menu - View commit details
-
Copy full SHA for ff90eba - Browse repository at this point
Copy the full SHA ff90ebaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 23de687 - Browse repository at this point
Copy the full SHA 23de687View commit details -
[Cosmos] Simple endpoint refresh interval (Azure#15781)
* 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
Configuration menu - View commit details
-
Copy full SHA for d3647f8 - Browse repository at this point
Copy the full SHA d3647f8View commit details -
Support track2 management packages (Azure#15975)
* Support track2 management packages
Configuration menu - View commit details
-
Copy full SHA for 00ea067 - Browse repository at this point
Copy the full SHA 00ea067View commit details -
Fix lint script for app config perf test (Azure#16046)
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". ```
Configuration menu - View commit details
-
Copy full SHA for facf5c1 - Browse repository at this point
Copy the full SHA facf5c1View commit details -
CodeGen from PR 14703 in Azure/azure-rest-api-specs
Merge 1f145a5e9d39d6670f94ccfc5af26d4339029459 into e793a8cd4b8d8b6b21cc7a26e364ad56d23a4861
SDKAuto committedJun 28, 2021 Configuration menu - View commit details
-
Copy full SHA for 4eeb41f - Browse repository at this point
Copy the full SHA 4eeb41fView commit details