View on GitHub
Resource revisions
Rules for AIP-162, covering resource revisions.
| Rule name | Description |
|---|---|
| commit-http-body | Commit methods should use `*` as the HTTP body. |
| commit-http-method | Commit methods must use the POST HTTP verb. |
| commit-http-uri-suffix | Commit methods must have the correct URI suffix |
| commit-request-message-name | Commit methods must have standardized request message names. |
| commit-request-name-behavior | Commit requests should annotate the `name` field with `google.api.field_behavior`. |
| commit-request-name-field | Commit RPCs must have a `name` field in the request. |
| commit-request-name-reference | Commit requests should annotate the `name` field with `google.api.resource_reference`. |
| commit-response-message-name | Commit methods must have standardized response message names. |
| delete-revision-http-body | Delete Revision methods should not have an HTTP body. |
| delete-revision-http-method | Delete Revision methods must use the DELETE HTTP verb. |
| delete-revision-http-uri-suffix | Delete Revision methods must have the correct URI suffix |
| delete-revision-request-message-name | Delete Revision methods must have standardized request message names. |
| delete-revision-request-name-behavior | Delete Revision requests should annotate the `name` field with `google.api.field_behavior`. |
| delete-revision-request-name-field | Delete Revision RPCs must have a `name` field in the request. |
| delete-revision-request-name-reference | Delete Revision requests should annotate the `name` field with `google.api.resource_reference`. |
| delete-revision-response-message-name | Delete Revision methods must return the resource. |
| rollback-http-body | Rollback methods should use `*` as the HTTP body. |
| rollback-http-method | Rollback methods must use the POST HTTP verb. |
| rollback-http-uri-suffix | Rollback methods must have the correct URI suffix |
| rollback-request-message-name | Rollback methods must have standardized request message names. |
| rollback-request-name-behavior | Rollback requests should annotate the `name` field with `google.api.field_behavior`. |
| rollback-request-name-field | Rollback RPCs must have a `name` field in the request. |
| rollback-request-name-reference | Rollback requests should annotate the `name` field with `google.api.resource_reference`. |
| rollback-request-revision-id-behavior | Rollback requests should annotate the `revision_id` field with `google.api.field_behavior`. |
| rollback-request-revision-id-field | Rollback RPCs must have a `revision_id` field in the request. |
| rollback-response-message-name | Rollback methods must have standardized response message names. |
| tag-revision-http-body | Tag Revision methods should use `*` as the HTTP body. |
| tag-revision-http-method | Tag Revision methods must use the POST HTTP verb. |
| tag-revision-http-uri-suffix | Tag Revision methods must have the correct URI suffix |
| tag-revision-request-message-name | Tag Revision methods must have standardized request message names. |
| tag-revision-request-name-behavior | Tag Revision requests should annotate the `name` field with `google.api.field_behavior`. |
| tag-revision-request-name-field | Tag Revision RPCs must have a `name` field in the request. |
| tag-revision-request-name-reference | Tag Revision requests should annotate the `name` field with `google.api.resource_reference`. |
| tag-revision-request-tag-behavior | Tag Revision requests should annotate the `tag` field with `google.api.field_behavior`. |
| tag-revision-request-tag-field | Tag Revision RPCs must have a `tag` field in the request. |
| tag-revision-response-message-name | Tag Revision methods must have standardized response message names. |
Note: Because AIPs sometimes cover topics that have some overlap, some rules related to resource revisions may be included in the rules for other AIPs.