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

Microsoft.NetApp first version #3639

Merged
merged 2 commits into from
Aug 27, 2018
Merged

Microsoft.NetApp first version #3639

merged 2 commits into from
Aug 27, 2018

Conversation

grimurjonsson
Copy link
Contributor

Has been previously merged into azure-rest-api-specs-pr: https://github.com/Azure/azure-rest-api-specs-pr/pull/513

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR 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 information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#3203

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@lmazuel lmazuel requested a review from ravbhatnagar August 14, 2018 21:15
@lmazuel lmazuel added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 14, 2018
clear-output-folder: true
```

## Python
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will fix

```


## C#
Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will fix

"description": "Microsoft NetApp Azure Resource Provider specification",
"version": "2017-08-15",
"x-ms-code-generation-settings": {
"name": "CloudVolumeManagementClient"
Copy link
Member

Choose a reason for hiding this comment

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

Why is that renaming? Shouldn't then rename the package to azure-mgmt-cloudvolume? What is the commercial advertising of this service on https://azure.microsoft.com/en-us/services/ ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't really understand what you mean. If you mean the x-ms-code-generation-settings, then I think I copied that from some document I was pointed out to use as reference. I think it's safe to remove. (I see its not in the cdn.json you're referencing)

Copy link
Member

@lmazuel lmazuel Aug 14, 2018

Choose a reason for hiding this comment

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

x-ms-code-generation-settings/name is the final constructor name in the SDK. So it seemed weird to me to have a package called "netapp", with a constructor called "CloudVolumeManagementClient" :)

Do not remove that node, otherwise the constructor will be called "MicrosoftNetAppClient" which is probably not what you want. Renaming "NetAppManagementClient" I guess makes sense.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changing to AzureNetAppFilesManagementClient, since thats the name of service on the site you posted.

}
],
"get": {
"description": "Lists all NetApp accounts in the subscription",
Copy link
Member

Choose a reason for hiding this comment

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

Wrong description since ResourceGroup is a parameter

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will fix

payload-flattening-threshold: 2
namespace: azure.mgmt.netapp
package-name: azure-mgmt-netapp
package-version: 5.0.0
Copy link
Member

Choose a reason for hiding this comment

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

Why 5.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

no reason, changing to 1.0

}
},
"Operation": {
"description": "Storage REST API operation definition.",
Copy link
Member

Choose a reason for hiding this comment

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

Copy/paste issue?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, will fix

"type": "string",
"description": "The origin of operations."
},
"properties": {
Copy link
Member

@lmazuel lmazuel Aug 14, 2018

Choose a reason for hiding this comment

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

You probably miss a $ref OperationProperties for details here, otherwise this node is interpreted as string (which likely isn't)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will fix

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@grimurjonsson
Copy link
Contributor Author

Ping.

@lmazuel lmazuel merged commit fbe5a21 into Azure:master Aug 27, 2018
ncalagar pushed a commit to ncalagar/azure-rest-api-specs that referenced this pull request Aug 28, 2018
* Remove TrackedResource from Swagger spec

"$ref": "../../common/v1/definitions.json#/definitions/TrackedResource"

* More updates on referring common types

More updates on referring common types

* Add UpdateParameters and Updateproperties

* Update example

* updated example

* update examples

Introducing new API for Azure Security Center Settings (Azure#3511)

* Add new API for Azure Security Center Settings

* Changed SettingsPUT API to receive parameter and not definition.

* - changed settings parameter name in example and in security parameter definition
- changes typo comment on settings get all example reference

* changes settings to setting in Settings API

* settings kind to setting kind in settings CSM API

Update batch resource-manager Node.js package version to 3.1.2 (Azure#3732)

IoTHub conf py (Azure#3733)

Reports API moved from stable to preview version with addition of documentation of a couple of new APIs (Azure#3640)

* Consumption specifications for cost insights and reporting operations

* Fixed $ref for ReportConfigDelete

* Silly me!! Fixed bad reference again

* Fixed schema validation issues

* Fixing validation errors around datetime and dynamic respones

* Fixed parameters in examples

* Fixed parameter name in example

* Removed x-ms-odata method for POST op

* Fixed ARM review comments

* Moved reports and usage analysis from microsoft.consumption to microsoft.costmanagament

* Merged with master again

* Updated reports api documentation

* Undo remove of API from stable version

providing description for new introduced property isRecurringCharge

fix example issues

Microsoft.ResourceGraph public preview spec (Azure#3716)

Add new microsoft.logic version (Azure#3683)

* Copy of the source version (2016-06-01) to seed the new version (2018-07-01-preview)

* Update Microsoft.Logic from 2016-06-01 to 2018-07-01-preview

* Remove extra prep files, update the readme

Fix Go SDK codegen for containerinstance (Azure#3735)

The package-2018-06 tag was incorrecly using the 2018-04 tag.
Moved Go SDK config section to its own config file.

Microsoft.NetApp first version (Azure#3639)

* Microsoft.NetApp first version

* Addressing pullrequest comments

added back billingperiod
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants