Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(Azure Monitor) Data Collection Rules stable 2021-04-01 #21128

Merged
merged 19 commits into from
Jul 1, 2021

Conversation

herreraj-ms
Copy link
Contributor

@herreraj-ms herreraj-ms commented May 17, 2021

All SDK Contribution checklist:

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines and Best Practices

  • 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.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

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.
  • 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.

@herreraj-ms
Copy link
Contributor Author

error in "net - mgmt ci" is because readme.md is pointing to "package-2020-03", but the new specs are in "package-2021-04-only"

image

@herreraj-ms
Copy link
Contributor Author

I left a comment of the issue on the specs PR: Azure/azure-rest-api-specs#14542 (comment)

For .NET client, manual fixes are required to deal with the duplicate model issue.

Does this make sense? Or is there other way for fixing it?

@herreraj-ms
Copy link
Contributor Author

herreraj-ms commented Jun 18, 2021

@allenjzhang the check "net -mgmt - ci" is failling because is using a previous readme.md version:

============================
##[error]Discrepancy detected between generated code in PR and reference generation. Please note, the files in the Generated folder should not be modified OR adding/excluding files. You may need to re-run sdk<RP_Name>\generate.ps1.
error: Discrepancy detected between generated code in PR and reference generation. Please note, the files in the Generated folder should not be modified OR adding/excluding files. You may need to re-run sdk<RP_Name>\generate.ps1.
============================
For reference, we are using following commands for the code check: 
autorest https://github.com/Azure/azure-rest-api-specs/blob/27cc07ddd294d98e05cb301e07a72378df9f87e8/specification/monitor/resource-manager/readme.md --csharp --version=v2 --reflect-api-versions --csharp-sdks-folder=D:/a/1/s/sdk  --use:@microsoft.azure/[email protected]

Should not the specs from the master branch be used for this check?
This one: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/monitor/resource-manager/readme.md

@herreraj-ms
Copy link
Contributor Author

@allenjzhang ping

@allenjzhang allenjzhang merged commit 4dc9e20 into Azure:main Jul 1, 2021
azure-sdk pushed a commit to azure-sdk/azure-sdk-for-net that referenced this pull request Nov 3, 2022
Added Response Schema for Runbook Operation (Azure#21128)

* Added Response Schema for Runbook Operation

* Update resopnse of Runbook Operation

* Updated example to fix Avacado errors

* Update resopnse of Runbook Operation

* Updated example to fix Avacado errors

* Fix Lint diff errors

* Fix Avacado errors

* Fix Avacado errors

Co-authored-by: Sushil Upadhyay <[email protected]>
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.

2 participants