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

Added reservation recommendations and tags #2679

Merged
merged 16 commits into from
Mar 19, 2018
Merged

Added reservation recommendations and tags #2679

merged 16 commits into from
Mar 19, 2018

Conversation

asarkar84
Copy link
Contributor

@asarkar84 asarkar84 commented Mar 16, 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

@AutorestCI
Copy link

AutorestCI commented Mar 16, 2018

Automation for azure-libraries-for-java

Nothing to generate for azure-libraries-for-java

@AutorestCI
Copy link

AutorestCI commented Mar 16, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented Mar 16, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Mar 16, 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#1328

Copy link
Member

@jhendrixMSFT jhendrixMSFT left a comment

Choose a reason for hiding this comment

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

Also note that the addition of the '$apply' parameter will introduce a breaking change for some SDKs.

"$ref": "./examples/ReservationRecommendationsFilterByScopeLookBackPeriod.json"
}
},
"parameters": [
Copy link
Member

Choose a reason for hiding this comment

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

The subscriptionId parameter is missing which is the cause of the travis failure, see the log.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure! Just missed it. I have added it.

"tags": [
"ReservationRecommendations"
],
"operationId": "reservationRecommendations_List",
Copy link
Member

Choose a reason for hiding this comment

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

Should be "ReservationRecommendations_List" (upper-case 'r').

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure! Corrected.

"recommendedQuantity": 1,
"totalCostWithReservedInstances": 0.0,
"netSavings": 4.634521202630137,
"firstUsageDate": "2018-03-06",
Copy link
Member

Choose a reason for hiding this comment

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

The schema defines this as date/time however you've only provided a date; this is causing model validation failures, see the log. This is applicable to other samples as well.

Copy link
Contributor Author

@asarkar84 asarkar84 Mar 16, 2018

Choose a reason for hiding this comment

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

Thanks! for sharing this. I have changed the format to DateTime in example.

Incorporated review comments
@asarkar84
Copy link
Contributor Author

Review comments have been incorporated. Please take a look now.

Incorporated review comments
"firstUsageDate": {
"description": "The usage date for looking back.",
"type": "string",
"format": "date-time",
Copy link
Member

Choose a reason for hiding this comment

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

There are still model validation failure regarding this date-time, see the log. Is this supposed to be just date like the others you changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry! Typo error. There was a space in the datetime string example. Just corrected it and waiting for build to complete.

Removed unwanted space
@asarkar84 asarkar84 requested a review from a user March 16, 2018 19:59
@asarkar84 asarkar84 requested a review from vladbarosan as a code owner March 16, 2018 19:59
"recommendedQuantity": 1,
"totalCostWithReservedInstances": 0.0,
"netSavings": 4.634521202630137,
"firstUsageDate": "2018-03-06T00:00:00Z ",
Copy link
Member

Choose a reason for hiding this comment

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

Another extra whitespace, looks like there's on line 42 as well. Please scrub the remaining example files for this error.

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! I have verified the other files as well.

Removed extra whitespace
@jhendrixMSFT
Copy link
Member

@AutorestCI rebuild azure-sdk-for-go

@asarkar84
Copy link
Contributor Author

Please merge the PR if everything looks good. Thank you!

@jhendrixMSFT jhendrixMSFT merged commit 1ed1606 into Azure:master Mar 19, 2018
@ravbhatnagar ravbhatnagar added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Mar 21, 2018
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
Adding arczoneid properties for the resources...
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 potential-sdk-breaking-change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants