-
Notifications
You must be signed in to change notification settings - Fork 47
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
Add new rule for new flag "x-ms-long-running-operation-options" #172
Comments
|
@fearthecowboy fixed |
Edit: updated values list with "original-uri" |
Edit: added default thanks to @sarangan12 |
I found this issue has 3 parts to this:
Among these parts, Only Part 1 needs to be implemented. You do NOT need to implement Part 2 & Part 3. They are automatically handled by Autorest Schema Validator (which gets executed before linter.). So, if these parts are violated then the autorest will error out even before the linter starts its execution. Example 1
Example 2
For Part 1, the code changes are ready and available at the PR: #179 |
Operation marked ad LRO can now have a new flag called "x-ms-long-running-operation-options":
For the linter to check the correct usage of this new flag:
Rule 1: If the operation is the POST LRO and with return type, the option "x-ms-long-running-operation-options" is required, and the option "final-state-via" is required.
Rule 2: The only authorized values of "final-state-via" are "location" or "azure-async-operation" or "original-uri" or "default"
The text was updated successfully, but these errors were encountered: