-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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 files for new api version 2017-03-31 (#1) #1054
Conversation
kejiun
commented
Mar 21, 2017
•
edited
Loading
edited
- added files for new api version 2017-03-31
- only releasing new version number, no api/signature changes
* added files for new api version 2017-03-31 * renamed folder
@kejiun, |
} | ||
], | ||
"responses": { | ||
"202": { |
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.
Here you are giving the status 202 which is accepted. But what is the final status? 200? If so, please include it
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.
The design of this API will be revisited after GA.
"GenerateRecommendations" | ||
], | ||
"description": "Retrieves the status of the recommendation computation or generation process. Invoke this API after calling the generation recommendation. The URI of this API is returned in the Location field of the response header.", | ||
"operationId": "Recommendations_GetGenerateRecommendationsStatus", |
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.
Are you particular in this name? Can it be names GenerateRecommendationsStatus_Get which is what we usually recommend
} | ||
], | ||
"responses": { | ||
"202": { |
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.
Here you mention 202 which is accepted. Now, how will I poll back to get the response? Which URI to hit? Usually it is obtained from the response of the 202. But there is no response here.
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.
The design of this API will be revisited after GA.
"Suppressions" | ||
], | ||
"description": "Obtains the details of a suppression.", | ||
"operationId": "Suppressions_Get", |
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.
Does this operation provide a list of suppressions for one recommendations? In that case, the recommendation is to use the id Suppressions_ListByRecommendations
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.
this one returns only one suppression
], | ||
"responses": { | ||
"200": { | ||
"description": "OK.", |
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.
Provide a valid description
], | ||
"responses": { | ||
"200": { | ||
"description": "OK.", |
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.
Provide a vaid description
"description": "The list of snoozed and dismissed rules for the recommendation.", | ||
"type": "array", | ||
"items": { | ||
"format": "uuid", |
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.
Is it possible to avoid usage of uuids?
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.
may I have the reason?
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.
Hank and I had a conversation on this. The design of this API will be revisited after GA. There may not be a need for suppressionIds. But lets not block GA due to this. This is read-only for now and service generates it. So user does not have to pass in the GUID.
} | ||
} | ||
}, | ||
"ResourceRecommendationBase": { |
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.
Can you confirm if this is a resource? If so, it should have an allOf of a resource.
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.
done
Running the swagger against linter, I get the following errors: ERROR: Per the Noun_Verb convention for Operation Ids, the noun 'Recommendations' should not appear after the underscore. Please fix them |
Based on the offline communications, I see some of the API design issues will be handled after GA release. The documentation issues seem to be resolved now. Approving these |
Can one of the admins verify this patch? |
#1054) * Remove hostnameprefix from properties and make checknameavailability regional * Remove 201 response declaration from the swagger spec