[AutoPR @azure/arm-batch] Azure Batch updated to 2021-06-01.14 #5107
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![openapi-sdkautomation[bot]](https://avatars.githubusercontent.com/in/10463?s=60&v=4){kind=small}
26 tasks
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14830/@azure_arm-batch
branch
3 times, most recently
from
72f4ba6 to
99a04b1
Compare
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>
…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.
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14830/@azure_arm-batch
branch
3 times, most recently
from
5c8eaf9 to
93a01fe
Compare
…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.
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
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14830/@azure_arm-batch
branch
2 times, most recently
from
c9d71f1 to
6892db4
Compare
…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>
…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
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14830/@azure_arm-batch
branch
from
6892db4 to
87f3a9f
Compare
Merge d98744647dd59d2a657b878285b5b4b6e45be3dd into c2e43f82e91ff7ad691381df56c535164b354cba
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14830/@azure_arm-batch
branch
from
87f3a9f to
0b78ccf
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create to sync Azure/azure-rest-api-specs#14830
Installation Instructions
You can install the package
@azure/arm-batchof this PR using the following command:curl -L "https://portal.azure-devex-tools.com/api/sdk-dl-pub?p=Azure/14830/azure-sdk-for-js/@azure_arm-batch/azure-arm-batch-5.0.0.tgz" -o azure-arm-batch-5.0.0.tgz npm install azure-arm-batch-5.0.0.tgzDirect Download
The generated package can be directly downloaded from here: