Skip to content
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-postgresql] Adding iperf APIs #4977

Closed

Conversation

openapi-sdkautomation[bot]
Copy link

Create to sync Azure/azure-rest-api-specs#14714

Installation Instructions

You can install the package @azure/arm-postgresql of this PR using the following command:

curl -L "https://portal.azure-devex-tools.com/api/sdk-dl-pub?p=Azure/14714/azure-sdk-for-js/@azure_arm-postgresql/azure-arm-postgresql-5.0.0.tgz" -o azure-arm-postgresql-5.0.0.tgz
npm install azure-arm-postgresql-5.0.0.tgz

Direct Download

The generated package can be directly downloaded from here:

@openapi-sdkautomation openapi-sdkautomation bot force-pushed the sdkAuto/14714/@azure_arm-postgresql branch 6 times, most recently from d8b5286 to a9da19e Compare June 16, 2021 12:59
praveenkuttappan and others added 7 commits June 18, 2021 14:27
* 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 <[email protected]>
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
@openapi-sdkautomation openapi-sdkautomation bot force-pushed the sdkAuto/14714/@azure_arm-postgresql branch from a9da19e to a50f3b9 Compare June 21, 2021 02:24
Merge 7a3eeb8530e1935618f79c2927de6e86c92b71b0 into 0c057560083bfdfd50202f0e79cfac8ec054d56a
@openapi-sdkautomation openapi-sdkautomation bot force-pushed the sdkAuto/14714/@azure_arm-postgresql branch from a50f3b9 to fb1ad83 Compare June 21, 2021 03:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants