[AutoPR @azure/arm-network] Remove read-only flag of ExpressRoute Gateway connections#6756
Draft
openapi-sdkautomation[bot] wants to merge 2101 commits intofeature/v4from
Draft
[AutoPR @azure/arm-network] Remove read-only flag of ExpressRoute Gateway connections#6756openapi-sdkautomation[bot] wants to merge 2101 commits intofeature/v4from
openapi-sdkautomation[bot] wants to merge 2101 commits intofeature/v4from
Conversation
25 tasks
* Post release automated changes for azure-arm-privatedns * Updated change log for new version Co-authored-by: Praveen Kuttappan <praveen.kuttappan@gmail.com>
* cleanup tests * First set of tests * Table client tests * Table Service * Node Tests * Browser Tests * Fix lint * Update recordings * Fix lint * go after a new version of the test-proxy that dumps the testmismatch * newer proxy version with additional logging. need to pr back this into sdk/tools * return test-proxy to align with main. there are conflicts that are not present in the investigation branch * Update recorded client * Update proxy tool build * fix format * Revert proxy tool version * Ignore headers * Fix format * Use HeaderlessMatcher * Fix format * Fix tests * Remove un needed config Co-authored-by: scbedd <45376673+scbedd@users.noreply.github.com>
* Change credscan to use v3 and enable to scan entire repo * Check string emtpy * add quotes around parameters Co-authored-by: sima-zhu <sizhu@microsoft.com>
Post release automated changes for azure-storage-blob
…ser assigned identity (Azure#20226)
…zure#20344) ### Packages impacted by this PR @azure/eventhubs-checkpointstore-blob ### Issues associated with this PR Partially addresses Azure#13667 ### Describe the problem that is addressed by this PR Because: - BlobCheckpointStore's constructor takes a class (ContainerClient) as an argument - That class is defined in @azure/storage-blob - ContainerClient contains private members You cannot pass what would otherwise be a compatible ContainerClient instance to BlobCheckpointStore unless it is successfully deduped by NPM, even across minor versions. This causes compatibility issues for anyone who upgrades storage-blob. ### 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? I tried to get clever with mapped types, but ran into a few situations (see PR for more information)
Post release automated changes for azure-monitor-query
* Make test more reliable * Migrate Purview scanning * Fix format * remove log
* [ServiceBus] add delay between infinite retry cycles Errors that are not retryable will be re-thrown out of the normal retry() call. However, we don't have any delay before restarting the retry cycle. This PR adds a delay before continuing the infinite retry cycles. * Add a test and update changelog also fixed the issue where we don't use `maxRetryDelayInMs` in Fixed retry mode. * Address CR feedback * Update sdk/servicebus/service-bus/CHANGELOG.md Co-authored-by: Ramya Rao <ramya.rao.a@outlook.com> * Revert max delay limit in Fixed retry mode as the setting only applies to Exponential retry mode. Co-authored-by: Ramya Rao <ramya.rao.a@outlook.com>
Post release automated changes for azure-web-pubsub-express
) This PR migrate purview administration to use new recorder and discard any use of the old one. It also updates the recordings. For more information check out [this migration guide](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/test-utils/recorder/MIGRATION.md).
This PR migrate purview catalog to use new recorder and discard any use of the old one. It also updates the recordings. For more information check out [this migration guide](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/test-utils/recorder/MIGRATION.md).
* Update migration guide * Spelling
This migrate monitor query to use new recorder and discard any use of the old one. It also updates the recordings. For more information check out [this migration guide](https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/test-utils/recorder/MIGRATION.md).
* Refine behavior of BlobClient.Exists to return true when server returns error message of 'BlobUsesCustomerSpecifiedEncryption'. * Resolve comments
* iothub-track2 * update
* compute-track2 * update
* storage-relesae * update * update
) ### Packages impacted by this PR @azure/event-hubs @azure/test-utils ### Issues associated with this PR Azure#20213 ### Describe the problem that is addressed by this PR Now that @azure/core-tracing@preview.14 is out, and hopefully the last version before GA, we need to upgrade a few packages in order to dogfood both the upgrade experience and the usage of these packages with the new [instrumentation package](https://www.npmjs.com/package/@azure/opentelemetry-instrumentation-azure-sdk). My goal was to upgrade one AMQP package and a few HTTP packages in addition to core-rest-pipeline to collect feedback. Upgrading EventHubs now allows us to start using the new APIs in a client package. ### 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? Haven't decided if this should be merged _or_ if we should just publish to NPM under a custom tag in order to allow customers to dogfood. I know there's an internal IoT Hub engineer that is interested in helping out so we just need something for them to try. Right now though I am leaning towards merging this in. I also decided to dump all the `parentSpan` legacy stuff - there really isn't a need to maintain tracing backwards compat with an option that has not been used in over 6 months.
Spell check scanning of packages listed above detected spelling errors in their public API surface. Many of those errors are false positives, which have been added to the `.vscode/cspell.json` file in order to ignore them. However, since all of those packages are already in GA, we cannot make changes to fix the actual spelling errors. For this reason, all of them have been listed in the file to be ignored as well.
) The value provided to EVENTHUB_CONNECTION_STRING in the live test pipeline doesn't contain the event hub name so it's failing with error: TypeError: Either provide "eventHubName" or the "connectionString": "***", must contain "EntityPath=<your-event-hub-name>". This PR passes event hub name too to the client constructor in the same way as some other tests do.
* Add new version of NetworkTraversal, 2022-03-01-preview, with new parameter TTL * Add missing await in README * Update format * Add review API * Add correct version in Changelog * Add options bag for parameters when calling GetRelayConfiguration * Fix format * Update release date * Add missing entry in sms Changelog to fix build errors * Update PR addressing comments * Fix comment * Update PR
* renames * changelog * feedback * Update sdk/formrecognizer/ai-form-recognizer/CHANGELOG.md
* [AzureStack][Mgmt]hybrid-profile-2020-09-01-for-monitor * update
### Packages impacted by this PR @azure/schema-registry-avro ### Issues associated with this PR Fixes Azure#20779 ### Describe the problem that is addressed by this PR ### 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? N/A ### Are there test cases added in this PR? _(If not, why?)_ Yes ### Provide a list of related PRs _(if any)_ N/A ### 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)
* Post release automated changes for azure-storage-blob * Post release automated changes for azure-storage-file-share * Post release automated changes for azure-storage-file-datalake * Post release automated changes for azure-storage-queue
) We claim that we can take `any` type of property values for properties to be modified but it's `applicationProperties` part of a Service Bus message that is modified. That property has a type of `number | boolean | string | Date | null` and is what the service supports. This PR corrects the types for these options to align with `applicationProperties`. Even though it shows as a breaking change, other unsupported types (e.g., an object literal) would cause service errors so they never worked.
Post release automated changes for azure-communication-phone-numbers
### Issues associated with this PR Resolves Azure#19234 ### Describe the problem that is addressed by this PR Upgrades puppeteer to the latest version ### 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? I looked through the changelog for puppeteer and did not see any major changes between 10 and 13 that should impact us
…re#20781) * throttlingRetryPolicy should honor abort signal * puppeteer for browser tests * changelog * Update sdk/core/core-rest-pipeline/CHANGELOG.md * update jsdoc * changelog * assert.isRejected * lint:fix * lock file
Post release automated changes for azure-event-hubs
* appservice-azure-stack * fix-appservice api-extractor Co-authored-by: qiaozha <qiaozha@microsoft.com>
…zure#20830) to workaround an issue in `nyc` v15
Post release automated changes for azure-synapse-artifacts
* Read the ms.service value from csv metadata * Update eng/common/scripts/Update-DocsMsMetadata.ps1 Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com> * Update eng/common/scripts/Update-DocsMsMetadata.ps1 Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com> * Update Update-DocsMsMetadata.ps1 Co-authored-by: sima-zhu <sizhu@microsoft.com> Co-authored-by: Sima Zhu <48036328+sima-zhu@users.noreply.github.com> Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
### Packages impacted by this PR @azure/core-tracing ### Describe the problem that is addressed by this PR It's happening friends! We are GAing core-tracing ### Are there test cases added in this PR? _(If not, why?)_ N/A - just a version change
…s" headers with the throttling policy (Azure#20817) * expand throttlingRetryStrategy with "retry-after-ms", "x-ms-retry-after-ms" headers * Expand test suite with "retry-after-ms" and "x-ms-retry-after-ms" * changelog * Update sdk/core/core-rest-pipeline/src/retryStrategies/throttlingRetryStrategy.ts * no new variable * no internal tag * refactor * new lines for readability * more refactor * Update sdk/core/core-rest-pipeline/src/retryStrategies/throttlingRetryStrategy.ts * part of the feedback * lint * Update sdk/core/core-rest-pipeline/src/retryStrategies/throttlingRetryStrategy.ts Co-authored-by: Jeff Fisher <xirzec@xirzec.com> * format Co-authored-by: Jeff Fisher <xirzec@xirzec.com>
* redis-release * update
* appplatform-release * update * update
…0842) Post release automated changes for azure-arm-appconfiguration
Merge ae7589d5a925843622b7bdba6bcdc6f46f935000 into 2e83e74be70ff1a7735e0398b865c88336dc56b6
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/16905/@azure_arm-network
branch
from
7a0df32 to
259e52c
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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#16905
Installation Instructions
You can install the package
@azure/arm-networkof this PR using the following command:curl -L "https://portal.azure-devex-tools.com/api/sdk-dl-pub?p=Azure/16905/azure-sdk-for-js/@azure_arm-network/azure-arm-network-25.4.0.tgz" -o azure-arm-network-25.4.0.tgz npm install azure-arm-network-25.4.0.tgzDirect Download
The generated package can be directly downloaded from here: