[AutoPR Microsoft.Azure.Management.IotCentral] [Microsoft.IoTCentral/iotApps] Removal of legacy S1 SKU, S360 Fixes, newer RP API version 2021-06-01 #4121
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/14311/Microsoft.Azure.Management.IotCentral
branch
10 times, most recently
from
7951001 to
c1ddfc0
Compare
openapi-sdkautomation
bot
changed the title
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14311/Microsoft.Azure.Management.IotCentral
branch
from
c1ddfc0 to
5b6f3f4
Compare
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14311/Microsoft.Azure.Management.IotCentral
branch
from
5b6f3f4 to
2d393a2
Compare
openapi-sdkautomation
bot
changed the title
…val in Development env. (Azure#21969) * if not on defaults, honor custom value. * changelog.
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.
Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>
* 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] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
In order to avoid duplication of logic we are creating an msbuild target that dumps out the properties for each of the projects and then parsing that for our other engineering system needs.
* Update change log headers based on guideline update Updates based on Azure/azure-sdk#3103 - Renamed "Key Bugs Fixed" to "Bugs Fixed" - Renamed "Fixed" to "Other Changes" Added a warning in validation if at lease one of the recommended headers aren't used. * Update eng/common/scripts/ChangeLog-Operations.ps1 Co-authored-by: JoshLove-msft <54595583+JoshLove-msft@users.noreply.github.com> Co-authored-by: Wes Haggard <Wes.Haggard@microsoft.com> Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com> Co-authored-by: JoshLove-msft <54595583+JoshLove-msft@users.noreply.github.com>
* deprecated api * improve downloadcontent and download streaming * wip
* updates * Update sdk/textanalytics/Azure.AI.TextAnalytics/README.md Co-authored-by: Krista Pratico <krpratic@microsoft.com> Co-authored-by: Krista Pratico <krpratic@microsoft.com>
…zure#21988) * Mark EventListener using tests as non-parallelizable * Adjust test that throws exceptions from indexing action handlers Reduce number of documents used in the test so that EventSource does not log a very large number of events. * Do not create proxies from proxies * Fix more tests to avoid event exceptions * Use GetOriginal() helper method when creating proxies
* Generate AKS SDK for 2021-05-01 API * Remove deprecated test * Update package info * Update test record Co-authored-by: Kaiqi Zhang <kaiqzhan@microsoft.com>
# 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/main/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/main/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/main/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/main/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/main/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.
…failures generating new SDKs (Azure#21765) * Update DataCollectionRulesTests.cs commenting out the DataCollectionRulesTests because DataCollectionRules have a different error response format from everything else in AzureMonitor and so they can't be built with this SDK. * Update DataCollectionRulesTests.cs Commenting this the DataCollectionRulesTests because DataCollectionRules have a different error response format from everything else in AzureMonitor and so they can't be built with this SDK.
* Limit number of events stored in TestEventListener * Throw exception when events are dropped Increase default max event count to 1000. * Dispose the event listener in AzureIdentityEventSourceTests * Add comments on TestEventListener ctor * Dispose TestEventListener in a timely manner * Use method local TestEventListener in Search
…#21789)" (Azure#22471) This reverts commit d8cc63a.
Reason: The ACS SDKs (including Identity) are being handed over to the respective service teams.
* Add interop sample * File header * PR FB
Increment package version after release of Azure.Core.Amqp
Partial fix for Azure#22413
* Service Bus extension API updates * MaxEventBatchSize
Merge 864f1674e9451bb110e645c571e265ffabc16d0e into 7601061bfbb72b2f19cb29c46cbf9a397c2d8893
openapi-sdkautomation
bot
force-pushed
the
sdkAuto/14311/Microsoft.Azure.Management.IotCentral
branch
from
2d393a2 to
edd3af7
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#14311
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: