Adding .Net SDK for Microsoft.IntegrationSpaces RP #39653
Closed
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
DevArjun23
changed the title
|
/azp run prepare-pipelines |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
FYI. I filed a bug regarding the |
archerzz
reviewed
Nov 9, 2023
There was a problem hiding this comment.
@DevArjun23 If you merge the main branch, the errors in pipeline regarding Options suffix should be gone. But you still need to handle the remaining issues.
* init * init * addressing comments for README & CHANGELOG
* Add unit test * Update copy data task test * Update bug * Add JsonPathSanitizers * Add DataFactoryElement Tests * Delete DataFactoryElementTests * Fix get sessionrecording.generateassetname * fix not use property --------- Co-authored-by: Bo Wang (Shanghai Wicresoft Co Ltd) <[email protected]>
…wareSecurityModules (Azure#39590)
* initial work * tests and fixes * fix csproj * fixes * csproj
* Parse any json into BinaryData not just objects This is needed to handle SetVariable activity inside ADF, because user can set `0` which should be parsed as number, or `"someString"` or Expression... * Added unit tests
…m to json (Azure#39565) Co-authored-by: Scott Beddall (from Dev Box) <[email protected]>
The focus of these changes is to fix an error in the doc comments which describe behavior of how an event processor forms batches inaccurately.
* SDK Review changes * Update changelog * Add test records * Update sdk/communication/Azure.Communication.JobRouter/CHANGELOG.md Co-authored-by: Rajarshi Sarkar <[email protected]> --------- Co-authored-by: Rajarshi Sarkar <[email protected]>
…es (Azure#39602) * Add auto-generated classes for live metrics swagger. * fix readme and changelog location * Fix CI yaml
* regenerate new code * Regenerate SDK code, remove creditial operation * fix ci, remove code owner change * update * fix changelog error * Revert "fix changelog error" This reverts commit 1146d93. --------- Co-authored-by: pshao25 <[email protected]>
* update 2023-09-01 autorest * mitigate configuration * generating API * Revert "generating API" This reverts commit 687b35c. * generating .NET SDK * mitigate breaking changes * export API * update * adding unit tests * reverting tag * revert change * fix error * fix discoverytests * address comments * Revert "address comments" This reverts commit 2d41b6b. * update tag in assets * Revert "Revert "address comments"" This reverts commit 1453a21. * rename models * fix GT tests * remove recording mode * adding test instructions * update Name,Type and Step * updating changelog * fix release date * fix build errors * update version * fix changelog --------- Co-authored-by: Wei Hu <[email protected]>
Co-authored-by: ArcturusZhang <[email protected]>
* Fix mocking of session processor * remove
* WIP * WIP * WIP * WIP * Enabled directory creation during enumeration; Tests; Some download directory tests don't work * Export API * Cleanup * Cleanup and removing unnecessary comments * Cleanup * Changed LocalDirectory Create to no op * Remove unnecessary tests
fix small typo
…#39680) * Collect AKS attach rate numerator * Remove kubernetes host check * pr feedback
…<float> to ReadOnlyMemory<float> (Azure#39679)
* AOAI: rename and move 'deploymentOrModelName' * very small fix to comments * PR feedback: constructor consistency pass + changelog * more PR feedback: exception consistency across new constructors * post-merge resolution: new snippet sample * post-merge resolution: include README reflection of snippet update * PR feedback: OpenAIClient exceptions docs pass for Options use
update samples to use latest code
* fix(sdk): excessive entries in changelog * fix incorrect version in csproj * remove empty sections
* Initialize HybridNetwork SDK VS solution * Run Update-Mgmt-CI script * Update autorest.md to use local spec checkout * Generate SDK code * Set value for default API version of Operation resource * add some initial UTs * Regenerate SDK against latest API changes * Update assets.json * Complete UTs * Use readme.md from public repo PR and regenerate code * fix broken UTs and add sanitizer to remove acrToken from recordings * Add constants for file names and other repetative strings * update assets.json with tag * try again * remove formatting when we stringify all json * use new recordings * fix ci.mgmt.yml for hdinsights * fix types for IDs and rename suggested models and props * update autorest.md to point at readme.md in main branch * generate API file * mark-ups * rename models with Options suffix
* Fix serialization * Fix serialization2 * change
Co-authored-by: ArcturusZhang <[email protected]> Co-authored-by: Azure SDK Bot <[email protected]> Co-authored-by: azure-sdk <[email protected]>
…ure#38017) * refactor how EnvironmentVariables are read * add logging * move EnvVar to Platform directory * fix merge conflict (EventSource) * add missing using * fix eventsource id
…ions + chat completions) (Azure#39347) * DRAFT: unvetted proposal for flattened streaming * add ported functions test * remaining tests ported * completions for consistency * comments, tests, and other cleanup * one orphaned test comment cleanup * xml comment fix * test assets, making it real * test assets pt. 2 (re-record functions) * revised pattern using new StreamingResponse<T> * use delegate resolver for stronger response/enum connection * add a snippet for streaming functions * also add a snippet for streaming with multiple choices * speculative CHANGELOG update * basic, standalone test coverage for StreamingResponse<T> * feedback: keep StreamingResponse<T> in Azure.AI.OpenAI * address missing 'using' on JsonDocument * tie up broken link from changelog * Post-merge: export-api and update-snippets
…#39712) * refactor * add comment
* [Event Hubs] Error handling for disabled entities The focus of these changes is to add dedicated handling when an Event Hub resource has been set to "disabled" status. This is now treated as a terminal error with a "ResourceNotFound" status, as it requires manual intervention. Previously, this would result in a general communication error that was transient and triggered implicit retries.
* scaffolding * fix merge conflict * update comment * fix subdirectory
…39645) * WIP * WIP * Added download directory tests for Share Directories
* sdk 2023-06-01-preview * update autorest.md * fix * fix * fix use 2021-12-01 and 2023-06-01 for operationResult * fix build errors * Add BackupAndExport wiht OperationResult test case covering swagger 2023-06-01-preview changes * use 2023-06-01-preview * Revert "Mysql/2023 06 01" * update * fix * fix * fix * use MySqlFlexibleServerSku * fix * fix * fix * fix * fix * update * fix * fix * fix changelog --------- Co-authored-by: Wei Hu <[email protected]> Co-authored-by: Sumit Kumar <[email protected]>
DevArjun23
force-pushed
the
archidda/AISNetSdk
branch
from
504fc72 to
d849700
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.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.