Closed
Conversation
* Implemented Get/Set KeyValue * Added ReadOnlySequenceContent * Optimized ParseConnectionString * Added return value to ReadAsync
* Moved telemetry to a policy * Improved Tests
* reorganized folders * Added tests for retries
* reorganized folders * Added buffer management tests
* Added more APIs and simplified * Experimenting with streamed upload * renames after the arch review
* Added more APIs and simplified * Experimenting with streamed upload * renames after the arch review * cleanup names and simplify configuration APIs
* Added more APIs and simplified * Experimenting with streamed upload * renames after the arch review * Changes to pipeline * Changed configuration APIs and added ETag
* finished Get mock * small rename
* changes to options * more immutability and ability to set options
* changes to options * more immutability and ability to set options * Removed usages of Url from System.Configuration
* Added custom nuget feeds * hiding strange APIs * removed Sequence<T> from core dll * more cleanup
…ver (Azure#24) * trying to call actual service * got response from live server * Set runs against live server
* 3 live tests * PR feedback
* refactor mock classes * refactor _responseContent
* refactoring + delete * extension method Clone
* moved off pipeline writer for request contnent * removed ContentWriter * cleaneup
* Removed Uri and ServiceMethod from Context.Create * Refactored how authentication headers is computed * small cleanup
Re-enable the version check for the HttpRequestMessage
In situations requiring cross-tenant auth, it is currently not possible to use MSI to fetch an access token directly. In these scenarios, it would be helpful to be able to use a client certificate grant, but with the certificate stored in Key Vault. Currently, this workflow is supported, but only for "development-like" environments (i.e. through the Visual Studio or Azure CLI token flows). This commit makes it possible for a service to use its managed identity to retrieve a Key Vault access token for client certificate grants.
…re work-in-progress introduced for github PRs (Azure#5258)
* Adding first version of Edge gateway sdk and tests * Fixing PR comments - Project property corrections, add assemblyinfo, use generate.ps1 * Fix PR comments - assemblyinfo, assemblyversion, unnecassary properties in proj files * PR comment fixes: Target framework, folder structure * Updated device updates test case * Regenerated client code with generate.ps1 pointing to azure master rest spec * PR Comments: project property fixes, rerun tests
…elay was in milliseconds. (Azure#5268)
* [Datafactory]SDK Change for SapOpenHub and Rest * fix indention
…t results, produce results under default directory
Travis Build didn't correctly report back, but was successful: https://travis-ci.org/Azure/azure-sdk-for-net/builds/496719788?utm_source=github_status&utm_medium=notification
…r minor fixes, bumping package version (Azure#5264)
* Updated Kusto GA version * Fixed comments
Rename Azure.Core to Azure.Base
…ing for release (Azure#5280) * Adding new properties to DataBricks LS and Custom activity and updating the changelog for release * Fixing version - 3.0.1 is not released yet. * Fixing the Release notes
PR Azure#5248 accidently renamed some files to the generated folder instead of Generated which causes case-sensitivity issues.
Update the template version for the next version as well as moved it to be a prerelease to test out some component governance checks.
added 3 commits
February 26, 2019 12:43
acured
pushed a commit
that referenced
this pull request
Mar 26, 2019
* # This is a combination of 5 commits. parent e68ceb4 author Lakshmanan Ramu Meenal <laramume@microsoft.com> 1539635490 -0700 committer Lakshmanan Ramu Meenal <laramume@microsoft.com> 1551313811 -0800 # This is a combination of 2 commits. # This is the 1st commit message: added 2.1 preview SDK for text analytics based on PR commanets changed the number of SDK's to one # This is the commit message #1: fixed test project errors # This is the commit message #2: fixed test project errors # This is the commit message #3: fixed test project errors # This is the commit message #4: fixed the log errors * changed the version name and package notes * # This is a combination of 5 commits. # This is the 1st commit message: added SDK for version 2.1 # This is the commit message #1: resolved build failure # This is the commit message #2: resolved build failure # This is the commit message #3: resolved build failure # This is the commit message #4: resolved build failure * added SDK for version 2.1 * changed version number to 3.0.0 * updated assemblyfileversion
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.
Description
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Testing Guidelines
SDK Generation Guidelines
*.csprojandAssemblyInfo.csfiles have been updated with the new version of the SDK.