-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Merge from master, and tests for 2021-03-01, and generated code for 2021-03-01 #21333
Merged
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
Based on feedback with the C# architects, we've made some changes to the class factoring here and renamed some methods. The goal was to try to reduce the number of clients we have and clean up some naming issues.
…20797) * Remove subscription id since it is not needed in test-resources.json
… methods (#20786) * renames * catch 404s * string format overloads for Query methods
* CI only
* Remove lock token remarks from settlement method docs * Remove references to LinkCloseMode.
* Topic filter sample * Update README.md * Update README.md * Fix link * PR FB * PR fb
…le services (#19203) * only identity change * resolve error * change hardcode string * change to supportedclouds * remove hardcode * remove change * remove hardcode * change to have the default in a common place * Remove the StartsWith * Remove the TestEnvironment.KeyvaultScope * Remove change * add hardcode string * Delete TestEnvVar file. * Remove hardcoded value of KeyvaultScope, add a initial value for it * Remove invalid changes. Co-authored-by: Wenjie Yu (Wicresoft North America Ltd) <v-wenjyu@microsoft.com> Co-authored-by: Tong Xu (Wicresoft North America Ltd) <v-xuto@microsoft.com>
…ers. (#20833) A recent bump to autorest core broke the autobump script, as two existing sdks refused validation. This PR does the bump, writes transforms for the short term, and then regenerates code. These issues are filed to update the swagger and remove the transform. Azure/azure-sdk#2803 handles this for ACR. Azure/azure-sdk#2805 handles this for Azure.AI.MetricsAdvisor .
…icationPolicy (#20670) * expose BearerTokenChallengeAuthenticationPolicy through BearerTokenAuthenticationPolicy
Co-authored-by: Jesse Squire <jesse.squire@gmail.com>
…operty validation (#20862)
* Updated TPM attestation APIs at the request of the TPM attestation team
…20733) The focus of these changes is to o refactor partition initialization into the background task responsible for processing the partition. Because failures would still be surfaced through the error handler mechanism and the flow for recovering would follow the existing partition processing failure, there should be no change to usage patterns nor visible behavioral changes.
* redesing for TextAppearance * changelog
* updated readme and changelog for may release * user version number 1.0.1 for the hot bug fixes
* Update samples to use #if SNIPPET * Fix docs
The focus of these changes is to introduce validation for configuration and permissions errors that would prevent an event processor from being able to recover without intervention. For example, an incorrect connection string or the inability to write to the storage container would be detected. Validation is performed in an unobtrusive way intended to avoid delaying the processor's ability to begin taking ownership of partitions while ensuring that host applications are made aware of fatal problems within the scope of the Start call, rather than having to rely on the error handler. Also included in these changes is retiring of the ListCheckpointsAsync implementation, which was deprecated in favor of GetCheckpointAsync previously.
* cache work * WIP * WIP * first e2e impl * renames and comment tidy for clarity * update to expiry and force refresh condition * tests pass * removing printfs * re-record tests to accomodate cached token * fix live tests to run in CI * work in progress * index on acr-cache-refresh-token: f906f3b work in progress * update tests * get expiry time from jwt * pr fb * make work with new base class PR * sanitize all but the expiration time in refresh_token in the recorded test logs * record tokens that don't expire + extra comments * pr fb
* Apply 2021-02-01 updates * Rename backup tests folder since it was ignored Co-authored-by: Audunn Baldvinsson <audunn.baldvinsson@netapp.com>
* Move docindex.yml from steps -> jobs * Add docindex.yml Co-authored-by: Daniel Jurek <djurek@microsoft.com>
The focus of these changes is to add the overview content as a README in the root of the SDK directory, which will be used by the MS Docs site to as the landing page: [Azure Event Grid libraries for .NET - Azure for .NET Developers](https://docs.microsoft.com/dotnet/api/overview/azure/eventgrid)
This is the work from #21232 applied to farm beats, the changes went in concurrently and didn't see one another.
* API updates to support function level autocomplete. * Fix test * Fix docs
Co-authored-by: Minnie Liu <peiliu@microsoft.com>
* initial addition of perf tests * further updates to perf tests * use separate scenarios * doc bug * pr fb * pr fb
* remove delays before deletes * small renames and change test mode
azure-sdk
pushed a commit
to azure-sdk/azure-sdk-for-net
that referenced
this pull request
Feb 9, 2023
Release cosmos db microsoft.document db 2022 11 15 (Azure#21333) * Adds base for updating Microsoft.DocumentDB from version stable/2022-08-15 to version 2022-11-15 * Updates readme * Updates API version in new specs and examples * Added specs for tables and gremlin * Adds support for creating ClientEncryptionKeys and create containers with ClientEncryptionPolicy * initial commit of new repair apis. * update api-version. * fix reference links within swagger. * update for tls version * fix validation errors. * fix: use v2 parameter type instead of v1. * Changed property name from minimum to minimal * Fixed property name to minimalTlsVersion on CosmosDBDatabaseAccountCreateMax.json * Fix spell check. * Fix prettier errors. * Adds Location and Azure-AsyncOperation header to examples. * Fix API version in example. * Add missing property to example. * Add base64 encoded byte array to examples. * Run Prettier * Fix bytes format on example. * Add missing headers in examples * Revert "fix: use v2 parameter type instead of v1." This reverts commit e96cda34470825e3fd5089e68a40462bc811fc7a. * Revert "fix validation errors." This reverts commit 5d784f713b34b07f481b2f90ff90f31e681fa049. * Revert "fix reference links within swagger." This reverts commit e4dde8e89dcea846f3f50058eb9fae653fe6554f. * Revert "update api-version." This reverts commit 6b67323728fc9106341b000207db29c508b33442. * Revert "initial commit of new repair apis." This reverts commit de954a9f16aa53f4f20600ec2aa10d97d7689d5f. * Fix LintDiff error * Fix bytes format errors * Add location and azure-AsyncOperation headers to 202s. * Add 202 headers to services.json * Run prettier. * Fix incorrect paths. * Remove x-ms-identifier. * Revert "Fix incorrect paths." This reverts commit a6992102873315dd4e66692168f4a0f96c5c3f17. * Whitespace change * Fixed version in restorable.json * Fix Lint error * Added id, name and type parameters to gremlin/table apis * Change additional properties to allow for any type --------- Co-authored-by: Santosh Kulkarni <66682828+kr-santosh@users.noreply.github.com> Co-authored-by: Vivek Sundararajan <visunda@microsoft.com> Co-authored-by: Vivek Sundararajan <32766101+vivek-microsoft@users.noreply.github.com> Co-authored-by: Daniela Vargas <danvargas@microsoft.com> Co-authored-by: ekuhlmann23 <48370687+ekuhlmann23@users.noreply.github.com> Co-authored-by: Erik Kühlmann Salazar <erikku@microsoft.com>
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.
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
Draft
mode if it is:General Guidelines and Best Practices
Testing Guidelines
SDK Generation Guidelines
*.csproj
andAssemblyInfo.cs
files have been updated with the new version of the SDK. Please double check nuget.org current release version.Additional management plane SDK specific contribution checklist:
Note: Only applies to
Microsoft.Azure.Management.[RP]
orAzure.ResourceManager.[RP]
Management plane SDK Troubleshooting
If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add
new service
label and/or contact assigned reviewer.If the check fails at the
Verify Code Generation
step, please ensure:generate.ps1/cmd
to generate this PR instead of callingautorest
directly.Please pay attention to the @microsoft.csharp version output after running
generate.ps1
. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.Note: We have recently updated the PSH module called by
generate.ps1
to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.