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

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

Merged
merged 17 commits into from
Aug 27, 2018

Conversation

shalinved
Copy link
Contributor

@shalinved shalinved commented Aug 14, 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 14, 2018

Automation for azure-sdk-for-python

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

@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-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Aug 14, 2018

Automation for azure-sdk-for-go

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-go#2546

@shalinved
Copy link
Contributor Author

@ravbhatnagar, @ms-premp

@sergey-shandar sergey-shandar added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required potential-sdk-breaking-change labels Aug 15, 2018
}
}
},
"/subscriptions/{subscriptionId}/providers/Microsoft.CostManagement/reports/{reportName}/run": {
Copy link
Contributor

Choose a reason for hiding this comment

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

This API signature will not work. PUT on /run needs the name of the run to be created.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated to POST

}
}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CostManagement/reports/{reportName}/run": {
Copy link
Contributor

Choose a reason for hiding this comment

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

same comment as above.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated to POST

"$ref": "./examples/ReportConfigDelete.json"
"$ref": "./examples/ReportDelete.json"
}
},
Copy link
Contributor

Choose a reason for hiding this comment

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

can you please move the changes of removing apis that we discussed over the call last week and adding new ones in different PRs? Lets have one PR where the removal is done.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

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.

Why are you moving from stable to preview? Usually, we don't allow this.

@shalinved
Copy link
Contributor Author

@sergey-shandar - We had a couple of meeting with @ravbhatnagar on moving the APIs from stable to preview. These APIs were never meant to be released as a stable version. They were meant to unblock internal Microsoft teams integrating with us. We didn't create any SDKs, didn't publish the APIs and have already verified that all the requests we received are from internal Microsoft teams.

We understand that once the APIs are available publicly, someone could build SDKs on top of these APIs and that experience might get broken but the data we have combined with absence of any API announcements suggests there is a very slim chance of that happening.

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.

We still need a formal approval from ARM

@ravbhatnagar
Copy link
Contributor

Signing off from ARM side.

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Aug 24, 2018
@sergey-shandar
Copy link
Contributor

@shalinved please, resolve conflicts

@sergey-shandar sergey-shandar removed the request for review from salameer August 24, 2018 00:54
@shalinved
Copy link
Contributor Author

@sergey-shandar - Conflicts fixed after merging with upstream.

@sergey-shandar sergey-shandar merged commit 21d580e 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
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants