Skip to content

Adding swagger for new api-version consumption 2018-08-31#3725

Closed
ncalagar wants to merge 11 commits intoAzure:masterfrom
ncalagar:master
Closed

Adding swagger for new api-version consumption 2018-08-31#3725
ncalagar wants to merge 11 commits intoAzure:masterfrom
ncalagar:master

Conversation

@ncalagar
Copy link
Contributor

@ncalagar ncalagar commented Aug 25, 2018

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Aug 25, 2018

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#2158

@AutorestCI
Copy link

AutorestCI commented Aug 25, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Aug 25, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Aug 25, 2018

Automation for azure-sdk-for-node

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-node#3319

@AutorestCI
Copy link

AutorestCI commented Aug 25, 2018

Automation for azure-sdk-for-go

A PR has been created for you:
Azure/azure-sdk-for-go#2542

@sergey-shandar
Copy link
Contributor

@ncalagar Is there a commit where we can see all the changes between old and new API?

ncalagar and others added 7 commits August 27, 2018 14:18
* 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
@ncalagar
Copy link
Contributor Author

ncalagar commented Aug 28, 2018

@sergey-shandar Here is list of new changes to this new version:

  • Adding new property "isRecurringCharge" to MarketplaceProperties
  • Adding charges apis and their associated changes and examples
  • Adding two new properties “usageStart” and “usageEnd” to ManagementGroupAggregatedCostProperties and addin usageStart and usageEnd filter to ManangmentGroupAggregatedCost and examples
  • Removing CostTags API and its examples

@ms-premp
Copy link
Contributor

@ms-premp fyi

Copy link
Contributor

@sergey-shandar sergey-shandar left a comment

Choose a reason for hiding this comment

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

@ncalagar we need two commits, the first one should be a copy from previous API version (with API-VERSION changes) and the second one is the changes. https://github.com/Azure/azure-rest-api-specs/blob/master/.github/CONTRIBUTING.md#filenames-and-folder-structure

Or use the portal https://portal.azure-devex-tools.com/app (preferred).

@ncalagar
Copy link
Contributor Author

@sergey-shandar Sure, in order to do that, I'm going to close this pull request and create a new one with mentioned 2 commits.

@ncalagar ncalagar closed this Aug 29, 2018
@ncalagar
Copy link
Contributor Author

@sergey-shandar This is the link to new PR : #3766

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.

6 participants