[AutoPR Microsoft.Azure.Management.Peering] Peering api 2021-06-01 #4355
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
![openapi-sdkautomation[bot]](https://avatars.githubusercontent.com/in/10463?s=60&v=4){kind=small}
26 tasks
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14703/Microsoft.Azure.Management.Peering
branch
4 times, most recently
from
f508d73 to
f8c4c2a
Compare
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14703/Microsoft.Azure.Management.Peering
branch
from
f8c4c2a to
0e1742f
Compare
…val in Development env. (Azure#21969) * if not on defaults, honor custom value. * changelog.
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14703/Microsoft.Azure.Management.Peering
branch
from
0e1742f to
d5c3c0d
Compare
Since track 1 SDKs are deprecated, remove the solution to avoid having to type the solution name when building from sdk/keyvault each time. This shouldn't affect the build which enumerates projects within service directories.
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14703/Microsoft.Azure.Management.Peering
branch
from
d5c3c0d to
cb856ce
Compare
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14703/Microsoft.Azure.Management.Peering
branch
2 times, most recently
from
6c786ed to
70b8abd
Compare
* Add public ctor for SubscriptionValidationResponse * Comment out package reference.
* Add Stable API Version for point-in-time restore.
* Newly generated SDK from latest swagger
* Updating testcases to fix the CI break.
* Fixing test errors
* Fixed failing tests
* Updated SDK Version and updated release notes.
* Bumping up AssemblyVersion/AssemblyFileVersion("3.1.0.0") from ("3.0.0.0")
Also gets rid of unnecessary, deprecated enableSoftDelete parameter.
Azure#21968) * Fixed pipeline break * 100% methods have protocol overloads * API cleanup * Update API file * renamed message to content * bug fix and parameter validation
* Add asserts to verify all actions are counted for pending queue * Increase timeout of test
Bumps [log4net](https://github.com/apache/logging-log4net) from 2.0.3 to 2.0.10. - [Release notes](https://github.com/apache/logging-log4net/releases) - [Changelog](https://github.com/apache/logging-log4net/blob/master/ReleaseInstructions.txt) - [Commits](https://github.com/apache/logging-log4net/commits/rel/2.0.10) --- updated-dependencies: - dependency-name: log4net dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Update links with master to use main * Update ci.yml files Co-authored-by: Chidozie Ononiwu <[email protected]>
* Fix storage extension build * Add project reference * Shadow type * Camel case
…re#22009) * Fix typo: `AmqpSendAuthenticanToken` → `AmqpSendAuthenticationToken` * Fix claims: `System.String[]` → `Manage,Listen`
…#22112) * Added JWT writer * fixed bugs * Removed dependency on System.IdentityModel.Tokens.Jwt * cleaned up tests * Exposed registered claims as properties * cleaned up code * fixed build break * Update sdk/webpubsub/Azure.Messaging.WebPubSub/tests/WebPubSubParseConnectionStringTests.cs Co-authored-by: Matt Ellis <[email protected]> * PR review feedback * fixed build break * we are ok with ASCII * merged with main and updated to build * Added error checks * fixed misspelling Co-authored-by: Matt Ellis <[email protected]>
* Check for API review status only if release date is set in changelog * Change property name to ReleaseStatus Co-authored-by: Praveen Kuttappan <[email protected]>
Co-authored-by: Christopher Scott <[email protected]>
Co-authored-by: Praveen Kuttappan <[email protected]>
…2059) The focus of these changes is to introduce the `AmqpAnnotatedMessage` abstraction as the basis for `EventData`, allowing access to the full set of AMQP message data. This enables scenarios such as interaction with other message brokers that make use of the protocol in ways that are not otherwise exposed within the Event Hubs client. This set of changes will be followed by refactoring of the `AmqpMessageConverter` to work with the full AMQP message rather than the known `EventData` subset.
* Regenerate .NET SDK for Event Grid 2021-06-01-preview * remove fun code * Record tests * regenerate tests * update version * update assymblyinfo file Co-authored-by: Ashraf Hamad <[email protected]>
Co-authored-by: Wes Haggard <[email protected]>
Increment package version after release of Azure.Communication.CallingServer
…zure#22068) * Remove Date header from Hmac Policy * Update CallServer recorded sessions * Manually fix recorded session for playback only * Update missed files * Update missed CallServer session files Co-authored-by: JP Chen <[email protected]>
* Create new SDK for VMSS * Add Tests * Add SDK for VMSS * Recreate the generated folder * Regenerate the metadata file Co-authored-by: Aashish Rajaram Salokhe <[email protected]>
* spell check * wip
# All SDK Contribution checklist: This checklist is used to make sure that common guidelines for a pull request are followed. - [ ] **Please open PR in `Draft` mode if it is:** - Work in progress or not intended to be merged. - Encountering multiple pipeline failures and working on fixes. - [ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above. - [ ] **I have read the [contribution guidelines](https://github.com/Azure/azure-sdk-for-net/blob/master/CONTRIBUTING.md).** - [ ] **The pull request does not introduce [breaking changes](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/breaking-change-rules.md).** ### [General Guidelines and Best Practices](https://github.com/Azure/azure-sdk-for-net/blob/master/CONTRIBUTING.md#general-guidelines) - [ ] Title of the pull request is clear and informative. - [ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, [see this page](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md). ### [Testing Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/master/CONTRIBUTING.md#testing-guidelines) - [ ] Pull request includes test coverage for the included changes. ### [SDK Generation Guidelines](https://github.com/Azure/azure-sdk-for-net/blob/master/CONTRIBUTING.md#sdk-generation-guidelines) - [ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only) - [ ] The `*.csproj` and `AssemblyInfo.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]` or `Azure.ResourceManager.[RP]` - [ ] Include updated [management metadata](https://github.com/Azure/azure-sdk-for-net/tree/master/eng/mgmt/mgmtmetadata). - [ ] Update AzureRP.props to add/remove version info to maintain up to date API versions. ### 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: - Do not modify any code in generated folders. - Do not selectively include/remove generated files in the PR. - Do use `generate.ps1/cmd` to generate this PR instead of calling `autorest` 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**: `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules` ### 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.
* [Identity] Adding regional STS support * update changelog * update api spec * adding AZURE_REGIONAL_AUTHORITY_NAME environment variable support * fix build issue from merge * fix implicit casting of environment variable * fixing merge issues * fixing implicit RegionalAuthority cast issue
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14703/Microsoft.Azure.Management.Peering
branch
from
70b8abd to
ccb4e1f
Compare
The focus of these changes is to refactor the `AmqpMessageConverter` to perform translation based on the full `AmqpAnnotatedMessage` rather than the `EventData` projection, as had previously been done.
Merge 1f145a5e9d39d6670f94ccfc5af26d4339029459 into e793a8cd4b8d8b6b21cc7a26e364ad56d23a4861
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14703/Microsoft.Azure.Management.Peering
branch
from
ccb4e1f to
9d12e00
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.
Create to sync Azure/azure-rest-api-specs#14703
Installation Instructions
In order to use the generated nuget package in your app, you will have to use it from a private feed.
To create a private feed, see the following link:
https://docs.microsoft.com/en-us/nuget/hosting-packages/local-feeds
This will allow you to create a new local feed and add the location of the new feed as one of the sources.
Direct Download
The generated package can be directly downloaded from here: