Skip to content

Conversation

@eliagrady
Copy link
Member

Regenerate SDK & fix tests.
Missing ExternalSecuritySolutionsTests sessionRecords - should not block since current ones are invalid as well.

@eliagrady eliagrady changed the title Update security SDK gen (no additions) AzureSecurityCenter - Update Microsoft.Security SDK generation Nov 4, 2020
@eliagrady eliagrady force-pushed the update_security_sdkGen branch from fbebae8 to aaf317c Compare November 5, 2020 09:02
@eliagrady
Copy link
Member Author

@YalinLi0312 \ @allenjzhang Could you please follow the checklist below?

  • Swagger review PR(s) link in PR description, and the PR(s) is merged - no specific swagger changes resulted in this PR
  • Metadata file eng/mgmt/mgmtmetadata_{RP}.txt is updated
  • Versions in *.csproj and AssemblyInfo.cs are updated, and follows semver
  • Release notes in *.csproj is updated
  • If there's a API-version update, the API tags in Az.Sdk.props are updated - please review this part
  • Generated code is not touched
  • Proper test coverage

@eliagrady
Copy link
Member Author

@allenjzhang , can you approve?

@m-nash
Copy link
Member

m-nash commented Nov 10, 2020

@eliagrady can you link the swagger PR that this is associated with?

@eliagrady
Copy link
Member Author

@eliagrady can you link the swagger PR that this is associated with?

There are no specific changes in the API in this PR - this PR is regen of the SDK and adding test coverage.

@m-nash
Copy link
Member

m-nash commented Nov 10, 2020

Typically a release of new swagger goes out ahead of the SDK. The SDK is then regenerated off of that new swagger commit id (associated with the PR). It appears from the metadata file that this was the swagger PR? Azure/azure-rest-api-specs#11518 Is that correct?

@eliagrady
Copy link
Member Author

Typically a release of new swagger goes out ahead of the SDK. The SDK is then regenerated off of that new swagger commit id (associated with the PR). It appears from the metadata file that this was the swagger PR? Azure/azure-rest-api-specs#11518 Is that correct?

Azure/azure-rest-api-specs#10100 is more likely - I believe there were a few merges to azure-rest-api-specs without SDK respective generations - this PR is indented to downsize this growing gap.

@eliagrady
Copy link
Member Author

Here's a Swagger PR: Azure/azure-rest-api-specs#10418 (I've added the missing tests for this one)

Can you please squash-merge-approve this?

Copy link
Member

@m-nash m-nash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Azure/azure-rest-api-specs#10100 was the one I was looking for which has the breaking change in it and the approved-breakingchange label.

@m-nash m-nash merged commit d39e67f into Azure:master Nov 12, 2020
@VeryEarly
Copy link
Contributor

Hi @m-nash ,

This SDK doesn't have api version generated, is that expected?

annelo-msft pushed a commit to annelo-msft/azure-sdk-for-net that referenced this pull request Feb 17, 2021
…#16580)

* autogenerated code using autorest

* regen SDK

* regen SDK metadata

* fix AdaptiveApplicationControlsTests

* fix AdaptiveApplicationControlsTests

* modify subAssessment tests and sessionRecords

* re-record compliances test sessions

* re-record discovered security solutions test sessions

* modify security alerts tests and sessionRecords

* re-record iot security solutions device security groups test sessions

* re-record iot security solutions test sessions

* re-record iot security solutions analtyics test sessions

* re-record iot security solutions test sessions

* re-record AdvancedThreatProtection test sessions

* adjust IotSecuritySolutionsAnalyticsRecommendation test

* temp: exclude ExternalSecuritySolutionsTests - require re-recording of session records

* add assessment tests and session records

* update AzSdk.RP.props, AssemblyInfo.cs and csproj release notes

* add iot sensors tests + session records

* rename IoT to Iot (naming conventions)

* remove redundant test

* add iot defender settings tests + session records
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants