|
598 | 598 | } |
599 | 599 | } |
600 | 600 | }, |
601 | | - "revision": "20190206", |
| 601 | + "revision": "20190307", |
602 | 602 | "rootUrl": "https://accesscontextmanager.googleapis.com/", |
603 | 603 | "schemas": { |
604 | 604 | "AccessLevel": { |
|
715 | 715 | "description": "Whether to negate the Condition. If true, the Condition becomes a NAND over\nits non-empty fields, each field must be false for the Condition overall to\nbe satisfied. Defaults to false.", |
716 | 716 | "type": "boolean" |
717 | 717 | }, |
| 718 | + "regions": { |
| 719 | + "description": "The request must originate from one of the provided countries/regions.\nMust be valid ISO 3166-1 alpha-2 codes.", |
| 720 | + "items": { |
| 721 | + "type": "string" |
| 722 | + }, |
| 723 | + "type": "array" |
| 724 | + }, |
718 | 725 | "requiredAccessLevels": { |
719 | 726 | "description": "A list of other access levels defined in the same `Policy`, referenced by\nresource name. Referencing an `AccessLevel` which does not exist is an\nerror. All access levels listed must be granted for the Condition\nto be true. Example:\n\"`accessPolicies/MY_POLICY/accessLevels/LEVEL_NAME\"`", |
720 | 727 | "items": { |
|
774 | 781 | }, |
775 | 782 | "type": "array" |
776 | 783 | }, |
| 784 | + "requireAdminApproval": { |
| 785 | + "description": "Whether the device needs to be approved by the customer admin.", |
| 786 | + "type": "boolean" |
| 787 | + }, |
| 788 | + "requireCorpOwned": { |
| 789 | + "description": "Whether the device needs to be corp owned.", |
| 790 | + "type": "boolean" |
| 791 | + }, |
777 | 792 | "requireScreenlock": { |
778 | 793 | "description": "Whether or not screenlock is required for the DevicePolicy to be true.\nDefaults to `false`.", |
779 | 794 | "type": "boolean" |
|
885 | 900 | "DESKTOP_MAC", |
886 | 901 | "DESKTOP_WINDOWS", |
887 | 902 | "DESKTOP_LINUX", |
888 | | - "DESKTOP_CHROME_OS", |
889 | | - "ANDROID", |
890 | | - "IOS" |
| 903 | + "DESKTOP_CHROME_OS" |
891 | 904 | ], |
892 | 905 | "enumDescriptions": [ |
893 | 906 | "The operating system of the device is not specified or not known.", |
894 | 907 | "A desktop Mac operating system.", |
895 | 908 | "A desktop Windows operating system.", |
896 | 909 | "A desktop Linux operating system.", |
897 | | - "A desktop ChromeOS operating system.", |
898 | | - "An Android operating system.", |
899 | | - "An iOS operating system." |
| 910 | + "A desktop ChromeOS operating system." |
900 | 911 | ], |
901 | 912 | "type": "string" |
| 913 | + }, |
| 914 | + "requireVerifiedChromeOs": { |
| 915 | + "description": "Only allows requests from devices with a verified Chrome OS.\nVerifications includes requirements that the device is enterprise-managed,\nconformant to Dasher domain policies, and the caller has permission to call\nthe API targeted by the request.", |
| 916 | + "type": "boolean" |
902 | 917 | } |
903 | 918 | }, |
904 | 919 | "type": "object" |
|
967 | 982 | "type": "array" |
968 | 983 | }, |
969 | 984 | "restrictedServices": { |
970 | | - "description": "GCP services that are subject to the Service Perimeter restrictions. May\ncontain a list of services or a single wildcard \"*\". For example, if\n`storage.googleapis.com` is specified, access to the storage buckets\ninside the perimeter must meet the perimeter's access restrictions.\n\nWildcard means that unless explicitly specified by \"unrestricted_services\"\nlist, any service is treated as restricted. One of the fields\n\"restricted_services\", \"unrestricted_services\" must contain a wildcard \"*\",\notherwise the Service Perimeter specification is invalid. It also means\nthat both field being empty is invalid as well. \"restricted_services\" can\nbe empty if and only if \"unrestricted_services\" list contains a \"*\"\nwildcard.", |
| 985 | + "description": "GCP services that are subject to the Service Perimeter restrictions. Must\ncontain a list of services. For example, if\n`storage.googleapis.com` is specified, access to the storage buckets\ninside the perimeter must meet the perimeter's access restrictions.", |
971 | 986 | "items": { |
972 | 987 | "type": "string" |
973 | 988 | }, |
974 | 989 | "type": "array" |
975 | 990 | }, |
976 | 991 | "unrestrictedServices": { |
977 | | - "description": "GCP services that are not subject to the Service Perimeter restrictions.\nMay contain a list of services or a single wildcard \"*\". For example, if\n`logging.googleapis.com` is unrestricted, users can access logs inside the\nperimeter as if the perimeter doesn't exist, and it also means VMs inside\nthe perimeter can access logs outside the perimeter.\n\nThe wildcard means that unless explicitly specified by\n\"restricted_services\" list, any service is treated as unrestricted. One of\nthe fields \"restricted_services\", \"unrestricted_services\" must contain a\nwildcard \"*\", otherwise the Service Perimeter specification is invalid. It\nalso means that both field being empty is invalid as well.\n\"unrestricted_services\" can be empty if and only if \"restricted_services\"\nlist contains a \"*\" wildcard.", |
| 992 | + "description": "GCP services that are not subject to the Service Perimeter\nrestrictions. Deprecated. Must be set to a single wildcard \"*\".\n\nThe wildcard means that unless explicitly specified by\n\"restricted_services\" list, any service is treated as unrestricted.", |
978 | 993 | "items": { |
979 | 994 | "type": "string" |
980 | 995 | }, |
|
984 | 999 | "type": "object" |
985 | 1000 | }, |
986 | 1001 | "Status": { |
987 | | - "description": "The `Status` type defines a logical error model that is suitable for different\nprogramming environments, including REST APIs and RPC APIs. It is used by\n[gRPC](https://github.com/grpc). The error model is designed to be:\n\n- Simple to use and understand for most users\n- Flexible enough to meet unexpected needs\n\n# Overview\n\nThe `Status` message contains three pieces of data: error code, error message,\nand error details. The error code should be an enum value of\ngoogle.rpc.Code, but it may accept additional error codes if needed. The\nerror message should be a developer-facing English message that helps\ndevelopers *understand* and *resolve* the error. If a localized user-facing\nerror message is needed, put the localized message in the error details or\nlocalize it in the client. The optional error details may contain arbitrary\ninformation about the error. There is a predefined set of error detail types\nin the package `google.rpc` that can be used for common error conditions.\n\n# Language mapping\n\nThe `Status` message is the logical representation of the error model, but it\nis not necessarily the actual wire format. When the `Status` message is\nexposed in different client libraries and different wire protocols, it can be\nmapped differently. For example, it will likely be mapped to some exceptions\nin Java, but more likely mapped to some error codes in C.\n\n# Other uses\n\nThe error model and the `Status` message can be used in a variety of\nenvironments, either with or without APIs, to provide a\nconsistent developer experience across different environments.\n\nExample uses of this error model include:\n\n- Partial errors. If a service needs to return partial errors to the client,\n it may embed the `Status` in the normal response to indicate the partial\n errors.\n\n- Workflow errors. A typical workflow has multiple steps. Each step may\n have a `Status` message for error reporting.\n\n- Batch operations. If a client uses batch request and batch response, the\n `Status` message should be used directly inside batch response, one for\n each error sub-response.\n\n- Asynchronous operations. If an API call embeds asynchronous operation\n results in its response, the status of those operations should be\n represented directly using the `Status` message.\n\n- Logging. If some API errors are stored in logs, the message `Status` could\n be used directly after any stripping needed for security/privacy reasons.", |
| 1002 | + "description": "The `Status` type defines a logical error model that is suitable for\ndifferent programming environments, including REST APIs and RPC APIs. It is\nused by [gRPC](https://github.com/grpc). The error model is designed to be:\n\n- Simple to use and understand for most users\n- Flexible enough to meet unexpected needs\n\n# Overview\n\nThe `Status` message contains three pieces of data: error code, error\nmessage, and error details. The error code should be an enum value of\ngoogle.rpc.Code, but it may accept additional error codes if needed. The\nerror message should be a developer-facing English message that helps\ndevelopers *understand* and *resolve* the error. If a localized user-facing\nerror message is needed, put the localized message in the error details or\nlocalize it in the client. The optional error details may contain arbitrary\ninformation about the error. There is a predefined set of error detail types\nin the package `google.rpc` that can be used for common error conditions.\n\n# Language mapping\n\nThe `Status` message is the logical representation of the error model, but it\nis not necessarily the actual wire format. When the `Status` message is\nexposed in different client libraries and different wire protocols, it can be\nmapped differently. For example, it will likely be mapped to some exceptions\nin Java, but more likely mapped to some error codes in C.\n\n# Other uses\n\nThe error model and the `Status` message can be used in a variety of\nenvironments, either with or without APIs, to provide a\nconsistent developer experience across different environments.\n\nExample uses of this error model include:\n\n- Partial errors. If a service needs to return partial errors to the client,\n it may embed the `Status` in the normal response to indicate the partial\n errors.\n\n- Workflow errors. A typical workflow has multiple steps. Each step may\n have a `Status` message for error reporting.\n\n- Batch operations. If a client uses batch request and batch response, the\n `Status` message should be used directly inside batch response, one for\n each error sub-response.\n\n- Asynchronous operations. If an API call embeds asynchronous operation\n results in its response, the status of those operations should be\n represented directly using the `Status` message.\n\n- Logging. If some API errors are stored in logs, the message `Status` could\n be used directly after any stripping needed for security/privacy reasons.", |
988 | 1003 | "id": "Status", |
989 | 1004 | "properties": { |
990 | 1005 | "code": { |
|
0 commit comments