-
Notifications
You must be signed in to change notification settings - Fork 5.1k
AVS 1.0.0-preview.1 SDK #12602
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
AVS 1.0.0-preview.1 SDK #12602
Conversation
|
Hi @ctaggart according to our guideline if you want to check in your code to |
|
Should I change the namespace from Visual Studio freezes every time I try to open up either project I created and I'm not sure why. Can someone else try? Is there something in the test base that can create and teardown a test resource group? I ask, because that is what the azdev python test API does. It is really convenient. |
Yes
Happens to me too. Not sure why. VSCode works.
Common practice is to have your test project reference resource manager SDK |
|
I just added a commit to enable CI for this new module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another thing is, you may have noticed that our CI failed due to timeout. I have a commit checked in to master to solve the problem, so please merge or rebase master to get the fix. Thanks
sdk/avs/Microsoft.Azure.Management.Avs/src/Microsoft.Azure.Management.Avs.csproj
Outdated
Show resolved
Hide resolved
Co-authored-by: Yeming Liu <felix_liu@outlook.com>
|
Thanks @isra-fel. The initial test now passes. My goal is to add test coverage that matches the az vmware tests. |
|
Hi @isra-fel, please review and merge if approved. Basic tests have been added for major functionality. I'll add more with the next API version coming up soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
|
Thanks for merging! How do I get this built and in the dev feed? I don't see |
|
We have a guide here to build and publish your module to nuget.org, which is basically every dotnet SDK is doing. I'm not familiar with dev feed, but if you are sure that's where you want your module to go, I think you can follow the same process but choose not to publish, and upload the bits to dev feed manually. |
* initial Microsoft.AVS .NET SDK * start tests and rename part 1 * dir mv * make test project compile * renamed to AvsClient * Assembly Avs * case rename on Windows step 1 * step 2 * enable ci for avs * first test and recorded session * change version to 1.0.0-preview.1 Co-authored-by: Yeming Liu <felix_liu@outlook.com> * create and delete a private cloud * add cluster tests Co-authored-by: Yeming Liu <Yeming.Liu@microsoft.com> Co-authored-by: Yeming Liu <felix_liu@outlook.com>
The is the beginning of a .NET SDK for the Microsoft.AVS service. I used a local swagger file that is in this pull request Azure/azure-rest-api-specs#9773 . It currently just contains the generated code. I haven't made any tests using the test framework.