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

Add support for Managed Instance for Apache Cassandra #19221

Merged
merged 9 commits into from
Mar 9, 2021
Merged

Add support for Managed Instance for Apache Cassandra #19221

merged 9 commits into from
Mar 9, 2021

Conversation

frrossms
Copy link
Contributor

@frrossms frrossms commented Mar 4, 2021

Based on Swagger PRs:

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.
  • The pull request does not introduce breaking changes.

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,

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.

frrossms added 7 commits March 5, 2021 13:07
Ran the command:

autorest C:\Users\frross\source\repos\azure-rest-api-specs\specification\cosmos-db\resource-manager\readme.md `
    --csharp --version=v2 --reflect-api-versions `
    --csharp-sdks-folder=C:\Users\frross\source\repos\azure-sdk-for-net\sdk `
    --tags=package-2021-03-preview
The preview release has quite a different structure, so I went back to the last release from it (commit 18e1b96) and copied the test files here. The project builds, but the tests have a couple errors to fix.
The Swagger changes needed were checked in, so rerun autorun from the master branch in the main repo instead of against a local checkout so the metadata is correct.
@frrossms
Copy link
Contributor Author

frrossms commented Mar 8, 2021

@m-nash I'm getting test failures saying it can't find an ARM template from TestData that is supposed to be copied to the output directory. I got that pattern from other parts of the repo that do the same thing. Do you have any insight on why it's not working on Github's tests?

frrossms added 2 commits March 8, 2021 10:48
I had hardcoded a \ instead of using Path.PathSeparator.
Instead of Path.Separator, which is making the build fail, just use a /, which is supported on all platforms.
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.

Approved since breaking change approved label was added

@@ -6,17 +6,14 @@
<PropertyGroup>
<PackageId>Microsoft.Azure.Management.CosmosDB</PackageId>
<Description>Provides developers with libraries for the CosmosDB under Azure Resource manager to manage CosmosDB Account, Databases and child resources and their available management capabilities. Create, Delete, Update CosmosDB Account, Databases and child resources. Note: This client library is for CosmosDB under Azure Resource Manager.</Description>
<Version>2.0.0</Version>
<Version>2.1.0</Version>
Copy link
Contributor

Choose a reason for hiding this comment

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

this version is wrong. It should be 2.1.0-preview. I cannot release without this change.

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.

3 participants