| Index: discovery/googleapis/firebaserules__v1.json
|
| diff --git a/discovery/googleapis/firebaserules__v1.json b/discovery/googleapis/firebaserules__v1.json
|
| index 76951346c4310e139a710f740872d6c426ab5a9c..6cf9b2c6f8e797c04db6289ccd7f9130b92f5c98 100644
|
| --- a/discovery/googleapis/firebaserules__v1.json
|
| +++ b/discovery/googleapis/firebaserules__v1.json
|
| @@ -2,14 +2,14 @@
|
| "auth": {
|
| "oauth2": {
|
| "scopes": {
|
| + "https://www.googleapis.com/auth/cloud-platform": {
|
| + "description": "View and manage your data across Google Cloud Platform services"
|
| + },
|
| "https://www.googleapis.com/auth/firebase": {
|
| "description": "View and administer all your Firebase data and settings"
|
| },
|
| "https://www.googleapis.com/auth/firebase.readonly": {
|
| "description": "View all your Firebase data and settings"
|
| - },
|
| - "https://www.googleapis.com/auth/cloud-platform": {
|
| - "description": "View and manage your data across Google Cloud Platform services"
|
| }
|
| }
|
| }
|
| @@ -31,22 +31,6 @@
|
| "ownerDomain": "google.com",
|
| "ownerName": "Google",
|
| "parameters": {
|
| - "pp": {
|
| - "default": "true",
|
| - "description": "Pretty-print response.",
|
| - "location": "query",
|
| - "type": "boolean"
|
| - },
|
| - "bearer_token": {
|
| - "description": "OAuth bearer token.",
|
| - "location": "query",
|
| - "type": "string"
|
| - },
|
| - "oauth_token": {
|
| - "description": "OAuth 2.0 token for the current user.",
|
| - "location": "query",
|
| - "type": "string"
|
| - },
|
| "upload_protocol": {
|
| "description": "Upload protocol for media (e.g. \"raw\", \"multipart\").",
|
| "location": "query",
|
| @@ -58,13 +42,13 @@
|
| "location": "query",
|
| "type": "boolean"
|
| },
|
| - "uploadType": {
|
| - "description": "Legacy upload protocol for media (e.g. \"media\", \"multipart\").",
|
| + "fields": {
|
| + "description": "Selector specifying which fields to include in a partial response.",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| - "fields": {
|
| - "description": "Selector specifying which fields to include in a partial response.",
|
| + "uploadType": {
|
| + "description": "Legacy upload protocol for media (e.g. \"media\", \"multipart\").",
|
| "location": "query",
|
| "type": "string"
|
| },
|
| @@ -116,6 +100,22 @@
|
| "description": "Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.",
|
| "location": "query",
|
| "type": "string"
|
| + },
|
| + "pp": {
|
| + "default": "true",
|
| + "description": "Pretty-print response.",
|
| + "location": "query",
|
| + "type": "boolean"
|
| + },
|
| + "bearer_token": {
|
| + "description": "OAuth bearer token.",
|
| + "location": "query",
|
| + "type": "string"
|
| + },
|
| + "oauth_token": {
|
| + "description": "OAuth 2.0 token for the current user.",
|
| + "location": "query",
|
| + "type": "string"
|
| }
|
| },
|
| "protocol": "rest",
|
| @@ -280,6 +280,31 @@
|
| },
|
| "releases": {
|
| "methods": {
|
| + "delete": {
|
| + "description": "Delete a `Release` by resource name.",
|
| + "httpMethod": "DELETE",
|
| + "id": "firebaserules.projects.releases.delete",
|
| + "parameterOrder": [
|
| + "name"
|
| + ],
|
| + "parameters": {
|
| + "name": {
|
| + "description": "Resource name for the `Release` to delete.\n\nFormat: `projects/{project_id}/releases/{release_id}`",
|
| + "location": "path",
|
| + "pattern": "^projects/[^/]+/releases/.+$",
|
| + "required": true,
|
| + "type": "string"
|
| + }
|
| + },
|
| + "path": "v1/{+name}",
|
| + "response": {
|
| + "$ref": "Empty"
|
| + },
|
| + "scopes": [
|
| + "https://www.googleapis.com/auth/cloud-platform",
|
| + "https://www.googleapis.com/auth/firebase"
|
| + ]
|
| + },
|
| "get": {
|
| "description": "Get a `Release` by name.",
|
| "httpMethod": "GET",
|
| @@ -314,11 +339,6 @@
|
| "name"
|
| ],
|
| "parameters": {
|
| - "filter": {
|
| - "description": "`Release` filter. The list method supports filters with restrictions on the\n`Release.name`, `Release.ruleset_name`, and `Release.test_suite_name`.\n\nExample 1: A filter of 'name=prod*' might return `Release`s with names\nwithin 'projects/foo' prefixed with 'prod':\n\nName | Ruleset Name\n------------------------------|-------------\nprojects/foo/releases/prod | projects/foo/rulesets/uuid1234\nprojects/foo/releases/prod/v1 | projects/foo/rulesets/uuid1234\nprojects/foo/releases/prod/v2 | projects/foo/rulesets/uuid8888\n\nExample 2: A filter of `name=prod* ruleset_name=uuid1234` would return only\n`Release` instances for 'projects/foo' with names prefixed with 'prod'\nreferring to the same `Ruleset` name of 'uuid1234':\n\nName | Ruleset Name\n------------------------------|-------------\nprojects/foo/releases/prod | projects/foo/rulesets/1234\nprojects/foo/releases/prod/v1 | projects/foo/rulesets/1234\n\nIn the examples, the filter parameters refer to the search filters are\nrelative to the project. Fully qualified prefixed may also be used. e.g.\n`test_suite_name=projects/foo/testsuites/uuid1`",
|
| - "location": "query",
|
| - "type": "string"
|
| - },
|
| "name": {
|
| "description": "Resource name for the project.\n\nFormat: `projects/{project_id}`",
|
| "location": "path",
|
| @@ -336,6 +356,11 @@
|
| "format": "int32",
|
| "location": "query",
|
| "type": "integer"
|
| + },
|
| + "filter": {
|
| + "description": "`Release` filter. The list method supports filters with restrictions on the\n`Release.name`, `Release.ruleset_name`, and `Release.test_suite_name`.\n\nExample 1: A filter of 'name=prod*' might return `Release`s with names\nwithin 'projects/foo' prefixed with 'prod':\n\nName | Ruleset Name\n------------------------------|-------------\nprojects/foo/releases/prod | projects/foo/rulesets/uuid1234\nprojects/foo/releases/prod/v1 | projects/foo/rulesets/uuid1234\nprojects/foo/releases/prod/v2 | projects/foo/rulesets/uuid8888\n\nExample 2: A filter of `name=prod* ruleset_name=uuid1234` would return only\n`Release` instances for 'projects/foo' with names prefixed with 'prod'\nreferring to the same `Ruleset` name of 'uuid1234':\n\nName | Ruleset Name\n------------------------------|-------------\nprojects/foo/releases/prod | projects/foo/rulesets/1234\nprojects/foo/releases/prod/v1 | projects/foo/rulesets/1234\n\nIn the examples, the filter parameters refer to the search filters are\nrelative to the project. Fully qualified prefixed may also be used. e.g.\n`test_suite_name=projects/foo/testsuites/uuid1`",
|
| + "location": "query",
|
| + "type": "string"
|
| }
|
| },
|
| "path": "v1/{+name}/releases",
|
| @@ -403,124 +428,43 @@
|
| "https://www.googleapis.com/auth/cloud-platform",
|
| "https://www.googleapis.com/auth/firebase"
|
| ]
|
| - },
|
| - "delete": {
|
| - "description": "Delete a `Release` by resource name.",
|
| - "httpMethod": "DELETE",
|
| - "id": "firebaserules.projects.releases.delete",
|
| - "parameterOrder": [
|
| - "name"
|
| - ],
|
| - "parameters": {
|
| - "name": {
|
| - "description": "Resource name for the `Release` to delete.\n\nFormat: `projects/{project_id}/releases/{release_id}`",
|
| - "location": "path",
|
| - "pattern": "^projects/[^/]+/releases/.+$",
|
| - "required": true,
|
| - "type": "string"
|
| - }
|
| - },
|
| - "path": "v1/{+name}",
|
| - "response": {
|
| - "$ref": "Empty"
|
| - },
|
| - "scopes": [
|
| - "https://www.googleapis.com/auth/cloud-platform",
|
| - "https://www.googleapis.com/auth/firebase"
|
| - ]
|
| }
|
| }
|
| }
|
| }
|
| }
|
| },
|
| - "revision": "20170418",
|
| + "revision": "20170523",
|
| "rootUrl": "https://firebaserules.googleapis.com/",
|
| "schemas": {
|
| - "TestRulesetResponse": {
|
| - "description": "The response for FirebaseRulesService.TestRuleset.",
|
| - "id": "TestRulesetResponse",
|
| - "properties": {
|
| - "testResults": {
|
| - "description": "The set of test results given the test cases in the `TestSuite`.\nThe results will appear in the same order as the test cases appear in the\n`TestSuite`.",
|
| - "items": {
|
| - "$ref": "TestResult"
|
| - },
|
| - "type": "array"
|
| - },
|
| - "issues": {
|
| - "description": "Syntactic and semantic `Source` issues of varying severity. Issues of\n`ERROR` severity will prevent tests from executing.",
|
| - "items": {
|
| - "$ref": "Issue"
|
| - },
|
| - "type": "array"
|
| - }
|
| - },
|
| + "Empty": {
|
| + "description": "A generic empty message that you can re-use to avoid defining duplicated\nempty messages in your APIs. A typical example is to use it as the request\nor the response type of an API method. For instance:\n\n service Foo {\n rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);\n }\n\nThe JSON representation for `Empty` is empty JSON object `{}`.",
|
| + "id": "Empty",
|
| + "properties": {},
|
| "type": "object"
|
| },
|
| - "ListRulesetsResponse": {
|
| - "description": "The response for FirebaseRulesService.ListRulesets.",
|
| - "id": "ListRulesetsResponse",
|
| + "FunctionMock": {
|
| + "description": "Mock function definition.\n\nMocks must refer to a function declared by the target service. The type of\nthe function args and result will be inferred at test time. If either the\narg or result values are not compatible with function type declaration, the\nrequest will be considered invalid.\n\nMore than one `FunctionMock` may be provided for a given function name so\nlong as the `Arg` matchers are distinct. There may be only one function\nfor a given overload where all `Arg` values are `Arg.any_value`.",
|
| + "id": "FunctionMock",
|
| "properties": {
|
| - "nextPageToken": {
|
| - "description": "The pagination token to retrieve the next page of results. If the value is\nempty, no further results remain.",
|
| + "function": {
|
| + "description": "The name of the function.\n\nThe function name must match one provided by a service declaration.",
|
| "type": "string"
|
| },
|
| - "rulesets": {
|
| - "description": "List of `Ruleset` instances.",
|
| - "items": {
|
| - "$ref": "Ruleset"
|
| - },
|
| - "type": "array"
|
| - }
|
| - },
|
| - "type": "object"
|
| - },
|
| - "TestResult": {
|
| - "description": "Test result message containing the state of the test as well as a\ndescription and source position for test failures.",
|
| - "id": "TestResult",
|
| - "properties": {
|
| - "functionCalls": {
|
| - "description": "The set of function calls made to service-defined methods.\n\nFunction calls are included in the order in which they are encountered\nduring evaluation, are provided for both mocked and unmocked functions,\nand included on the response regardless of the test `state`.",
|
| - "items": {
|
| - "$ref": "FunctionCall"
|
| - },
|
| - "type": "array"
|
| - },
|
| - "state": {
|
| - "description": "State of the test.",
|
| - "enum": [
|
| - "STATE_UNSPECIFIED",
|
| - "SUCCESS",
|
| - "FAILURE"
|
| - ],
|
| - "enumDescriptions": [
|
| - "Test state is not set.",
|
| - "Test is a success.",
|
| - "Test is a failure."
|
| - ],
|
| - "type": "string"
|
| + "result": {
|
| + "$ref": "Result",
|
| + "description": "The mock result of the function call."
|
| },
|
| - "debugMessages": {
|
| - "description": "Debug messages related to test execution issues encountered during\nevaluation.\n\nDebug messages may be related to too many or too few invocations of\nfunction mocks or to runtime errors that occur during evaluation.\n\nFor example: ```Unable to read variable [name: \"resource\"]```",
|
| + "args": {
|
| + "description": "The list of `Arg` values to match. The order in which the arguments are\nprovided is the order in which they must appear in the function\ninvocation.",
|
| "items": {
|
| - "type": "string"
|
| + "$ref": "Arg"
|
| },
|
| "type": "array"
|
| - },
|
| - "errorPosition": {
|
| - "$ref": "SourcePosition",
|
| - "description": "Position in the `Source` or `Ruleset` where the principle runtime error\noccurs.\n\nEvaluation of an expression may result in an error. Rules are deny by\ndefault, so a `DENY` expectation when an error is generated is valid.\nWhen there is a `DENY` with an error, the `SourcePosition` is returned.\n\nE.g. `error_position { line: 19 column: 37 }`"
|
| }
|
| },
|
| "type": "object"
|
| },
|
| - "Empty": {
|
| - "description": "A generic empty message that you can re-use to avoid defining duplicated\nempty messages in your APIs. A typical example is to use it as the request\nor the response type of an API method. For instance:\n\n service Foo {\n rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);\n }\n\nThe JSON representation for `Empty` is empty JSON object `{}`.",
|
| - "id": "Empty",
|
| - "properties": {},
|
| - "type": "object"
|
| - },
|
| "Source": {
|
| "description": "`Source` is one or more `File` messages comprising a logical set of rules.",
|
| "id": "Source",
|
| @@ -535,6 +479,21 @@
|
| },
|
| "type": "object"
|
| },
|
| + "Result": {
|
| + "description": "Possible result values from the function mock invocation.",
|
| + "id": "Result",
|
| + "properties": {
|
| + "value": {
|
| + "description": "The result is an actual value. The type of the value must match that\nof the type declared by the service.",
|
| + "type": "any"
|
| + },
|
| + "undefined": {
|
| + "$ref": "Empty",
|
| + "description": "The result is undefined, meaning the result could not be computed."
|
| + }
|
| + },
|
| + "type": "object"
|
| + },
|
| "SourcePosition": {
|
| "description": "Position in the `Source` content including its line, column number, and an\nindex of the `File` in the `Source` message. Used for debug purposes.",
|
| "id": "SourcePosition",
|
| @@ -556,13 +515,38 @@
|
| },
|
| "type": "object"
|
| },
|
| - "TestRulesetRequest": {
|
| - "description": "The request for FirebaseRulesService.TestRuleset.",
|
| - "id": "TestRulesetRequest",
|
| + "TestCase": {
|
| + "description": "`TestCase` messages provide the request context and an expectation as to\nwhether the given context will be allowed or denied. Test cases may specify\nthe `request`, `resource`, and `function_mocks` to mock a function call to\na service-provided function.\n\nThe `request` object represents context present at request-time.\n\nThe `resource` is the value of the target resource as it appears in\npersistent storage before the request is executed.",
|
| + "id": "TestCase",
|
| "properties": {
|
| - "source": {
|
| - "$ref": "Source",
|
| - "description": "Optional `Source` to be checked for correctness.\n\nThis field must not be set when the resource name refers to a `Ruleset`."
|
| + "resource": {
|
| + "description": "Optional resource value as it appears in persistent storage before the\nrequest is fulfilled.\n\nThe resource type depends on the `request.path` value.",
|
| + "type": "any"
|
| + },
|
| + "functionMocks": {
|
| + "description": "Optional function mocks for service-defined functions. If not set, any\nservice defined function is expected to return an error, which may or may\nnot influence the test outcome.",
|
| + "items": {
|
| + "$ref": "FunctionMock"
|
| + },
|
| + "type": "array"
|
| + },
|
| + "expectation": {
|
| + "description": "Test expectation.",
|
| + "enum": [
|
| + "EXPECTATION_UNSPECIFIED",
|
| + "ALLOW",
|
| + "DENY"
|
| + ],
|
| + "enumDescriptions": [
|
| + "Unspecified expectation.",
|
| + "Expect an allowed result.",
|
| + "Expect a denied result."
|
| + ],
|
| + "type": "string"
|
| + },
|
| + "request": {
|
| + "description": "Request context.\n\nThe exact format of the request context is service-dependent. See the\nappropriate service documentation for information about the supported\nfields and types on the request. Minimally, all services support the\nfollowing fields and types:\n\nRequest field | Type\n---------------|-----------------\nauth.uid | `string`\nauth.token | `map<string, string>`\nheaders | `map<string, string>`\nmethod | `string`\nparams | `map<string, string>`\npath | `string`\ntime | `google.protobuf.Timestamp`\n\nIf the request value is not well-formed for the service, the request will\nbe rejected as an invalid argument.",
|
| + "type": "any"
|
| }
|
| },
|
| "type": "object"
|
| @@ -598,6 +582,21 @@
|
| },
|
| "type": "object"
|
| },
|
| + "TestRulesetRequest": {
|
| + "description": "The request for FirebaseRulesService.TestRuleset.",
|
| + "id": "TestRulesetRequest",
|
| + "properties": {
|
| + "source": {
|
| + "$ref": "Source",
|
| + "description": "Optional `Source` to be checked for correctness.\n\nThis field must not be set when the resource name refers to a `Ruleset`."
|
| + },
|
| + "testSuite": {
|
| + "$ref": "TestSuite",
|
| + "description": "Inline `TestSuite` to run."
|
| + }
|
| + },
|
| + "type": "object"
|
| + },
|
| "Ruleset": {
|
| "description": "`Ruleset` is an immutable copy of `Source` with a globally unique identifier\nand a creation time.",
|
| "id": "Ruleset",
|
| @@ -618,6 +617,26 @@
|
| },
|
| "type": "object"
|
| },
|
| + "File": {
|
| + "description": "`File` containing source content.",
|
| + "id": "File",
|
| + "properties": {
|
| + "name": {
|
| + "description": "File name.",
|
| + "type": "string"
|
| + },
|
| + "content": {
|
| + "description": "Textual Content.",
|
| + "type": "string"
|
| + },
|
| + "fingerprint": {
|
| + "description": "Fingerprint (e.g. github sha) associated with the `File`.",
|
| + "format": "byte",
|
| + "type": "string"
|
| + }
|
| + },
|
| + "type": "object"
|
| + },
|
| "FunctionCall": {
|
| "description": "Represents a service-defined function call that was invoked during test\nexecution.",
|
| "id": "FunctionCall",
|
| @@ -654,50 +673,137 @@
|
| },
|
| "type": "object"
|
| },
|
| - "File": {
|
| - "description": "`File` containing source content.",
|
| - "id": "File",
|
| + "Release": {
|
| + "description": "`Release` is a named reference to a `Ruleset`. Once a `Release` refers to a\n`Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.",
|
| + "id": "Release",
|
| "properties": {
|
| "name": {
|
| - "description": "File name.",
|
| + "description": "Resource name for the `Release`.\n\n`Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`\nwhich affords developers a great deal of flexibility in mapping the name\nto the style that best fits their existing development practices. For\nexample, a name could refer to an environment, an app, a version, or some\ncombination of three.\n\nIn the table below, for the project name `projects/foo`, the following\nrelative release paths show how flat and structured names might be chosen\nto match a desired development / deployment strategy.\n\nUse Case | Flat Name | Structured Name\n-------------|---------------------|----------------\nEnvironments | releases/qa | releases/qa\nApps | releases/app1_qa | releases/app1/qa\nVersions | releases/app1_v2_qa | releases/app1/v2/qa\n\nThe delimiter between the release name path elements can be almost anything\nand it should work equally well with the release name list filter, but in\nmany ways the structured paths provide a clearer picture of the\nrelationship between `Release` instances.\n\nFormat: `projects/{project_id}/releases/{release_id}`",
|
| "type": "string"
|
| },
|
| - "content": {
|
| - "description": "Textual Content.",
|
| + "rulesetName": {
|
| + "description": "Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must\nexist the `Release` to be created.",
|
| "type": "string"
|
| },
|
| - "fingerprint": {
|
| - "description": "Fingerprint (e.g. github sha) associated with the `File`.",
|
| - "format": "byte",
|
| + "createTime": {
|
| + "description": "Time the release was created.\nOutput only.",
|
| + "format": "google-datetime",
|
| + "type": "string"
|
| + },
|
| + "updateTime": {
|
| + "description": "Time the release was updated.\nOutput only.",
|
| + "format": "google-datetime",
|
| "type": "string"
|
| }
|
| },
|
| "type": "object"
|
| },
|
| - "Release": {
|
| - "description": "`Release` is a named reference to a `Ruleset`. Once a `Release` refers to a\n`Ruleset`, rules-enabled services will be able to enforce the `Ruleset`.",
|
| - "id": "Release",
|
| + "TestRulesetResponse": {
|
| + "description": "The response for FirebaseRulesService.TestRuleset.",
|
| + "id": "TestRulesetResponse",
|
| "properties": {
|
| - "updateTime": {
|
| - "description": "Time the release was updated.\nOutput only.",
|
| - "format": "google-datetime",
|
| - "type": "string"
|
| + "issues": {
|
| + "description": "Syntactic and semantic `Source` issues of varying severity. Issues of\n`ERROR` severity will prevent tests from executing.",
|
| + "items": {
|
| + "$ref": "Issue"
|
| + },
|
| + "type": "array"
|
| },
|
| - "name": {
|
| - "description": "Resource name for the `Release`.\n\n`Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2`\nwhich affords developers a great deal of flexibility in mapping the name\nto the style that best fits their existing development practices. For\nexample, a name could refer to an environment, an app, a version, or some\ncombination of three.\n\nIn the table below, for the project name `projects/foo`, the following\nrelative release paths show how flat and structured names might be chosen\nto match a desired development / deployment strategy.\n\nUse Case | Flat Name | Structured Name\n-------------|---------------------|----------------\nEnvironments | releases/qa | releases/qa\nApps | releases/app1_qa | releases/app1/qa\nVersions | releases/app1_v2_qa | releases/app1/v2/qa\n\nThe delimiter between the release name path elements can be almost anything\nand it should work equally well with the release name list filter, but in\nmany ways the structured paths provide a clearer picture of the\nrelationship between `Release` instances.\n\nFormat: `projects/{project_id}/releases/{release_id}`",
|
| - "type": "string"
|
| + "testResults": {
|
| + "description": "The set of test results given the test cases in the `TestSuite`.\nThe results will appear in the same order as the test cases appear in the\n`TestSuite`.",
|
| + "items": {
|
| + "$ref": "TestResult"
|
| + },
|
| + "type": "array"
|
| + }
|
| + },
|
| + "type": "object"
|
| + },
|
| + "TestResult": {
|
| + "description": "Test result message containing the state of the test as well as a\ndescription and source position for test failures.",
|
| + "id": "TestResult",
|
| + "properties": {
|
| + "errorPosition": {
|
| + "$ref": "SourcePosition",
|
| + "description": "Position in the `Source` or `Ruleset` where the principle runtime error\noccurs.\n\nEvaluation of an expression may result in an error. Rules are deny by\ndefault, so a `DENY` expectation when an error is generated is valid.\nWhen there is a `DENY` with an error, the `SourcePosition` is returned.\n\nE.g. `error_position { line: 19 column: 37 }`"
|
| },
|
| - "rulesetName": {
|
| - "description": "Name of the `Ruleset` referred to by this `Release`. The `Ruleset` must\nexist the `Release` to be created.",
|
| + "functionCalls": {
|
| + "description": "The set of function calls made to service-defined methods.\n\nFunction calls are included in the order in which they are encountered\nduring evaluation, are provided for both mocked and unmocked functions,\nand included on the response regardless of the test `state`.",
|
| + "items": {
|
| + "$ref": "FunctionCall"
|
| + },
|
| + "type": "array"
|
| + },
|
| + "state": {
|
| + "description": "State of the test.",
|
| + "enum": [
|
| + "STATE_UNSPECIFIED",
|
| + "SUCCESS",
|
| + "FAILURE"
|
| + ],
|
| + "enumDescriptions": [
|
| + "Test state is not set.",
|
| + "Test is a success.",
|
| + "Test is a failure."
|
| + ],
|
| "type": "string"
|
| },
|
| - "createTime": {
|
| - "description": "Time the release was created.\nOutput only.",
|
| - "format": "google-datetime",
|
| + "debugMessages": {
|
| + "description": "Debug messages related to test execution issues encountered during\nevaluation.\n\nDebug messages may be related to too many or too few invocations of\nfunction mocks or to runtime errors that occur during evaluation.\n\nFor example: ```Unable to read variable [name: \"resource\"]```",
|
| + "items": {
|
| + "type": "string"
|
| + },
|
| + "type": "array"
|
| + }
|
| + },
|
| + "type": "object"
|
| + },
|
| + "ListRulesetsResponse": {
|
| + "description": "The response for FirebaseRulesService.ListRulesets.",
|
| + "id": "ListRulesetsResponse",
|
| + "properties": {
|
| + "rulesets": {
|
| + "description": "List of `Ruleset` instances.",
|
| + "items": {
|
| + "$ref": "Ruleset"
|
| + },
|
| + "type": "array"
|
| + },
|
| + "nextPageToken": {
|
| + "description": "The pagination token to retrieve the next page of results. If the value is\nempty, no further results remain.",
|
| "type": "string"
|
| }
|
| },
|
| "type": "object"
|
| + },
|
| + "Arg": {
|
| + "description": "Arg matchers for the mock function.",
|
| + "id": "Arg",
|
| + "properties": {
|
| + "exactValue": {
|
| + "description": "Argument exactly matches value provided.",
|
| + "type": "any"
|
| + },
|
| + "anyValue": {
|
| + "$ref": "Empty",
|
| + "description": "Argument matches any value provided."
|
| + }
|
| + },
|
| + "type": "object"
|
| + },
|
| + "TestSuite": {
|
| + "description": "`TestSuite` is a collection of `TestCase` instances that validate the logical\ncorrectness of a `Ruleset`. The `TestSuite` may be referenced in-line within\na `TestRuleset` invocation or as part of a `Release` object as a pre-release\ncheck.",
|
| + "id": "TestSuite",
|
| + "properties": {
|
| + "testCases": {
|
| + "description": "Collection of test cases associated with the `TestSuite`.",
|
| + "items": {
|
| + "$ref": "TestCase"
|
| + },
|
| + "type": "array"
|
| + }
|
| + },
|
| + "type": "object"
|
| }
|
| },
|
| "servicePath": "",
|
|
|
Chromium Code Reviews
Issue 2936613002:
Api-Roll 50: 2017-06-12 (Closed)
