google-api-client 0.19.8 → 0.20.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (355) hide show
  1. checksums.yaml +4 -4
  2. data/.travis.yml +7 -4
  3. data/CHANGELOG.md +106 -0
  4. data/MIGRATING.md +3 -3
  5. data/README.md +6 -9
  6. data/generated/google/apis/adexchangebuyer2_v2beta1.rb +1 -1
  7. data/generated/google/apis/adexchangebuyer2_v2beta1/classes.rb +1 -7
  8. data/generated/google/apis/adexchangebuyer2_v2beta1/representations.rb +0 -1
  9. data/generated/google/apis/adexchangebuyer2_v2beta1/service.rb +2 -8
  10. data/generated/google/apis/adexchangebuyer_v1_4.rb +1 -1
  11. data/generated/google/apis/adexchangebuyer_v1_4/classes.rb +84 -9
  12. data/generated/google/apis/adexchangebuyer_v1_4/representations.rb +33 -0
  13. data/generated/google/apis/admin_directory_v1.rb +1 -1
  14. data/generated/google/apis/admin_directory_v1/classes.rb +11 -10
  15. data/generated/google/apis/admin_directory_v1/service.rb +21 -7
  16. data/generated/google/apis/analytics_v3.rb +1 -1
  17. data/generated/google/apis/analytics_v3/service.rb +1 -1
  18. data/generated/google/apis/androiddeviceprovisioning_v1.rb +1 -1
  19. data/generated/google/apis/androiddeviceprovisioning_v1/classes.rb +52 -35
  20. data/generated/google/apis/androiddeviceprovisioning_v1/service.rb +33 -20
  21. data/generated/google/apis/androidenterprise_v1.rb +1 -1
  22. data/generated/google/apis/androidenterprise_v1/classes.rb +44 -0
  23. data/generated/google/apis/androidenterprise_v1/representations.rb +17 -0
  24. data/generated/google/apis/androidmanagement_v1.rb +1 -1
  25. data/generated/google/apis/androidmanagement_v1/classes.rb +66 -0
  26. data/generated/google/apis/androidmanagement_v1/representations.rb +10 -0
  27. data/generated/google/apis/androidpublisher_v2.rb +1 -1
  28. data/generated/google/apis/androidpublisher_v2/classes.rb +37 -72
  29. data/generated/google/apis/androidpublisher_v2/representations.rb +5 -34
  30. data/generated/google/apis/androidpublisher_v2/service.rb +6 -52
  31. data/generated/google/apis/appengine_v1.rb +2 -2
  32. data/generated/google/apis/appengine_v1/classes.rb +82 -7
  33. data/generated/google/apis/appengine_v1/representations.rb +32 -0
  34. data/generated/google/apis/appengine_v1/service.rb +2 -2
  35. data/generated/google/apis/appengine_v1alpha.rb +2 -2
  36. data/generated/google/apis/appengine_v1alpha/classes.rb +35 -0
  37. data/generated/google/apis/appengine_v1alpha/representations.rb +16 -0
  38. data/generated/google/apis/appengine_v1alpha/service.rb +2 -2
  39. data/generated/google/apis/appengine_v1beta.rb +2 -2
  40. data/generated/google/apis/appengine_v1beta/classes.rb +51 -7
  41. data/generated/google/apis/appengine_v1beta/representations.rb +17 -0
  42. data/generated/google/apis/appengine_v1beta/service.rb +2 -2
  43. data/generated/google/apis/appengine_v1beta4.rb +2 -2
  44. data/generated/google/apis/appengine_v1beta4/classes.rb +50 -6
  45. data/generated/google/apis/appengine_v1beta4/representations.rb +17 -0
  46. data/generated/google/apis/appengine_v1beta4/service.rb +2 -2
  47. data/generated/google/apis/appengine_v1beta5.rb +2 -2
  48. data/generated/google/apis/appengine_v1beta5/classes.rb +50 -6
  49. data/generated/google/apis/appengine_v1beta5/representations.rb +17 -0
  50. data/generated/google/apis/appengine_v1beta5/service.rb +2 -2
  51. data/generated/google/apis/bigquery_v2.rb +1 -1
  52. data/generated/google/apis/bigquery_v2/classes.rb +19 -11
  53. data/generated/google/apis/bigquery_v2/representations.rb +4 -3
  54. data/generated/google/apis/bigquery_v2/service.rb +9 -1
  55. data/generated/google/apis/bigquerydatatransfer_v1.rb +1 -1
  56. data/generated/google/apis/bigquerydatatransfer_v1/classes.rb +9 -6
  57. data/generated/google/apis/bigquerydatatransfer_v1/representations.rb +1 -0
  58. data/generated/google/apis/bigquerydatatransfer_v1/service.rb +1 -1
  59. data/generated/google/apis/calendar_v3.rb +1 -1
  60. data/generated/google/apis/calendar_v3/classes.rb +3 -1
  61. data/generated/google/apis/{firebaseremoteconfig_v1.rb → chat_v1.rb} +8 -9
  62. data/generated/google/apis/chat_v1/classes.rb +890 -0
  63. data/generated/google/apis/chat_v1/representations.rb +445 -0
  64. data/generated/google/apis/chat_v1/service.rb +344 -0
  65. data/generated/google/apis/cloudbilling_v1.rb +2 -2
  66. data/generated/google/apis/cloudbilling_v1/classes.rb +341 -5
  67. data/generated/google/apis/cloudbilling_v1/representations.rb +103 -0
  68. data/generated/google/apis/cloudbilling_v1/service.rb +217 -10
  69. data/generated/google/apis/cloudbuild_v1.rb +2 -2
  70. data/generated/google/apis/cloudbuild_v1/classes.rb +180 -84
  71. data/generated/google/apis/cloudbuild_v1/representations.rb +35 -0
  72. data/generated/google/apis/cloudbuild_v1/service.rb +25 -25
  73. data/generated/google/apis/cloudiot_v1.rb +2 -2
  74. data/generated/google/apis/cloudiot_v1/classes.rb +13 -142
  75. data/generated/google/apis/cloudiot_v1/representations.rb +0 -32
  76. data/generated/google/apis/cloudiot_v1/service.rb +2 -2
  77. data/generated/google/apis/cloudkms_v1.rb +1 -1
  78. data/generated/google/apis/cloudkms_v1/classes.rb +7 -1
  79. data/generated/google/apis/cloudkms_v1/representations.rb +1 -0
  80. data/generated/google/apis/cloudkms_v1/service.rb +1 -1
  81. data/generated/google/apis/cloudresourcemanager_v1.rb +2 -2
  82. data/generated/google/apis/cloudresourcemanager_v1/classes.rb +2 -2
  83. data/generated/google/apis/cloudresourcemanager_v1/service.rb +4 -5
  84. data/generated/google/apis/cloudresourcemanager_v1beta1.rb +2 -2
  85. data/generated/google/apis/cloudresourcemanager_v1beta1/classes.rb +1 -1
  86. data/generated/google/apis/cloudresourcemanager_v1beta1/service.rb +6 -6
  87. data/generated/google/apis/{clouduseraccounts_beta.rb → cloudresourcemanager_v2.rb} +10 -16
  88. data/generated/google/apis/cloudresourcemanager_v2/classes.rb +821 -0
  89. data/generated/google/apis/cloudresourcemanager_v2/representations.rb +304 -0
  90. data/generated/google/apis/cloudresourcemanager_v2/service.rb +534 -0
  91. data/generated/google/apis/cloudresourcemanager_v2beta1.rb +2 -2
  92. data/generated/google/apis/cloudresourcemanager_v2beta1/service.rb +1 -1
  93. data/generated/google/apis/cloudtasks_v2beta2.rb +1 -1
  94. data/generated/google/apis/cloudtasks_v2beta2/classes.rb +7 -0
  95. data/generated/google/apis/cloudtasks_v2beta2/representations.rb +1 -0
  96. data/generated/google/apis/cloudtrace_v1.rb +1 -1
  97. data/generated/google/apis/cloudtrace_v1/classes.rb +2 -0
  98. data/generated/google/apis/compute_alpha.rb +1 -1
  99. data/generated/google/apis/compute_alpha/classes.rb +216 -120
  100. data/generated/google/apis/compute_alpha/representations.rb +25 -1
  101. data/generated/google/apis/compute_alpha/service.rb +1354 -1621
  102. data/generated/google/apis/compute_beta.rb +1 -1
  103. data/generated/google/apis/compute_beta/classes.rb +548 -85
  104. data/generated/google/apis/compute_beta/representations.rb +159 -0
  105. data/generated/google/apis/compute_beta/service.rb +1971 -1460
  106. data/generated/google/apis/compute_v1.rb +1 -1
  107. data/generated/google/apis/compute_v1/classes.rb +206 -70
  108. data/generated/google/apis/compute_v1/representations.rb +32 -0
  109. data/generated/google/apis/compute_v1/service.rb +1184 -1278
  110. data/generated/google/apis/container_v1.rb +1 -1
  111. data/generated/google/apis/container_v1/classes.rb +742 -9
  112. data/generated/google/apis/container_v1/representations.rb +90 -0
  113. data/generated/google/apis/container_v1/service.rb +1380 -100
  114. data/generated/google/apis/container_v1beta1.rb +1 -1
  115. data/generated/google/apis/container_v1beta1/classes.rb +191 -138
  116. data/generated/google/apis/container_v1beta1/representations.rb +2 -0
  117. data/generated/google/apis/container_v1beta1/service.rb +236 -231
  118. data/generated/google/apis/content_v2.rb +1 -1
  119. data/generated/google/apis/content_v2/classes.rb +2690 -1540
  120. data/generated/google/apis/content_v2/representations.rb +491 -0
  121. data/generated/google/apis/content_v2/service.rb +684 -0
  122. data/generated/google/apis/content_v2sandbox.rb +1 -1
  123. data/generated/google/apis/content_v2sandbox/classes.rb +2 -1
  124. data/generated/google/apis/dataflow_v1b3.rb +2 -2
  125. data/generated/google/apis/dataflow_v1b3/classes.rb +95 -0
  126. data/generated/google/apis/dataflow_v1b3/representations.rb +36 -0
  127. data/generated/google/apis/dataflow_v1b3/service.rb +1 -1
  128. data/generated/google/apis/dataproc_v1.rb +1 -1
  129. data/generated/google/apis/dataproc_v1/classes.rb +56 -45
  130. data/generated/google/apis/dataproc_v1/representations.rb +1 -0
  131. data/generated/google/apis/dataproc_v1/service.rb +30 -3
  132. data/generated/google/apis/dataproc_v1beta2.rb +1 -1
  133. data/generated/google/apis/dataproc_v1beta2/classes.rb +77 -53
  134. data/generated/google/apis/dataproc_v1beta2/representations.rb +2 -0
  135. data/generated/google/apis/dataproc_v1beta2/service.rb +484 -18
  136. data/generated/google/apis/datastore_v1.rb +1 -1
  137. data/generated/google/apis/datastore_v1/classes.rb +372 -0
  138. data/generated/google/apis/datastore_v1/representations.rb +132 -0
  139. data/generated/google/apis/datastore_v1/service.rb +77 -0
  140. data/generated/google/apis/datastore_v1beta1.rb +1 -1
  141. data/generated/google/apis/datastore_v1beta1/classes.rb +255 -0
  142. data/generated/google/apis/datastore_v1beta1/representations.rb +100 -0
  143. data/generated/google/apis/datastore_v1beta3.rb +1 -1
  144. data/generated/google/apis/datastore_v1beta3/classes.rb +255 -0
  145. data/generated/google/apis/datastore_v1beta3/representations.rb +100 -0
  146. data/generated/google/apis/deploymentmanager_alpha.rb +1 -1
  147. data/generated/google/apis/deploymentmanager_alpha/classes.rb +6 -1
  148. data/generated/google/apis/deploymentmanager_alpha/service.rb +121 -145
  149. data/generated/google/apis/deploymentmanager_v2.rb +1 -1
  150. data/generated/google/apis/deploymentmanager_v2/service.rb +79 -91
  151. data/generated/google/apis/deploymentmanager_v2beta.rb +1 -1
  152. data/generated/google/apis/deploymentmanager_v2beta/classes.rb +6 -1
  153. data/generated/google/apis/deploymentmanager_v2beta/service.rb +121 -145
  154. data/generated/google/apis/dialogflow_v2.rb +35 -0
  155. data/generated/google/apis/dialogflow_v2/classes.rb +3994 -0
  156. data/generated/google/apis/dialogflow_v2/representations.rb +1670 -0
  157. data/generated/google/apis/dialogflow_v2/service.rb +1397 -0
  158. data/generated/google/apis/dialogflow_v2beta1.rb +1 -1
  159. data/generated/google/apis/dialogflow_v2beta1/classes.rb +39 -11
  160. data/generated/google/apis/dialogflow_v2beta1/representations.rb +1 -0
  161. data/generated/google/apis/dialogflow_v2beta1/service.rb +559 -16
  162. data/generated/google/apis/dlp_v2.rb +36 -0
  163. data/generated/google/apis/dlp_v2/classes.rb +6431 -0
  164. data/generated/google/apis/dlp_v2/representations.rb +3116 -0
  165. data/generated/google/apis/dlp_v2/service.rb +1300 -0
  166. data/generated/google/apis/dlp_v2beta1.rb +4 -4
  167. data/generated/google/apis/dlp_v2beta1/classes.rb +38 -0
  168. data/generated/google/apis/dlp_v2beta1/representations.rb +17 -0
  169. data/generated/google/apis/dlp_v2beta1/service.rb +3 -3
  170. data/generated/google/apis/dlp_v2beta2.rb +4 -4
  171. data/generated/google/apis/dlp_v2beta2/classes.rb +229 -1
  172. data/generated/google/apis/dlp_v2beta2/representations.rb +91 -0
  173. data/generated/google/apis/dlp_v2beta2/service.rb +3 -3
  174. data/generated/google/apis/dns_v1.rb +1 -1
  175. data/generated/google/apis/dns_v1/classes.rb +496 -0
  176. data/generated/google/apis/dns_v1/representations.rb +188 -0
  177. data/generated/google/apis/dns_v1/service.rb +319 -6
  178. data/generated/google/apis/dns_v1beta2.rb +1 -1
  179. data/generated/google/apis/dns_v1beta2/classes.rb +0 -19
  180. data/generated/google/apis/dns_v1beta2/representations.rb +0 -14
  181. data/generated/google/apis/dns_v1beta2/service.rb +2 -4
  182. data/generated/google/apis/dns_v2beta1.rb +1 -1
  183. data/generated/google/apis/dns_v2beta1/classes.rb +6 -19
  184. data/generated/google/apis/dns_v2beta1/representations.rb +1 -14
  185. data/generated/google/apis/dns_v2beta1/service.rb +2 -4
  186. data/generated/google/apis/doubleclicksearch_v2.rb +1 -1
  187. data/generated/google/apis/doubleclicksearch_v2/classes.rb +4 -0
  188. data/generated/google/apis/firebasedynamiclinks_v1.rb +1 -1
  189. data/generated/google/apis/firebasedynamiclinks_v1/classes.rb +2 -2
  190. data/generated/google/apis/firestore_v1beta1.rb +1 -1
  191. data/generated/google/apis/firestore_v1beta1/classes.rb +1 -1
  192. data/generated/google/apis/genomics_v1.rb +1 -1
  193. data/generated/google/apis/genomics_v1/classes.rb +271 -1
  194. data/generated/google/apis/genomics_v1/representations.rb +140 -0
  195. data/generated/google/apis/genomics_v1/service.rb +9 -1
  196. data/generated/google/apis/genomics_v1alpha2.rb +1 -1
  197. data/generated/google/apis/genomics_v1alpha2/classes.rb +271 -1
  198. data/generated/google/apis/genomics_v1alpha2/representations.rb +140 -0
  199. data/generated/google/apis/genomics_v1alpha2/service.rb +9 -1
  200. data/generated/google/apis/genomics_v2alpha1.rb +37 -0
  201. data/generated/google/apis/genomics_v2alpha1/classes.rb +1306 -0
  202. data/generated/google/apis/genomics_v2alpha1/representations.rb +535 -0
  203. data/generated/google/apis/genomics_v2alpha1/service.rb +261 -0
  204. data/generated/google/apis/gmail_v1.rb +1 -1
  205. data/generated/google/apis/gmail_v1/classes.rb +2 -1
  206. data/generated/google/apis/iam_v1.rb +1 -1
  207. data/generated/google/apis/iam_v1/classes.rb +1 -1
  208. data/generated/google/apis/language_v1.rb +2 -2
  209. data/generated/google/apis/language_v1/classes.rb +2 -1
  210. data/generated/google/apis/language_v1/service.rb +1 -1
  211. data/generated/google/apis/language_v1beta1.rb +2 -2
  212. data/generated/google/apis/language_v1beta1/service.rb +1 -1
  213. data/generated/google/apis/language_v1beta2.rb +2 -2
  214. data/generated/google/apis/language_v1beta2/classes.rb +2 -1
  215. data/generated/google/apis/language_v1beta2/service.rb +1 -1
  216. data/generated/google/apis/logging_v2.rb +1 -1
  217. data/generated/google/apis/logging_v2beta1.rb +1 -1
  218. data/generated/google/apis/manufacturers_v1.rb +1 -1
  219. data/generated/google/apis/manufacturers_v1/service.rb +14 -11
  220. data/generated/google/apis/ml_v1.rb +2 -2
  221. data/generated/google/apis/ml_v1/classes.rb +180 -5
  222. data/generated/google/apis/ml_v1/representations.rb +49 -0
  223. data/generated/google/apis/ml_v1/service.rb +1 -1
  224. data/generated/google/apis/monitoring_v3.rb +1 -1
  225. data/generated/google/apis/monitoring_v3/classes.rb +797 -2
  226. data/generated/google/apis/monitoring_v3/representations.rb +279 -0
  227. data/generated/google/apis/monitoring_v3/service.rb +612 -0
  228. data/generated/google/apis/oslogin_v1.rb +2 -2
  229. data/generated/google/apis/oslogin_v1/service.rb +1 -1
  230. data/generated/google/apis/oslogin_v1alpha.rb +2 -2
  231. data/generated/google/apis/oslogin_v1alpha/service.rb +1 -1
  232. data/generated/google/apis/oslogin_v1beta.rb +2 -2
  233. data/generated/google/apis/oslogin_v1beta/service.rb +1 -1
  234. data/generated/google/apis/pagespeedonline_v4.rb +32 -0
  235. data/generated/google/apis/pagespeedonline_v4/classes.rb +795 -0
  236. data/generated/google/apis/pagespeedonline_v4/representations.rb +335 -0
  237. data/generated/google/apis/pagespeedonline_v4/service.rb +129 -0
  238. data/generated/google/apis/people_v1.rb +2 -2
  239. data/generated/google/apis/people_v1/classes.rb +5 -2
  240. data/generated/google/apis/people_v1/service.rb +9 -7
  241. data/generated/google/apis/poly_v1.rb +1 -1
  242. data/generated/google/apis/poly_v1/classes.rb +153 -0
  243. data/generated/google/apis/poly_v1/representations.rb +67 -0
  244. data/generated/google/apis/proximitybeacon_v1beta1.rb +2 -2
  245. data/generated/google/apis/proximitybeacon_v1beta1/service.rb +1 -1
  246. data/generated/google/apis/pubsub_v1.rb +1 -1
  247. data/generated/google/apis/pubsub_v1/classes.rb +3 -0
  248. data/generated/google/apis/pubsub_v1/service.rb +7 -0
  249. data/generated/google/apis/script_v1.rb +2 -2
  250. data/generated/google/apis/script_v1/service.rb +1 -1
  251. data/generated/google/apis/serviceconsumermanagement_v1.rb +1 -1
  252. data/generated/google/apis/serviceconsumermanagement_v1/classes.rb +21 -126
  253. data/generated/google/apis/serviceconsumermanagement_v1/representations.rb +0 -30
  254. data/generated/google/apis/serviceconsumermanagement_v1/service.rb +14 -13
  255. data/generated/google/apis/servicecontrol_v1.rb +1 -1
  256. data/generated/google/apis/servicecontrol_v1/classes.rb +2 -1
  257. data/generated/google/apis/servicecontrol_v1/service.rb +9 -6
  258. data/generated/google/apis/servicemanagement_v1.rb +1 -1
  259. data/generated/google/apis/servicemanagement_v1/classes.rb +44 -157
  260. data/generated/google/apis/servicemanagement_v1/representations.rb +2 -48
  261. data/generated/google/apis/servicemanagement_v1/service.rb +9 -0
  262. data/generated/google/apis/{serviceusage_v1.rb → serviceusage_v1beta1.rb} +6 -6
  263. data/generated/google/apis/{serviceusage_v1 → serviceusage_v1beta1}/classes.rb +290 -325
  264. data/generated/google/apis/{serviceusage_v1 → serviceusage_v1beta1}/representations.rb +105 -163
  265. data/generated/google/apis/{serviceusage_v1 → serviceusage_v1beta1}/service.rb +105 -163
  266. data/generated/google/apis/serviceuser_v1.rb +2 -2
  267. data/generated/google/apis/serviceuser_v1/classes.rb +44 -101
  268. data/generated/google/apis/serviceuser_v1/representations.rb +2 -30
  269. data/generated/google/apis/serviceuser_v1/service.rb +1 -1
  270. data/generated/google/apis/sheets_v4.rb +1 -1
  271. data/generated/google/apis/sheets_v4/classes.rb +643 -10
  272. data/generated/google/apis/sheets_v4/representations.rb +53 -0
  273. data/generated/google/apis/slides_v1.rb +1 -1
  274. data/generated/google/apis/slides_v1/classes.rb +92 -9
  275. data/generated/google/apis/slides_v1/representations.rb +21 -0
  276. data/generated/google/apis/slides_v1/service.rb +3 -2
  277. data/generated/google/apis/sourcerepo_v1.rb +1 -1
  278. data/generated/google/apis/sourcerepo_v1/classes.rb +4 -73
  279. data/generated/google/apis/sourcerepo_v1/representations.rb +0 -20
  280. data/generated/google/apis/spanner_v1.rb +1 -1
  281. data/generated/google/apis/spanner_v1/classes.rb +238 -2
  282. data/generated/google/apis/spanner_v1/representations.rb +86 -0
  283. data/generated/google/apis/spanner_v1/service.rb +80 -0
  284. data/generated/google/apis/speech_v1.rb +2 -2
  285. data/generated/google/apis/speech_v1/classes.rb +14 -19
  286. data/generated/google/apis/speech_v1/representations.rb +0 -1
  287. data/generated/google/apis/speech_v1/service.rb +1 -1
  288. data/generated/google/apis/speech_v1beta1.rb +2 -2
  289. data/generated/google/apis/speech_v1beta1/service.rb +1 -1
  290. data/generated/google/apis/sqladmin_v1beta4.rb +1 -1
  291. data/generated/google/apis/sqladmin_v1beta4/classes.rb +15 -6
  292. data/generated/google/apis/sqladmin_v1beta4/representations.rb +1 -0
  293. data/generated/google/apis/storage_v1.rb +1 -1
  294. data/generated/google/apis/storage_v1/service.rb +3 -6
  295. data/generated/google/apis/storagetransfer_v1.rb +2 -2
  296. data/generated/google/apis/storagetransfer_v1/service.rb +1 -1
  297. data/generated/google/apis/testing_v1.rb +1 -1
  298. data/generated/google/apis/testing_v1/classes.rb +107 -2
  299. data/generated/google/apis/testing_v1/representations.rb +38 -0
  300. data/generated/google/apis/texttospeech_v1beta1.rb +34 -0
  301. data/generated/google/apis/texttospeech_v1beta1/classes.rb +278 -0
  302. data/generated/google/apis/texttospeech_v1beta1/representations.rb +133 -0
  303. data/generated/google/apis/texttospeech_v1beta1/service.rb +128 -0
  304. data/generated/google/apis/toolresults_v1beta3.rb +1 -1
  305. data/generated/google/apis/toolresults_v1beta3/classes.rb +30 -16
  306. data/generated/google/apis/tpu_v1alpha1.rb +1 -1
  307. data/generated/google/apis/tpu_v1alpha1/classes.rb +57 -0
  308. data/generated/google/apis/tpu_v1alpha1/representations.rb +30 -0
  309. data/generated/google/apis/tpu_v1alpha1/service.rb +73 -1
  310. data/generated/google/apis/vault_v1.rb +1 -1
  311. data/generated/google/apis/vault_v1/classes.rb +29 -3
  312. data/generated/google/apis/vault_v1/representations.rb +15 -0
  313. data/generated/google/apis/vault_v1/service.rb +8 -2
  314. data/generated/google/apis/videointelligence_v1beta1.rb +1 -1
  315. data/generated/google/apis/videointelligence_v1beta1/classes.rb +650 -0
  316. data/generated/google/apis/videointelligence_v1beta1/representations.rb +315 -0
  317. data/generated/google/apis/vision_v1.rb +2 -2
  318. data/generated/google/apis/vision_v1/classes.rb +290 -2
  319. data/generated/google/apis/vision_v1/representations.rb +128 -0
  320. data/generated/google/apis/vision_v1/service.rb +187 -1
  321. data/generated/google/apis/vision_v1p1beta1.rb +2 -2
  322. data/generated/google/apis/vision_v1p1beta1/classes.rb +136 -2
  323. data/generated/google/apis/vision_v1p1beta1/representations.rb +71 -0
  324. data/generated/google/apis/vision_v1p1beta1/service.rb +1 -1
  325. data/generated/google/apis/vision_v1p2beta1.rb +39 -0
  326. data/generated/google/apis/vision_v1p2beta1/classes.rb +2172 -0
  327. data/generated/google/apis/vision_v1p2beta1/representations.rb +895 -0
  328. data/generated/google/apis/vision_v1p2beta1/service.rb +126 -0
  329. data/generated/google/apis/youtube_partner_v1.rb +1 -1
  330. data/generated/google/apis/youtube_v3.rb +1 -1
  331. data/generated/google/apis/youtube_v3/classes.rb +12 -0
  332. data/generated/google/apis/youtube_v3/representations.rb +2 -0
  333. data/generated/google/apis/youtubereporting_v1.rb +1 -1
  334. data/lib/google/apis/core/json_representation.rb +1 -1
  335. data/lib/google/apis/version.rb +3 -3
  336. data/samples/web/Gemfile +3 -0
  337. metadata +38 -26
  338. data/generated/google/apis/clouduseraccounts_alpha.rb +0 -44
  339. data/generated/google/apis/clouduseraccounts_alpha/classes.rb +0 -1188
  340. data/generated/google/apis/clouduseraccounts_alpha/representations.rb +0 -494
  341. data/generated/google/apis/clouduseraccounts_alpha/service.rb +0 -1152
  342. data/generated/google/apis/clouduseraccounts_beta/classes.rb +0 -845
  343. data/generated/google/apis/clouduseraccounts_beta/representations.rb +0 -352
  344. data/generated/google/apis/clouduseraccounts_beta/service.rb +0 -908
  345. data/generated/google/apis/clouduseraccounts_vm_alpha.rb +0 -44
  346. data/generated/google/apis/clouduseraccounts_vm_alpha/classes.rb +0 -1188
  347. data/generated/google/apis/clouduseraccounts_vm_alpha/representations.rb +0 -494
  348. data/generated/google/apis/clouduseraccounts_vm_alpha/service.rb +0 -1152
  349. data/generated/google/apis/clouduseraccounts_vm_beta.rb +0 -44
  350. data/generated/google/apis/clouduseraccounts_vm_beta/classes.rb +0 -845
  351. data/generated/google/apis/clouduseraccounts_vm_beta/representations.rb +0 -352
  352. data/generated/google/apis/clouduseraccounts_vm_beta/service.rb +0 -908
  353. data/generated/google/apis/firebaseremoteconfig_v1/classes.rb +0 -200
  354. data/generated/google/apis/firebaseremoteconfig_v1/representations.rb +0 -89
  355. data/generated/google/apis/firebaseremoteconfig_v1/service.rb +0 -153
@@ -1840,6 +1840,12 @@ module Google
1840
1840
  include Google::Apis::Core::JsonObjectSupport
1841
1841
  end
1842
1842
 
1843
+ class RouterAdvertisedIpRange
1844
+ class Representation < Google::Apis::Core::JsonRepresentation; end
1845
+
1846
+ include Google::Apis::Core::JsonObjectSupport
1847
+ end
1848
+
1843
1849
  class RouterAggregatedList
1844
1850
  class Representation < Google::Apis::Core::JsonRepresentation; end
1845
1851
 
@@ -2881,6 +2887,8 @@ module Google
2881
2887
  property :device_name, as: 'deviceName'
2882
2888
  property :disk_encryption_key, as: 'diskEncryptionKey', class: Google::Apis::ComputeV1::CustomerEncryptionKey, decorator: Google::Apis::ComputeV1::CustomerEncryptionKey::Representation
2883
2889
 
2890
+ collection :guest_os_features, as: 'guestOsFeatures', class: Google::Apis::ComputeV1::GuestOsFeature, decorator: Google::Apis::ComputeV1::GuestOsFeature::Representation
2891
+
2884
2892
  property :index, as: 'index'
2885
2893
  property :initialize_params, as: 'initializeParams', class: Google::Apis::ComputeV1::AttachedDiskInitializeParams, decorator: Google::Apis::ComputeV1::AttachedDiskInitializeParams::Representation
2886
2894
 
@@ -3448,6 +3456,8 @@ module Google
3448
3456
  property :description, as: 'description'
3449
3457
  property :disk_encryption_key, as: 'diskEncryptionKey', class: Google::Apis::ComputeV1::CustomerEncryptionKey, decorator: Google::Apis::ComputeV1::CustomerEncryptionKey::Representation
3450
3458
 
3459
+ collection :guest_os_features, as: 'guestOsFeatures', class: Google::Apis::ComputeV1::GuestOsFeature, decorator: Google::Apis::ComputeV1::GuestOsFeature::Representation
3460
+
3451
3461
  property :id, :numeric_string => true, as: 'id'
3452
3462
  property :kind, as: 'kind'
3453
3463
  property :label_fingerprint, :base64 => true, as: 'labelFingerprint'
@@ -4131,6 +4141,10 @@ module Google
4131
4141
  property :source_image_encryption_key, as: 'sourceImageEncryptionKey', class: Google::Apis::ComputeV1::CustomerEncryptionKey, decorator: Google::Apis::ComputeV1::CustomerEncryptionKey::Representation
4132
4142
 
4133
4143
  property :source_image_id, as: 'sourceImageId'
4144
+ property :source_snapshot, as: 'sourceSnapshot'
4145
+ property :source_snapshot_encryption_key, as: 'sourceSnapshotEncryptionKey', class: Google::Apis::ComputeV1::CustomerEncryptionKey, decorator: Google::Apis::ComputeV1::CustomerEncryptionKey::Representation
4146
+
4147
+ property :source_snapshot_id, as: 'sourceSnapshotId'
4134
4148
  property :source_type, as: 'sourceType'
4135
4149
  property :status, as: 'status'
4136
4150
  end
@@ -5318,6 +5332,7 @@ module Google
5318
5332
 
5319
5333
  collection :alias_ip_ranges, as: 'aliasIpRanges', class: Google::Apis::ComputeV1::AliasIpRange, decorator: Google::Apis::ComputeV1::AliasIpRange::Representation
5320
5334
 
5335
+ property :fingerprint, :base64 => true, as: 'fingerprint'
5321
5336
  property :kind, as: 'kind'
5322
5337
  property :name, as: 'name'
5323
5338
  property :network, as: 'network'
@@ -5990,6 +6005,14 @@ module Google
5990
6005
  end
5991
6006
  end
5992
6007
 
6008
+ class RouterAdvertisedIpRange
6009
+ # @private
6010
+ class Representation < Google::Apis::Core::JsonRepresentation
6011
+ property :description, as: 'description'
6012
+ property :range, as: 'range'
6013
+ end
6014
+ end
6015
+
5993
6016
  class RouterAggregatedList
5994
6017
  # @private
5995
6018
  class Representation < Google::Apis::Core::JsonRepresentation
@@ -6025,6 +6048,10 @@ module Google
6025
6048
  class RouterBgp
6026
6049
  # @private
6027
6050
  class Representation < Google::Apis::Core::JsonRepresentation
6051
+ property :advertise_mode, as: 'advertiseMode'
6052
+ collection :advertised_groups, as: 'advertisedGroups'
6053
+ collection :advertised_ip_ranges, as: 'advertisedIpRanges', class: Google::Apis::ComputeV1::RouterAdvertisedIpRange, decorator: Google::Apis::ComputeV1::RouterAdvertisedIpRange::Representation
6054
+
6028
6055
  property :asn, as: 'asn'
6029
6056
  end
6030
6057
  end
@@ -6032,6 +6059,10 @@ module Google
6032
6059
  class RouterBgpPeer
6033
6060
  # @private
6034
6061
  class Representation < Google::Apis::Core::JsonRepresentation
6062
+ property :advertise_mode, as: 'advertiseMode'
6063
+ collection :advertised_groups, as: 'advertisedGroups'
6064
+ collection :advertised_ip_ranges, as: 'advertisedIpRanges', class: Google::Apis::ComputeV1::RouterAdvertisedIpRange, decorator: Google::Apis::ComputeV1::RouterAdvertisedIpRange::Representation
6065
+
6035
6066
  property :advertised_route_priority, as: 'advertisedRoutePriority'
6036
6067
  property :interface_name, as: 'interfaceName'
6037
6068
  property :ip_address, as: 'ipAddress'
@@ -6305,6 +6336,7 @@ module Google
6305
6336
  class Representation < Google::Apis::Core::JsonRepresentation
6306
6337
  property :creation_timestamp, as: 'creationTimestamp'
6307
6338
  property :description, as: 'description'
6339
+ property :fingerprint, :base64 => true, as: 'fingerprint'
6308
6340
  property :gateway_address, as: 'gatewayAddress'
6309
6341
  property :id, :numeric_string => true, as: 'id'
6310
6342
  property :ip_cidr_range, as: 'ipCidrRange'
@@ -57,25 +57,22 @@ module Google
57
57
  # @param [String] project
58
58
  # Project ID for this request.
59
59
  # @param [String] filter
60
- # Sets a filter `expression` for filtering listed resources. Your `expression`
61
- # must be in the format: field_name comparison_string literal_string.
62
- # The field_name is the name of the field you want to compare. Only atomic field
63
- # types are supported (string, number, boolean). The comparison_string must be
64
- # either eq (equals) or ne (not equals). The literal_string is the string value
65
- # to filter to. The literal value must be valid for the type of field you are
66
- # filtering by (string, number, boolean). For string fields, the literal value
67
- # is interpreted as a regular expression using RE2 syntax. The literal value
68
- # must match the entire field.
69
- # For example, to filter for instances that do not have a name of example-
70
- # instance, you would use name ne example-instance.
71
- # You can filter on nested fields. For example, you could filter on instances
72
- # that have set the scheduling.automaticRestart field to true. Use filtering on
73
- # nested fields to take advantage of labels to organize and search for results
74
- # based on label values.
60
+ # A filter expression that filters resources listed in the response. The
61
+ # expression must specify the field name, a comparison operator, and the value
62
+ # that you want to use for filtering. The value must be a string, a number, or a
63
+ # boolean. The comparison operator must be either =, !=, >, or <.
64
+ # For example, if you are filtering Compute Engine instances, you can exclude
65
+ # instances named example-instance by specifying name != example-instance.
66
+ # You can also filter nested fields. For example, you could specify scheduling.
67
+ # automaticRestart = false to include instances only if they are not scheduled
68
+ # for automatic restarts. You can use filtering on nested fields to filter based
69
+ # on resource labels.
75
70
  # To filter on multiple expressions, provide each separate expression within
76
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
77
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
78
- # resources must match all expressions to pass the filters.
71
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
72
+ # Intel Skylake"). By default, each expression is an AND expression. However,
73
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
74
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
75
+ # automaticRestart = true).
79
76
  # @param [Fixnum] max_results
80
77
  # The maximum number of results per page that should be returned. If the number
81
78
  # of available results is larger than maxResults, Compute Engine returns a
@@ -177,25 +174,22 @@ module Google
177
174
  # @param [String] zone
178
175
  # The name of the zone for this request.
179
176
  # @param [String] filter
180
- # Sets a filter `expression` for filtering listed resources. Your `expression`
181
- # must be in the format: field_name comparison_string literal_string.
182
- # The field_name is the name of the field you want to compare. Only atomic field
183
- # types are supported (string, number, boolean). The comparison_string must be
184
- # either eq (equals) or ne (not equals). The literal_string is the string value
185
- # to filter to. The literal value must be valid for the type of field you are
186
- # filtering by (string, number, boolean). For string fields, the literal value
187
- # is interpreted as a regular expression using RE2 syntax. The literal value
188
- # must match the entire field.
189
- # For example, to filter for instances that do not have a name of example-
190
- # instance, you would use name ne example-instance.
191
- # You can filter on nested fields. For example, you could filter on instances
192
- # that have set the scheduling.automaticRestart field to true. Use filtering on
193
- # nested fields to take advantage of labels to organize and search for results
194
- # based on label values.
177
+ # A filter expression that filters resources listed in the response. The
178
+ # expression must specify the field name, a comparison operator, and the value
179
+ # that you want to use for filtering. The value must be a string, a number, or a
180
+ # boolean. The comparison operator must be either =, !=, >, or <.
181
+ # For example, if you are filtering Compute Engine instances, you can exclude
182
+ # instances named example-instance by specifying name != example-instance.
183
+ # You can also filter nested fields. For example, you could specify scheduling.
184
+ # automaticRestart = false to include instances only if they are not scheduled
185
+ # for automatic restarts. You can use filtering on nested fields to filter based
186
+ # on resource labels.
195
187
  # To filter on multiple expressions, provide each separate expression within
196
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
197
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
198
- # resources must match all expressions to pass the filters.
188
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
189
+ # Intel Skylake"). By default, each expression is an AND expression. However,
190
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
191
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
192
+ # automaticRestart = true).
199
193
  # @param [Fixnum] max_results
200
194
  # The maximum number of results per page that should be returned. If the number
201
195
  # of available results is larger than maxResults, Compute Engine returns a
@@ -254,25 +248,22 @@ module Google
254
248
  # @param [String] project
255
249
  # Project ID for this request.
256
250
  # @param [String] filter
257
- # Sets a filter `expression` for filtering listed resources. Your `expression`
258
- # must be in the format: field_name comparison_string literal_string.
259
- # The field_name is the name of the field you want to compare. Only atomic field
260
- # types are supported (string, number, boolean). The comparison_string must be
261
- # either eq (equals) or ne (not equals). The literal_string is the string value
262
- # to filter to. The literal value must be valid for the type of field you are
263
- # filtering by (string, number, boolean). For string fields, the literal value
264
- # is interpreted as a regular expression using RE2 syntax. The literal value
265
- # must match the entire field.
266
- # For example, to filter for instances that do not have a name of example-
267
- # instance, you would use name ne example-instance.
268
- # You can filter on nested fields. For example, you could filter on instances
269
- # that have set the scheduling.automaticRestart field to true. Use filtering on
270
- # nested fields to take advantage of labels to organize and search for results
271
- # based on label values.
251
+ # A filter expression that filters resources listed in the response. The
252
+ # expression must specify the field name, a comparison operator, and the value
253
+ # that you want to use for filtering. The value must be a string, a number, or a
254
+ # boolean. The comparison operator must be either =, !=, >, or <.
255
+ # For example, if you are filtering Compute Engine instances, you can exclude
256
+ # instances named example-instance by specifying name != example-instance.
257
+ # You can also filter nested fields. For example, you could specify scheduling.
258
+ # automaticRestart = false to include instances only if they are not scheduled
259
+ # for automatic restarts. You can use filtering on nested fields to filter based
260
+ # on resource labels.
272
261
  # To filter on multiple expressions, provide each separate expression within
273
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
274
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
275
- # resources must match all expressions to pass the filters.
262
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
263
+ # Intel Skylake"). By default, each expression is an AND expression. However,
264
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
265
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
266
+ # automaticRestart = true).
276
267
  # @param [Fixnum] max_results
277
268
  # The maximum number of results per page that should be returned. If the number
278
269
  # of available results is larger than maxResults, Compute Engine returns a
@@ -480,25 +471,22 @@ module Google
480
471
  # @param [String] region
481
472
  # Name of the region for this request.
482
473
  # @param [String] filter
483
- # Sets a filter `expression` for filtering listed resources. Your `expression`
484
- # must be in the format: field_name comparison_string literal_string.
485
- # The field_name is the name of the field you want to compare. Only atomic field
486
- # types are supported (string, number, boolean). The comparison_string must be
487
- # either eq (equals) or ne (not equals). The literal_string is the string value
488
- # to filter to. The literal value must be valid for the type of field you are
489
- # filtering by (string, number, boolean). For string fields, the literal value
490
- # is interpreted as a regular expression using RE2 syntax. The literal value
491
- # must match the entire field.
492
- # For example, to filter for instances that do not have a name of example-
493
- # instance, you would use name ne example-instance.
494
- # You can filter on nested fields. For example, you could filter on instances
495
- # that have set the scheduling.automaticRestart field to true. Use filtering on
496
- # nested fields to take advantage of labels to organize and search for results
497
- # based on label values.
474
+ # A filter expression that filters resources listed in the response. The
475
+ # expression must specify the field name, a comparison operator, and the value
476
+ # that you want to use for filtering. The value must be a string, a number, or a
477
+ # boolean. The comparison operator must be either =, !=, >, or <.
478
+ # For example, if you are filtering Compute Engine instances, you can exclude
479
+ # instances named example-instance by specifying name != example-instance.
480
+ # You can also filter nested fields. For example, you could specify scheduling.
481
+ # automaticRestart = false to include instances only if they are not scheduled
482
+ # for automatic restarts. You can use filtering on nested fields to filter based
483
+ # on resource labels.
498
484
  # To filter on multiple expressions, provide each separate expression within
499
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
500
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
501
- # resources must match all expressions to pass the filters.
485
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
486
+ # Intel Skylake"). By default, each expression is an AND expression. However,
487
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
488
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
489
+ # automaticRestart = true).
502
490
  # @param [Fixnum] max_results
503
491
  # The maximum number of results per page that should be returned. If the number
504
492
  # of available results is larger than maxResults, Compute Engine returns a
@@ -557,25 +545,22 @@ module Google
557
545
  # @param [String] project
558
546
  # Project ID for this request.
559
547
  # @param [String] filter
560
- # Sets a filter `expression` for filtering listed resources. Your `expression`
561
- # must be in the format: field_name comparison_string literal_string.
562
- # The field_name is the name of the field you want to compare. Only atomic field
563
- # types are supported (string, number, boolean). The comparison_string must be
564
- # either eq (equals) or ne (not equals). The literal_string is the string value
565
- # to filter to. The literal value must be valid for the type of field you are
566
- # filtering by (string, number, boolean). For string fields, the literal value
567
- # is interpreted as a regular expression using RE2 syntax. The literal value
568
- # must match the entire field.
569
- # For example, to filter for instances that do not have a name of example-
570
- # instance, you would use name ne example-instance.
571
- # You can filter on nested fields. For example, you could filter on instances
572
- # that have set the scheduling.automaticRestart field to true. Use filtering on
573
- # nested fields to take advantage of labels to organize and search for results
574
- # based on label values.
548
+ # A filter expression that filters resources listed in the response. The
549
+ # expression must specify the field name, a comparison operator, and the value
550
+ # that you want to use for filtering. The value must be a string, a number, or a
551
+ # boolean. The comparison operator must be either =, !=, >, or <.
552
+ # For example, if you are filtering Compute Engine instances, you can exclude
553
+ # instances named example-instance by specifying name != example-instance.
554
+ # You can also filter nested fields. For example, you could specify scheduling.
555
+ # automaticRestart = false to include instances only if they are not scheduled
556
+ # for automatic restarts. You can use filtering on nested fields to filter based
557
+ # on resource labels.
575
558
  # To filter on multiple expressions, provide each separate expression within
576
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
577
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
578
- # resources must match all expressions to pass the filters.
559
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
560
+ # Intel Skylake"). By default, each expression is an AND expression. However,
561
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
562
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
563
+ # automaticRestart = true).
579
564
  # @param [Fixnum] max_results
580
565
  # The maximum number of results per page that should be returned. If the number
581
566
  # of available results is larger than maxResults, Compute Engine returns a
@@ -784,25 +769,22 @@ module Google
784
769
  # @param [String] zone
785
770
  # Name of the zone for this request.
786
771
  # @param [String] filter
787
- # Sets a filter `expression` for filtering listed resources. Your `expression`
788
- # must be in the format: field_name comparison_string literal_string.
789
- # The field_name is the name of the field you want to compare. Only atomic field
790
- # types are supported (string, number, boolean). The comparison_string must be
791
- # either eq (equals) or ne (not equals). The literal_string is the string value
792
- # to filter to. The literal value must be valid for the type of field you are
793
- # filtering by (string, number, boolean). For string fields, the literal value
794
- # is interpreted as a regular expression using RE2 syntax. The literal value
795
- # must match the entire field.
796
- # For example, to filter for instances that do not have a name of example-
797
- # instance, you would use name ne example-instance.
798
- # You can filter on nested fields. For example, you could filter on instances
799
- # that have set the scheduling.automaticRestart field to true. Use filtering on
800
- # nested fields to take advantage of labels to organize and search for results
801
- # based on label values.
772
+ # A filter expression that filters resources listed in the response. The
773
+ # expression must specify the field name, a comparison operator, and the value
774
+ # that you want to use for filtering. The value must be a string, a number, or a
775
+ # boolean. The comparison operator must be either =, !=, >, or <.
776
+ # For example, if you are filtering Compute Engine instances, you can exclude
777
+ # instances named example-instance by specifying name != example-instance.
778
+ # You can also filter nested fields. For example, you could specify scheduling.
779
+ # automaticRestart = false to include instances only if they are not scheduled
780
+ # for automatic restarts. You can use filtering on nested fields to filter based
781
+ # on resource labels.
802
782
  # To filter on multiple expressions, provide each separate expression within
803
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
804
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
805
- # resources must match all expressions to pass the filters.
783
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
784
+ # Intel Skylake"). By default, each expression is an AND expression. However,
785
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
786
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
787
+ # automaticRestart = true).
806
788
  # @param [Fixnum] max_results
807
789
  # The maximum number of results per page that should be returned. If the number
808
790
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1117,25 +1099,22 @@ module Google
1117
1099
  # @param [String] project
1118
1100
  # Project ID for this request.
1119
1101
  # @param [String] filter
1120
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1121
- # must be in the format: field_name comparison_string literal_string.
1122
- # The field_name is the name of the field you want to compare. Only atomic field
1123
- # types are supported (string, number, boolean). The comparison_string must be
1124
- # either eq (equals) or ne (not equals). The literal_string is the string value
1125
- # to filter to. The literal value must be valid for the type of field you are
1126
- # filtering by (string, number, boolean). For string fields, the literal value
1127
- # is interpreted as a regular expression using RE2 syntax. The literal value
1128
- # must match the entire field.
1129
- # For example, to filter for instances that do not have a name of example-
1130
- # instance, you would use name ne example-instance.
1131
- # You can filter on nested fields. For example, you could filter on instances
1132
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1133
- # nested fields to take advantage of labels to organize and search for results
1134
- # based on label values.
1102
+ # A filter expression that filters resources listed in the response. The
1103
+ # expression must specify the field name, a comparison operator, and the value
1104
+ # that you want to use for filtering. The value must be a string, a number, or a
1105
+ # boolean. The comparison operator must be either =, !=, >, or <.
1106
+ # For example, if you are filtering Compute Engine instances, you can exclude
1107
+ # instances named example-instance by specifying name != example-instance.
1108
+ # You can also filter nested fields. For example, you could specify scheduling.
1109
+ # automaticRestart = false to include instances only if they are not scheduled
1110
+ # for automatic restarts. You can use filtering on nested fields to filter based
1111
+ # on resource labels.
1135
1112
  # To filter on multiple expressions, provide each separate expression within
1136
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1137
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1138
- # resources must match all expressions to pass the filters.
1113
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1114
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1115
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1116
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1117
+ # automaticRestart = true).
1139
1118
  # @param [Fixnum] max_results
1140
1119
  # The maximum number of results per page that should be returned. If the number
1141
1120
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1303,25 +1282,22 @@ module Google
1303
1282
  # @param [String] project
1304
1283
  # Name of the project scoping this request.
1305
1284
  # @param [String] filter
1306
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1307
- # must be in the format: field_name comparison_string literal_string.
1308
- # The field_name is the name of the field you want to compare. Only atomic field
1309
- # types are supported (string, number, boolean). The comparison_string must be
1310
- # either eq (equals) or ne (not equals). The literal_string is the string value
1311
- # to filter to. The literal value must be valid for the type of field you are
1312
- # filtering by (string, number, boolean). For string fields, the literal value
1313
- # is interpreted as a regular expression using RE2 syntax. The literal value
1314
- # must match the entire field.
1315
- # For example, to filter for instances that do not have a name of example-
1316
- # instance, you would use name ne example-instance.
1317
- # You can filter on nested fields. For example, you could filter on instances
1318
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1319
- # nested fields to take advantage of labels to organize and search for results
1320
- # based on label values.
1285
+ # A filter expression that filters resources listed in the response. The
1286
+ # expression must specify the field name, a comparison operator, and the value
1287
+ # that you want to use for filtering. The value must be a string, a number, or a
1288
+ # boolean. The comparison operator must be either =, !=, >, or <.
1289
+ # For example, if you are filtering Compute Engine instances, you can exclude
1290
+ # instances named example-instance by specifying name != example-instance.
1291
+ # You can also filter nested fields. For example, you could specify scheduling.
1292
+ # automaticRestart = false to include instances only if they are not scheduled
1293
+ # for automatic restarts. You can use filtering on nested fields to filter based
1294
+ # on resource labels.
1321
1295
  # To filter on multiple expressions, provide each separate expression within
1322
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1323
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1324
- # resources must match all expressions to pass the filters.
1296
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1297
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1298
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1299
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1300
+ # automaticRestart = true).
1325
1301
  # @param [Fixnum] max_results
1326
1302
  # The maximum number of results per page that should be returned. If the number
1327
1303
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1562,25 +1538,22 @@ module Google
1562
1538
  # @param [String] project
1563
1539
  # Project ID for this request.
1564
1540
  # @param [String] filter
1565
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1566
- # must be in the format: field_name comparison_string literal_string.
1567
- # The field_name is the name of the field you want to compare. Only atomic field
1568
- # types are supported (string, number, boolean). The comparison_string must be
1569
- # either eq (equals) or ne (not equals). The literal_string is the string value
1570
- # to filter to. The literal value must be valid for the type of field you are
1571
- # filtering by (string, number, boolean). For string fields, the literal value
1572
- # is interpreted as a regular expression using RE2 syntax. The literal value
1573
- # must match the entire field.
1574
- # For example, to filter for instances that do not have a name of example-
1575
- # instance, you would use name ne example-instance.
1576
- # You can filter on nested fields. For example, you could filter on instances
1577
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1578
- # nested fields to take advantage of labels to organize and search for results
1579
- # based on label values.
1541
+ # A filter expression that filters resources listed in the response. The
1542
+ # expression must specify the field name, a comparison operator, and the value
1543
+ # that you want to use for filtering. The value must be a string, a number, or a
1544
+ # boolean. The comparison operator must be either =, !=, >, or <.
1545
+ # For example, if you are filtering Compute Engine instances, you can exclude
1546
+ # instances named example-instance by specifying name != example-instance.
1547
+ # You can also filter nested fields. For example, you could specify scheduling.
1548
+ # automaticRestart = false to include instances only if they are not scheduled
1549
+ # for automatic restarts. You can use filtering on nested fields to filter based
1550
+ # on resource labels.
1580
1551
  # To filter on multiple expressions, provide each separate expression within
1581
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1582
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1583
- # resources must match all expressions to pass the filters.
1552
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1553
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1554
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1555
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1556
+ # automaticRestart = true).
1584
1557
  # @param [Fixnum] max_results
1585
1558
  # The maximum number of results per page that should be returned. If the number
1586
1559
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1751,25 +1724,22 @@ module Google
1751
1724
  # @param [String] project
1752
1725
  # Project ID for this request.
1753
1726
  # @param [String] filter
1754
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1755
- # must be in the format: field_name comparison_string literal_string.
1756
- # The field_name is the name of the field you want to compare. Only atomic field
1757
- # types are supported (string, number, boolean). The comparison_string must be
1758
- # either eq (equals) or ne (not equals). The literal_string is the string value
1759
- # to filter to. The literal value must be valid for the type of field you are
1760
- # filtering by (string, number, boolean). For string fields, the literal value
1761
- # is interpreted as a regular expression using RE2 syntax. The literal value
1762
- # must match the entire field.
1763
- # For example, to filter for instances that do not have a name of example-
1764
- # instance, you would use name ne example-instance.
1765
- # You can filter on nested fields. For example, you could filter on instances
1766
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1767
- # nested fields to take advantage of labels to organize and search for results
1768
- # based on label values.
1727
+ # A filter expression that filters resources listed in the response. The
1728
+ # expression must specify the field name, a comparison operator, and the value
1729
+ # that you want to use for filtering. The value must be a string, a number, or a
1730
+ # boolean. The comparison operator must be either =, !=, >, or <.
1731
+ # For example, if you are filtering Compute Engine instances, you can exclude
1732
+ # instances named example-instance by specifying name != example-instance.
1733
+ # You can also filter nested fields. For example, you could specify scheduling.
1734
+ # automaticRestart = false to include instances only if they are not scheduled
1735
+ # for automatic restarts. You can use filtering on nested fields to filter based
1736
+ # on resource labels.
1769
1737
  # To filter on multiple expressions, provide each separate expression within
1770
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1771
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1772
- # resources must match all expressions to pass the filters.
1738
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1739
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1740
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1741
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1742
+ # automaticRestart = true).
1773
1743
  # @param [Fixnum] max_results
1774
1744
  # The maximum number of results per page that should be returned. If the number
1775
1745
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1871,25 +1841,22 @@ module Google
1871
1841
  # @param [String] zone
1872
1842
  # The name of the zone for this request.
1873
1843
  # @param [String] filter
1874
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1875
- # must be in the format: field_name comparison_string literal_string.
1876
- # The field_name is the name of the field you want to compare. Only atomic field
1877
- # types are supported (string, number, boolean). The comparison_string must be
1878
- # either eq (equals) or ne (not equals). The literal_string is the string value
1879
- # to filter to. The literal value must be valid for the type of field you are
1880
- # filtering by (string, number, boolean). For string fields, the literal value
1881
- # is interpreted as a regular expression using RE2 syntax. The literal value
1882
- # must match the entire field.
1883
- # For example, to filter for instances that do not have a name of example-
1884
- # instance, you would use name ne example-instance.
1885
- # You can filter on nested fields. For example, you could filter on instances
1886
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1887
- # nested fields to take advantage of labels to organize and search for results
1888
- # based on label values.
1844
+ # A filter expression that filters resources listed in the response. The
1845
+ # expression must specify the field name, a comparison operator, and the value
1846
+ # that you want to use for filtering. The value must be a string, a number, or a
1847
+ # boolean. The comparison operator must be either =, !=, >, or <.
1848
+ # For example, if you are filtering Compute Engine instances, you can exclude
1849
+ # instances named example-instance by specifying name != example-instance.
1850
+ # You can also filter nested fields. For example, you could specify scheduling.
1851
+ # automaticRestart = false to include instances only if they are not scheduled
1852
+ # for automatic restarts. You can use filtering on nested fields to filter based
1853
+ # on resource labels.
1889
1854
  # To filter on multiple expressions, provide each separate expression within
1890
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1891
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1892
- # resources must match all expressions to pass the filters.
1855
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1856
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1857
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1858
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1859
+ # automaticRestart = true).
1893
1860
  # @param [Fixnum] max_results
1894
1861
  # The maximum number of results per page that should be returned. If the number
1895
1862
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1948,25 +1915,22 @@ module Google
1948
1915
  # @param [String] project
1949
1916
  # Project ID for this request.
1950
1917
  # @param [String] filter
1951
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1952
- # must be in the format: field_name comparison_string literal_string.
1953
- # The field_name is the name of the field you want to compare. Only atomic field
1954
- # types are supported (string, number, boolean). The comparison_string must be
1955
- # either eq (equals) or ne (not equals). The literal_string is the string value
1956
- # to filter to. The literal value must be valid for the type of field you are
1957
- # filtering by (string, number, boolean). For string fields, the literal value
1958
- # is interpreted as a regular expression using RE2 syntax. The literal value
1959
- # must match the entire field.
1960
- # For example, to filter for instances that do not have a name of example-
1961
- # instance, you would use name ne example-instance.
1962
- # You can filter on nested fields. For example, you could filter on instances
1963
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1964
- # nested fields to take advantage of labels to organize and search for results
1965
- # based on label values.
1918
+ # A filter expression that filters resources listed in the response. The
1919
+ # expression must specify the field name, a comparison operator, and the value
1920
+ # that you want to use for filtering. The value must be a string, a number, or a
1921
+ # boolean. The comparison operator must be either =, !=, >, or <.
1922
+ # For example, if you are filtering Compute Engine instances, you can exclude
1923
+ # instances named example-instance by specifying name != example-instance.
1924
+ # You can also filter nested fields. For example, you could specify scheduling.
1925
+ # automaticRestart = false to include instances only if they are not scheduled
1926
+ # for automatic restarts. You can use filtering on nested fields to filter based
1927
+ # on resource labels.
1966
1928
  # To filter on multiple expressions, provide each separate expression within
1967
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1968
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1969
- # resources must match all expressions to pass the filters.
1929
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1930
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1931
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1932
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1933
+ # automaticRestart = true).
1970
1934
  # @param [Fixnum] max_results
1971
1935
  # The maximum number of results per page that should be returned. If the number
1972
1936
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2240,25 +2204,22 @@ module Google
2240
2204
  # @param [String] zone
2241
2205
  # The name of the zone for this request.
2242
2206
  # @param [String] filter
2243
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2244
- # must be in the format: field_name comparison_string literal_string.
2245
- # The field_name is the name of the field you want to compare. Only atomic field
2246
- # types are supported (string, number, boolean). The comparison_string must be
2247
- # either eq (equals) or ne (not equals). The literal_string is the string value
2248
- # to filter to. The literal value must be valid for the type of field you are
2249
- # filtering by (string, number, boolean). For string fields, the literal value
2250
- # is interpreted as a regular expression using RE2 syntax. The literal value
2251
- # must match the entire field.
2252
- # For example, to filter for instances that do not have a name of example-
2253
- # instance, you would use name ne example-instance.
2254
- # You can filter on nested fields. For example, you could filter on instances
2255
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2256
- # nested fields to take advantage of labels to organize and search for results
2257
- # based on label values.
2207
+ # A filter expression that filters resources listed in the response. The
2208
+ # expression must specify the field name, a comparison operator, and the value
2209
+ # that you want to use for filtering. The value must be a string, a number, or a
2210
+ # boolean. The comparison operator must be either =, !=, >, or <.
2211
+ # For example, if you are filtering Compute Engine instances, you can exclude
2212
+ # instances named example-instance by specifying name != example-instance.
2213
+ # You can also filter nested fields. For example, you could specify scheduling.
2214
+ # automaticRestart = false to include instances only if they are not scheduled
2215
+ # for automatic restarts. You can use filtering on nested fields to filter based
2216
+ # on resource labels.
2258
2217
  # To filter on multiple expressions, provide each separate expression within
2259
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2260
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2261
- # resources must match all expressions to pass the filters.
2218
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2219
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2220
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2221
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2222
+ # automaticRestart = true).
2262
2223
  # @param [Fixnum] max_results
2263
2224
  # The maximum number of results per page that should be returned. If the number
2264
2225
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2570,25 +2531,22 @@ module Google
2570
2531
  # @param [String] project
2571
2532
  # Project ID for this request.
2572
2533
  # @param [String] filter
2573
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2574
- # must be in the format: field_name comparison_string literal_string.
2575
- # The field_name is the name of the field you want to compare. Only atomic field
2576
- # types are supported (string, number, boolean). The comparison_string must be
2577
- # either eq (equals) or ne (not equals). The literal_string is the string value
2578
- # to filter to. The literal value must be valid for the type of field you are
2579
- # filtering by (string, number, boolean). For string fields, the literal value
2580
- # is interpreted as a regular expression using RE2 syntax. The literal value
2581
- # must match the entire field.
2582
- # For example, to filter for instances that do not have a name of example-
2583
- # instance, you would use name ne example-instance.
2584
- # You can filter on nested fields. For example, you could filter on instances
2585
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2586
- # nested fields to take advantage of labels to organize and search for results
2587
- # based on label values.
2534
+ # A filter expression that filters resources listed in the response. The
2535
+ # expression must specify the field name, a comparison operator, and the value
2536
+ # that you want to use for filtering. The value must be a string, a number, or a
2537
+ # boolean. The comparison operator must be either =, !=, >, or <.
2538
+ # For example, if you are filtering Compute Engine instances, you can exclude
2539
+ # instances named example-instance by specifying name != example-instance.
2540
+ # You can also filter nested fields. For example, you could specify scheduling.
2541
+ # automaticRestart = false to include instances only if they are not scheduled
2542
+ # for automatic restarts. You can use filtering on nested fields to filter based
2543
+ # on resource labels.
2588
2544
  # To filter on multiple expressions, provide each separate expression within
2589
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2590
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2591
- # resources must match all expressions to pass the filters.
2545
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2546
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2547
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2548
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2549
+ # automaticRestart = true).
2592
2550
  # @param [Fixnum] max_results
2593
2551
  # The maximum number of results per page that should be returned. If the number
2594
2552
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2756,25 +2714,22 @@ module Google
2756
2714
  # @param [String] project
2757
2715
  # Project ID for this request.
2758
2716
  # @param [String] filter
2759
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2760
- # must be in the format: field_name comparison_string literal_string.
2761
- # The field_name is the name of the field you want to compare. Only atomic field
2762
- # types are supported (string, number, boolean). The comparison_string must be
2763
- # either eq (equals) or ne (not equals). The literal_string is the string value
2764
- # to filter to. The literal value must be valid for the type of field you are
2765
- # filtering by (string, number, boolean). For string fields, the literal value
2766
- # is interpreted as a regular expression using RE2 syntax. The literal value
2767
- # must match the entire field.
2768
- # For example, to filter for instances that do not have a name of example-
2769
- # instance, you would use name ne example-instance.
2770
- # You can filter on nested fields. For example, you could filter on instances
2771
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2772
- # nested fields to take advantage of labels to organize and search for results
2773
- # based on label values.
2717
+ # A filter expression that filters resources listed in the response. The
2718
+ # expression must specify the field name, a comparison operator, and the value
2719
+ # that you want to use for filtering. The value must be a string, a number, or a
2720
+ # boolean. The comparison operator must be either =, !=, >, or <.
2721
+ # For example, if you are filtering Compute Engine instances, you can exclude
2722
+ # instances named example-instance by specifying name != example-instance.
2723
+ # You can also filter nested fields. For example, you could specify scheduling.
2724
+ # automaticRestart = false to include instances only if they are not scheduled
2725
+ # for automatic restarts. You can use filtering on nested fields to filter based
2726
+ # on resource labels.
2774
2727
  # To filter on multiple expressions, provide each separate expression within
2775
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2776
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2777
- # resources must match all expressions to pass the filters.
2728
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2729
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2730
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2731
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2732
+ # automaticRestart = true).
2778
2733
  # @param [Fixnum] max_results
2779
2734
  # The maximum number of results per page that should be returned. If the number
2780
2735
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2983,25 +2938,22 @@ module Google
2983
2938
  # @param [String] region
2984
2939
  # Name of the region scoping this request.
2985
2940
  # @param [String] filter
2986
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2987
- # must be in the format: field_name comparison_string literal_string.
2988
- # The field_name is the name of the field you want to compare. Only atomic field
2989
- # types are supported (string, number, boolean). The comparison_string must be
2990
- # either eq (equals) or ne (not equals). The literal_string is the string value
2991
- # to filter to. The literal value must be valid for the type of field you are
2992
- # filtering by (string, number, boolean). For string fields, the literal value
2993
- # is interpreted as a regular expression using RE2 syntax. The literal value
2994
- # must match the entire field.
2995
- # For example, to filter for instances that do not have a name of example-
2996
- # instance, you would use name ne example-instance.
2997
- # You can filter on nested fields. For example, you could filter on instances
2998
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2999
- # nested fields to take advantage of labels to organize and search for results
3000
- # based on label values.
2941
+ # A filter expression that filters resources listed in the response. The
2942
+ # expression must specify the field name, a comparison operator, and the value
2943
+ # that you want to use for filtering. The value must be a string, a number, or a
2944
+ # boolean. The comparison operator must be either =, !=, >, or <.
2945
+ # For example, if you are filtering Compute Engine instances, you can exclude
2946
+ # instances named example-instance by specifying name != example-instance.
2947
+ # You can also filter nested fields. For example, you could specify scheduling.
2948
+ # automaticRestart = false to include instances only if they are not scheduled
2949
+ # for automatic restarts. You can use filtering on nested fields to filter based
2950
+ # on resource labels.
3001
2951
  # To filter on multiple expressions, provide each separate expression within
3002
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3003
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3004
- # resources must match all expressions to pass the filters.
2952
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2953
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2954
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2955
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2956
+ # automaticRestart = true).
3005
2957
  # @param [Fixnum] max_results
3006
2958
  # The maximum number of results per page that should be returned. If the number
3007
2959
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3257,25 +3209,22 @@ module Google
3257
3209
  # @param [String] project
3258
3210
  # Project ID for this request.
3259
3211
  # @param [String] filter
3260
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3261
- # must be in the format: field_name comparison_string literal_string.
3262
- # The field_name is the name of the field you want to compare. Only atomic field
3263
- # types are supported (string, number, boolean). The comparison_string must be
3264
- # either eq (equals) or ne (not equals). The literal_string is the string value
3265
- # to filter to. The literal value must be valid for the type of field you are
3266
- # filtering by (string, number, boolean). For string fields, the literal value
3267
- # is interpreted as a regular expression using RE2 syntax. The literal value
3268
- # must match the entire field.
3269
- # For example, to filter for instances that do not have a name of example-
3270
- # instance, you would use name ne example-instance.
3271
- # You can filter on nested fields. For example, you could filter on instances
3272
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3273
- # nested fields to take advantage of labels to organize and search for results
3274
- # based on label values.
3212
+ # A filter expression that filters resources listed in the response. The
3213
+ # expression must specify the field name, a comparison operator, and the value
3214
+ # that you want to use for filtering. The value must be a string, a number, or a
3215
+ # boolean. The comparison operator must be either =, !=, >, or <.
3216
+ # For example, if you are filtering Compute Engine instances, you can exclude
3217
+ # instances named example-instance by specifying name != example-instance.
3218
+ # You can also filter nested fields. For example, you could specify scheduling.
3219
+ # automaticRestart = false to include instances only if they are not scheduled
3220
+ # for automatic restarts. You can use filtering on nested fields to filter based
3221
+ # on resource labels.
3275
3222
  # To filter on multiple expressions, provide each separate expression within
3276
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3277
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3278
- # resources must match all expressions to pass the filters.
3223
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3224
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3225
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3226
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3227
+ # automaticRestart = true).
3279
3228
  # @param [Fixnum] max_results
3280
3229
  # The maximum number of results per page that should be returned. If the number
3281
3230
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3474,25 +3423,22 @@ module Google
3474
3423
  # @param [String] project
3475
3424
  # Project ID for this request.
3476
3425
  # @param [String] filter
3477
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3478
- # must be in the format: field_name comparison_string literal_string.
3479
- # The field_name is the name of the field you want to compare. Only atomic field
3480
- # types are supported (string, number, boolean). The comparison_string must be
3481
- # either eq (equals) or ne (not equals). The literal_string is the string value
3482
- # to filter to. The literal value must be valid for the type of field you are
3483
- # filtering by (string, number, boolean). For string fields, the literal value
3484
- # is interpreted as a regular expression using RE2 syntax. The literal value
3485
- # must match the entire field.
3486
- # For example, to filter for instances that do not have a name of example-
3487
- # instance, you would use name ne example-instance.
3488
- # You can filter on nested fields. For example, you could filter on instances
3489
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3490
- # nested fields to take advantage of labels to organize and search for results
3491
- # based on label values.
3426
+ # A filter expression that filters resources listed in the response. The
3427
+ # expression must specify the field name, a comparison operator, and the value
3428
+ # that you want to use for filtering. The value must be a string, a number, or a
3429
+ # boolean. The comparison operator must be either =, !=, >, or <.
3430
+ # For example, if you are filtering Compute Engine instances, you can exclude
3431
+ # instances named example-instance by specifying name != example-instance.
3432
+ # You can also filter nested fields. For example, you could specify scheduling.
3433
+ # automaticRestart = false to include instances only if they are not scheduled
3434
+ # for automatic restarts. You can use filtering on nested fields to filter based
3435
+ # on resource labels.
3492
3436
  # To filter on multiple expressions, provide each separate expression within
3493
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3494
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3495
- # resources must match all expressions to pass the filters.
3437
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3438
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3439
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3440
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3441
+ # automaticRestart = true).
3496
3442
  # @param [Fixnum] max_results
3497
3443
  # The maximum number of results per page that should be returned. If the number
3498
3444
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3604,25 +3550,22 @@ module Google
3604
3550
  # @param [String] project
3605
3551
  # Project ID for this request.
3606
3552
  # @param [String] filter
3607
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3608
- # must be in the format: field_name comparison_string literal_string.
3609
- # The field_name is the name of the field you want to compare. Only atomic field
3610
- # types are supported (string, number, boolean). The comparison_string must be
3611
- # either eq (equals) or ne (not equals). The literal_string is the string value
3612
- # to filter to. The literal value must be valid for the type of field you are
3613
- # filtering by (string, number, boolean). For string fields, the literal value
3614
- # is interpreted as a regular expression using RE2 syntax. The literal value
3615
- # must match the entire field.
3616
- # For example, to filter for instances that do not have a name of example-
3617
- # instance, you would use name ne example-instance.
3618
- # You can filter on nested fields. For example, you could filter on instances
3619
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3620
- # nested fields to take advantage of labels to organize and search for results
3621
- # based on label values.
3553
+ # A filter expression that filters resources listed in the response. The
3554
+ # expression must specify the field name, a comparison operator, and the value
3555
+ # that you want to use for filtering. The value must be a string, a number, or a
3556
+ # boolean. The comparison operator must be either =, !=, >, or <.
3557
+ # For example, if you are filtering Compute Engine instances, you can exclude
3558
+ # instances named example-instance by specifying name != example-instance.
3559
+ # You can also filter nested fields. For example, you could specify scheduling.
3560
+ # automaticRestart = false to include instances only if they are not scheduled
3561
+ # for automatic restarts. You can use filtering on nested fields to filter based
3562
+ # on resource labels.
3622
3563
  # To filter on multiple expressions, provide each separate expression within
3623
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3624
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3625
- # resources must match all expressions to pass the filters.
3564
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3565
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3566
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3567
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3568
+ # automaticRestart = true).
3626
3569
  # @param [Fixnum] max_results
3627
3570
  # The maximum number of results per page that should be returned. If the number
3628
3571
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3755,25 +3698,22 @@ module Google
3755
3698
  # @param [String] project
3756
3699
  # Project ID for this request.
3757
3700
  # @param [String] filter
3758
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3759
- # must be in the format: field_name comparison_string literal_string.
3760
- # The field_name is the name of the field you want to compare. Only atomic field
3761
- # types are supported (string, number, boolean). The comparison_string must be
3762
- # either eq (equals) or ne (not equals). The literal_string is the string value
3763
- # to filter to. The literal value must be valid for the type of field you are
3764
- # filtering by (string, number, boolean). For string fields, the literal value
3765
- # is interpreted as a regular expression using RE2 syntax. The literal value
3766
- # must match the entire field.
3767
- # For example, to filter for instances that do not have a name of example-
3768
- # instance, you would use name ne example-instance.
3769
- # You can filter on nested fields. For example, you could filter on instances
3770
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3771
- # nested fields to take advantage of labels to organize and search for results
3772
- # based on label values.
3701
+ # A filter expression that filters resources listed in the response. The
3702
+ # expression must specify the field name, a comparison operator, and the value
3703
+ # that you want to use for filtering. The value must be a string, a number, or a
3704
+ # boolean. The comparison operator must be either =, !=, >, or <.
3705
+ # For example, if you are filtering Compute Engine instances, you can exclude
3706
+ # instances named example-instance by specifying name != example-instance.
3707
+ # You can also filter nested fields. For example, you could specify scheduling.
3708
+ # automaticRestart = false to include instances only if they are not scheduled
3709
+ # for automatic restarts. You can use filtering on nested fields to filter based
3710
+ # on resource labels.
3773
3711
  # To filter on multiple expressions, provide each separate expression within
3774
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3775
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3776
- # resources must match all expressions to pass the filters.
3712
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3713
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3714
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3715
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3716
+ # automaticRestart = true).
3777
3717
  # @param [Fixnum] max_results
3778
3718
  # The maximum number of results per page that should be returned. If the number
3779
3719
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3971,25 +3911,22 @@ module Google
3971
3911
  # @param [String] project
3972
3912
  # Project ID for this request.
3973
3913
  # @param [String] filter
3974
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3975
- # must be in the format: field_name comparison_string literal_string.
3976
- # The field_name is the name of the field you want to compare. Only atomic field
3977
- # types are supported (string, number, boolean). The comparison_string must be
3978
- # either eq (equals) or ne (not equals). The literal_string is the string value
3979
- # to filter to. The literal value must be valid for the type of field you are
3980
- # filtering by (string, number, boolean). For string fields, the literal value
3981
- # is interpreted as a regular expression using RE2 syntax. The literal value
3982
- # must match the entire field.
3983
- # For example, to filter for instances that do not have a name of example-
3984
- # instance, you would use name ne example-instance.
3985
- # You can filter on nested fields. For example, you could filter on instances
3986
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3987
- # nested fields to take advantage of labels to organize and search for results
3988
- # based on label values.
3914
+ # A filter expression that filters resources listed in the response. The
3915
+ # expression must specify the field name, a comparison operator, and the value
3916
+ # that you want to use for filtering. The value must be a string, a number, or a
3917
+ # boolean. The comparison operator must be either =, !=, >, or <.
3918
+ # For example, if you are filtering Compute Engine instances, you can exclude
3919
+ # instances named example-instance by specifying name != example-instance.
3920
+ # You can also filter nested fields. For example, you could specify scheduling.
3921
+ # automaticRestart = false to include instances only if they are not scheduled
3922
+ # for automatic restarts. You can use filtering on nested fields to filter based
3923
+ # on resource labels.
3989
3924
  # To filter on multiple expressions, provide each separate expression within
3990
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3991
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3992
- # resources must match all expressions to pass the filters.
3925
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3926
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3927
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3928
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3929
+ # automaticRestart = true).
3993
3930
  # @param [Fixnum] max_results
3994
3931
  # The maximum number of results per page that should be returned. If the number
3995
3932
  # of available results is larger than maxResults, Compute Engine returns a
@@ -4297,25 +4234,22 @@ module Google
4297
4234
  # @param [String] project
4298
4235
  # Project ID for this request.
4299
4236
  # @param [String] filter
4300
- # Sets a filter `expression` for filtering listed resources. Your `expression`
4301
- # must be in the format: field_name comparison_string literal_string.
4302
- # The field_name is the name of the field you want to compare. Only atomic field
4303
- # types are supported (string, number, boolean). The comparison_string must be
4304
- # either eq (equals) or ne (not equals). The literal_string is the string value
4305
- # to filter to. The literal value must be valid for the type of field you are
4306
- # filtering by (string, number, boolean). For string fields, the literal value
4307
- # is interpreted as a regular expression using RE2 syntax. The literal value
4308
- # must match the entire field.
4309
- # For example, to filter for instances that do not have a name of example-
4310
- # instance, you would use name ne example-instance.
4311
- # You can filter on nested fields. For example, you could filter on instances
4312
- # that have set the scheduling.automaticRestart field to true. Use filtering on
4313
- # nested fields to take advantage of labels to organize and search for results
4314
- # based on label values.
4237
+ # A filter expression that filters resources listed in the response. The
4238
+ # expression must specify the field name, a comparison operator, and the value
4239
+ # that you want to use for filtering. The value must be a string, a number, or a
4240
+ # boolean. The comparison operator must be either =, !=, >, or <.
4241
+ # For example, if you are filtering Compute Engine instances, you can exclude
4242
+ # instances named example-instance by specifying name != example-instance.
4243
+ # You can also filter nested fields. For example, you could specify scheduling.
4244
+ # automaticRestart = false to include instances only if they are not scheduled
4245
+ # for automatic restarts. You can use filtering on nested fields to filter based
4246
+ # on resource labels.
4315
4247
  # To filter on multiple expressions, provide each separate expression within
4316
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
4317
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
4318
- # resources must match all expressions to pass the filters.
4248
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
4249
+ # Intel Skylake"). By default, each expression is an AND expression. However,
4250
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
4251
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
4252
+ # automaticRestart = true).
4319
4253
  # @param [Fixnum] max_results
4320
4254
  # The maximum number of results per page that should be returned. If the number
4321
4255
  # of available results is larger than maxResults, Compute Engine returns a
@@ -4623,25 +4557,22 @@ module Google
4623
4557
  # @param [String] project
4624
4558
  # Project ID for this request.
4625
4559
  # @param [String] filter
4626
- # Sets a filter `expression` for filtering listed resources. Your `expression`
4627
- # must be in the format: field_name comparison_string literal_string.
4628
- # The field_name is the name of the field you want to compare. Only atomic field
4629
- # types are supported (string, number, boolean). The comparison_string must be
4630
- # either eq (equals) or ne (not equals). The literal_string is the string value
4631
- # to filter to. The literal value must be valid for the type of field you are
4632
- # filtering by (string, number, boolean). For string fields, the literal value
4633
- # is interpreted as a regular expression using RE2 syntax. The literal value
4634
- # must match the entire field.
4635
- # For example, to filter for instances that do not have a name of example-
4636
- # instance, you would use name ne example-instance.
4637
- # You can filter on nested fields. For example, you could filter on instances
4638
- # that have set the scheduling.automaticRestart field to true. Use filtering on
4639
- # nested fields to take advantage of labels to organize and search for results
4640
- # based on label values.
4560
+ # A filter expression that filters resources listed in the response. The
4561
+ # expression must specify the field name, a comparison operator, and the value
4562
+ # that you want to use for filtering. The value must be a string, a number, or a
4563
+ # boolean. The comparison operator must be either =, !=, >, or <.
4564
+ # For example, if you are filtering Compute Engine instances, you can exclude
4565
+ # instances named example-instance by specifying name != example-instance.
4566
+ # You can also filter nested fields. For example, you could specify scheduling.
4567
+ # automaticRestart = false to include instances only if they are not scheduled
4568
+ # for automatic restarts. You can use filtering on nested fields to filter based
4569
+ # on resource labels.
4641
4570
  # To filter on multiple expressions, provide each separate expression within
4642
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
4643
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
4644
- # resources must match all expressions to pass the filters.
4571
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
4572
+ # Intel Skylake"). By default, each expression is an AND expression. However,
4573
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
4574
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
4575
+ # automaticRestart = true).
4645
4576
  # @param [Fixnum] max_results
4646
4577
  # The maximum number of results per page that should be returned. If the number
4647
4578
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5048,25 +4979,22 @@ module Google
5048
4979
  # @param [String] project
5049
4980
  # Project ID for this request.
5050
4981
  # @param [String] filter
5051
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5052
- # must be in the format: field_name comparison_string literal_string.
5053
- # The field_name is the name of the field you want to compare. Only atomic field
5054
- # types are supported (string, number, boolean). The comparison_string must be
5055
- # either eq (equals) or ne (not equals). The literal_string is the string value
5056
- # to filter to. The literal value must be valid for the type of field you are
5057
- # filtering by (string, number, boolean). For string fields, the literal value
5058
- # is interpreted as a regular expression using RE2 syntax. The literal value
5059
- # must match the entire field.
5060
- # For example, to filter for instances that do not have a name of example-
5061
- # instance, you would use name ne example-instance.
5062
- # You can filter on nested fields. For example, you could filter on instances
5063
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5064
- # nested fields to take advantage of labels to organize and search for results
5065
- # based on label values.
4982
+ # A filter expression that filters resources listed in the response. The
4983
+ # expression must specify the field name, a comparison operator, and the value
4984
+ # that you want to use for filtering. The value must be a string, a number, or a
4985
+ # boolean. The comparison operator must be either =, !=, >, or <.
4986
+ # For example, if you are filtering Compute Engine instances, you can exclude
4987
+ # instances named example-instance by specifying name != example-instance.
4988
+ # You can also filter nested fields. For example, you could specify scheduling.
4989
+ # automaticRestart = false to include instances only if they are not scheduled
4990
+ # for automatic restarts. You can use filtering on nested fields to filter based
4991
+ # on resource labels.
5066
4992
  # To filter on multiple expressions, provide each separate expression within
5067
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5068
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5069
- # resources must match all expressions to pass the filters.
4993
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
4994
+ # Intel Skylake"). By default, each expression is an AND expression. However,
4995
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
4996
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
4997
+ # automaticRestart = true).
5070
4998
  # @param [Fixnum] max_results
5071
4999
  # The maximum number of results per page that should be returned. If the number
5072
5000
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5233,25 +5161,22 @@ module Google
5233
5161
  # @param [String] project
5234
5162
  # Project ID for this request.
5235
5163
  # @param [String] filter
5236
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5237
- # must be in the format: field_name comparison_string literal_string.
5238
- # The field_name is the name of the field you want to compare. Only atomic field
5239
- # types are supported (string, number, boolean). The comparison_string must be
5240
- # either eq (equals) or ne (not equals). The literal_string is the string value
5241
- # to filter to. The literal value must be valid for the type of field you are
5242
- # filtering by (string, number, boolean). For string fields, the literal value
5243
- # is interpreted as a regular expression using RE2 syntax. The literal value
5244
- # must match the entire field.
5245
- # For example, to filter for instances that do not have a name of example-
5246
- # instance, you would use name ne example-instance.
5247
- # You can filter on nested fields. For example, you could filter on instances
5248
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5249
- # nested fields to take advantage of labels to organize and search for results
5250
- # based on label values.
5164
+ # A filter expression that filters resources listed in the response. The
5165
+ # expression must specify the field name, a comparison operator, and the value
5166
+ # that you want to use for filtering. The value must be a string, a number, or a
5167
+ # boolean. The comparison operator must be either =, !=, >, or <.
5168
+ # For example, if you are filtering Compute Engine instances, you can exclude
5169
+ # instances named example-instance by specifying name != example-instance.
5170
+ # You can also filter nested fields. For example, you could specify scheduling.
5171
+ # automaticRestart = false to include instances only if they are not scheduled
5172
+ # for automatic restarts. You can use filtering on nested fields to filter based
5173
+ # on resource labels.
5251
5174
  # To filter on multiple expressions, provide each separate expression within
5252
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5253
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5254
- # resources must match all expressions to pass the filters.
5175
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5176
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5177
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5178
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5179
+ # automaticRestart = true).
5255
5180
  # @param [Fixnum] max_results
5256
5181
  # The maximum number of results per page that should be returned. If the number
5257
5182
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5535,25 +5460,22 @@ module Google
5535
5460
  # @param [String] zone
5536
5461
  # The name of the zone where the managed instance group is located.
5537
5462
  # @param [String] filter
5538
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5539
- # must be in the format: field_name comparison_string literal_string.
5540
- # The field_name is the name of the field you want to compare. Only atomic field
5541
- # types are supported (string, number, boolean). The comparison_string must be
5542
- # either eq (equals) or ne (not equals). The literal_string is the string value
5543
- # to filter to. The literal value must be valid for the type of field you are
5544
- # filtering by (string, number, boolean). For string fields, the literal value
5545
- # is interpreted as a regular expression using RE2 syntax. The literal value
5546
- # must match the entire field.
5547
- # For example, to filter for instances that do not have a name of example-
5548
- # instance, you would use name ne example-instance.
5549
- # You can filter on nested fields. For example, you could filter on instances
5550
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5551
- # nested fields to take advantage of labels to organize and search for results
5552
- # based on label values.
5463
+ # A filter expression that filters resources listed in the response. The
5464
+ # expression must specify the field name, a comparison operator, and the value
5465
+ # that you want to use for filtering. The value must be a string, a number, or a
5466
+ # boolean. The comparison operator must be either =, !=, >, or <.
5467
+ # For example, if you are filtering Compute Engine instances, you can exclude
5468
+ # instances named example-instance by specifying name != example-instance.
5469
+ # You can also filter nested fields. For example, you could specify scheduling.
5470
+ # automaticRestart = false to include instances only if they are not scheduled
5471
+ # for automatic restarts. You can use filtering on nested fields to filter based
5472
+ # on resource labels.
5553
5473
  # To filter on multiple expressions, provide each separate expression within
5554
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5555
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5556
- # resources must match all expressions to pass the filters.
5474
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5475
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5476
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5477
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5478
+ # automaticRestart = true).
5557
5479
  # @param [Fixnum] max_results
5558
5480
  # The maximum number of results per page that should be returned. If the number
5559
5481
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5973,25 +5895,22 @@ module Google
5973
5895
  # @param [String] project
5974
5896
  # Project ID for this request.
5975
5897
  # @param [String] filter
5976
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5977
- # must be in the format: field_name comparison_string literal_string.
5978
- # The field_name is the name of the field you want to compare. Only atomic field
5979
- # types are supported (string, number, boolean). The comparison_string must be
5980
- # either eq (equals) or ne (not equals). The literal_string is the string value
5981
- # to filter to. The literal value must be valid for the type of field you are
5982
- # filtering by (string, number, boolean). For string fields, the literal value
5983
- # is interpreted as a regular expression using RE2 syntax. The literal value
5984
- # must match the entire field.
5985
- # For example, to filter for instances that do not have a name of example-
5986
- # instance, you would use name ne example-instance.
5987
- # You can filter on nested fields. For example, you could filter on instances
5988
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5989
- # nested fields to take advantage of labels to organize and search for results
5990
- # based on label values.
5898
+ # A filter expression that filters resources listed in the response. The
5899
+ # expression must specify the field name, a comparison operator, and the value
5900
+ # that you want to use for filtering. The value must be a string, a number, or a
5901
+ # boolean. The comparison operator must be either =, !=, >, or <.
5902
+ # For example, if you are filtering Compute Engine instances, you can exclude
5903
+ # instances named example-instance by specifying name != example-instance.
5904
+ # You can also filter nested fields. For example, you could specify scheduling.
5905
+ # automaticRestart = false to include instances only if they are not scheduled
5906
+ # for automatic restarts. You can use filtering on nested fields to filter based
5907
+ # on resource labels.
5991
5908
  # To filter on multiple expressions, provide each separate expression within
5992
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5993
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5994
- # resources must match all expressions to pass the filters.
5909
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5910
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5911
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5912
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5913
+ # automaticRestart = true).
5995
5914
  # @param [Fixnum] max_results
5996
5915
  # The maximum number of results per page that should be returned. If the number
5997
5916
  # of available results is larger than maxResults, Compute Engine returns a
@@ -6203,25 +6122,22 @@ module Google
6203
6122
  # @param [String] zone
6204
6123
  # The name of the zone where the instance group is located.
6205
6124
  # @param [String] filter
6206
- # Sets a filter `expression` for filtering listed resources. Your `expression`
6207
- # must be in the format: field_name comparison_string literal_string.
6208
- # The field_name is the name of the field you want to compare. Only atomic field
6209
- # types are supported (string, number, boolean). The comparison_string must be
6210
- # either eq (equals) or ne (not equals). The literal_string is the string value
6211
- # to filter to. The literal value must be valid for the type of field you are
6212
- # filtering by (string, number, boolean). For string fields, the literal value
6213
- # is interpreted as a regular expression using RE2 syntax. The literal value
6214
- # must match the entire field.
6215
- # For example, to filter for instances that do not have a name of example-
6216
- # instance, you would use name ne example-instance.
6217
- # You can filter on nested fields. For example, you could filter on instances
6218
- # that have set the scheduling.automaticRestart field to true. Use filtering on
6219
- # nested fields to take advantage of labels to organize and search for results
6220
- # based on label values.
6125
+ # A filter expression that filters resources listed in the response. The
6126
+ # expression must specify the field name, a comparison operator, and the value
6127
+ # that you want to use for filtering. The value must be a string, a number, or a
6128
+ # boolean. The comparison operator must be either =, !=, >, or <.
6129
+ # For example, if you are filtering Compute Engine instances, you can exclude
6130
+ # instances named example-instance by specifying name != example-instance.
6131
+ # You can also filter nested fields. For example, you could specify scheduling.
6132
+ # automaticRestart = false to include instances only if they are not scheduled
6133
+ # for automatic restarts. You can use filtering on nested fields to filter based
6134
+ # on resource labels.
6221
6135
  # To filter on multiple expressions, provide each separate expression within
6222
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
6223
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
6224
- # resources must match all expressions to pass the filters.
6136
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
6137
+ # Intel Skylake"). By default, each expression is an AND expression. However,
6138
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
6139
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
6140
+ # automaticRestart = true).
6225
6141
  # @param [Fixnum] max_results
6226
6142
  # The maximum number of results per page that should be returned. If the number
6227
6143
  # of available results is larger than maxResults, Compute Engine returns a
@@ -6286,25 +6202,22 @@ module Google
6286
6202
  # included instances.
6287
6203
  # @param [Google::Apis::ComputeV1::InstanceGroupsListInstancesRequest] instance_groups_list_instances_request_object
6288
6204
  # @param [String] filter
6289
- # Sets a filter `expression` for filtering listed resources. Your `expression`
6290
- # must be in the format: field_name comparison_string literal_string.
6291
- # The field_name is the name of the field you want to compare. Only atomic field
6292
- # types are supported (string, number, boolean). The comparison_string must be
6293
- # either eq (equals) or ne (not equals). The literal_string is the string value
6294
- # to filter to. The literal value must be valid for the type of field you are
6295
- # filtering by (string, number, boolean). For string fields, the literal value
6296
- # is interpreted as a regular expression using RE2 syntax. The literal value
6297
- # must match the entire field.
6298
- # For example, to filter for instances that do not have a name of example-
6299
- # instance, you would use name ne example-instance.
6300
- # You can filter on nested fields. For example, you could filter on instances
6301
- # that have set the scheduling.automaticRestart field to true. Use filtering on
6302
- # nested fields to take advantage of labels to organize and search for results
6303
- # based on label values.
6205
+ # A filter expression that filters resources listed in the response. The
6206
+ # expression must specify the field name, a comparison operator, and the value
6207
+ # that you want to use for filtering. The value must be a string, a number, or a
6208
+ # boolean. The comparison operator must be either =, !=, >, or <.
6209
+ # For example, if you are filtering Compute Engine instances, you can exclude
6210
+ # instances named example-instance by specifying name != example-instance.
6211
+ # You can also filter nested fields. For example, you could specify scheduling.
6212
+ # automaticRestart = false to include instances only if they are not scheduled
6213
+ # for automatic restarts. You can use filtering on nested fields to filter based
6214
+ # on resource labels.
6304
6215
  # To filter on multiple expressions, provide each separate expression within
6305
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
6306
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
6307
- # resources must match all expressions to pass the filters.
6216
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
6217
+ # Intel Skylake"). By default, each expression is an AND expression. However,
6218
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
6219
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
6220
+ # automaticRestart = true).
6308
6221
  # @param [Fixnum] max_results
6309
6222
  # The maximum number of results per page that should be returned. If the number
6310
6223
  # of available results is larger than maxResults, Compute Engine returns a
@@ -6627,25 +6540,22 @@ module Google
6627
6540
  # @param [String] project
6628
6541
  # Project ID for this request.
6629
6542
  # @param [String] filter
6630
- # Sets a filter `expression` for filtering listed resources. Your `expression`
6631
- # must be in the format: field_name comparison_string literal_string.
6632
- # The field_name is the name of the field you want to compare. Only atomic field
6633
- # types are supported (string, number, boolean). The comparison_string must be
6634
- # either eq (equals) or ne (not equals). The literal_string is the string value
6635
- # to filter to. The literal value must be valid for the type of field you are
6636
- # filtering by (string, number, boolean). For string fields, the literal value
6637
- # is interpreted as a regular expression using RE2 syntax. The literal value
6638
- # must match the entire field.
6639
- # For example, to filter for instances that do not have a name of example-
6640
- # instance, you would use name ne example-instance.
6641
- # You can filter on nested fields. For example, you could filter on instances
6642
- # that have set the scheduling.automaticRestart field to true. Use filtering on
6643
- # nested fields to take advantage of labels to organize and search for results
6644
- # based on label values.
6543
+ # A filter expression that filters resources listed in the response. The
6544
+ # expression must specify the field name, a comparison operator, and the value
6545
+ # that you want to use for filtering. The value must be a string, a number, or a
6546
+ # boolean. The comparison operator must be either =, !=, >, or <.
6547
+ # For example, if you are filtering Compute Engine instances, you can exclude
6548
+ # instances named example-instance by specifying name != example-instance.
6549
+ # You can also filter nested fields. For example, you could specify scheduling.
6550
+ # automaticRestart = false to include instances only if they are not scheduled
6551
+ # for automatic restarts. You can use filtering on nested fields to filter based
6552
+ # on resource labels.
6645
6553
  # To filter on multiple expressions, provide each separate expression within
6646
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
6647
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
6648
- # resources must match all expressions to pass the filters.
6554
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
6555
+ # Intel Skylake"). By default, each expression is an AND expression. However,
6556
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
6557
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
6558
+ # automaticRestart = true).
6649
6559
  # @param [Fixnum] max_results
6650
6560
  # The maximum number of results per page that should be returned. If the number
6651
6561
  # of available results is larger than maxResults, Compute Engine returns a
@@ -6762,25 +6672,22 @@ module Google
6762
6672
  # @param [String] project
6763
6673
  # Project ID for this request.
6764
6674
  # @param [String] filter
6765
- # Sets a filter `expression` for filtering listed resources. Your `expression`
6766
- # must be in the format: field_name comparison_string literal_string.
6767
- # The field_name is the name of the field you want to compare. Only atomic field
6768
- # types are supported (string, number, boolean). The comparison_string must be
6769
- # either eq (equals) or ne (not equals). The literal_string is the string value
6770
- # to filter to. The literal value must be valid for the type of field you are
6771
- # filtering by (string, number, boolean). For string fields, the literal value
6772
- # is interpreted as a regular expression using RE2 syntax. The literal value
6773
- # must match the entire field.
6774
- # For example, to filter for instances that do not have a name of example-
6775
- # instance, you would use name ne example-instance.
6776
- # You can filter on nested fields. For example, you could filter on instances
6777
- # that have set the scheduling.automaticRestart field to true. Use filtering on
6778
- # nested fields to take advantage of labels to organize and search for results
6779
- # based on label values.
6675
+ # A filter expression that filters resources listed in the response. The
6676
+ # expression must specify the field name, a comparison operator, and the value
6677
+ # that you want to use for filtering. The value must be a string, a number, or a
6678
+ # boolean. The comparison operator must be either =, !=, >, or <.
6679
+ # For example, if you are filtering Compute Engine instances, you can exclude
6680
+ # instances named example-instance by specifying name != example-instance.
6681
+ # You can also filter nested fields. For example, you could specify scheduling.
6682
+ # automaticRestart = false to include instances only if they are not scheduled
6683
+ # for automatic restarts. You can use filtering on nested fields to filter based
6684
+ # on resource labels.
6780
6685
  # To filter on multiple expressions, provide each separate expression within
6781
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
6782
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
6783
- # resources must match all expressions to pass the filters.
6686
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
6687
+ # Intel Skylake"). By default, each expression is an AND expression. However,
6688
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
6689
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
6690
+ # automaticRestart = true).
6784
6691
  # @param [Fixnum] max_results
6785
6692
  # The maximum number of results per page that should be returned. If the number
6786
6693
  # of available results is larger than maxResults, Compute Engine returns a
@@ -7214,25 +7121,22 @@ module Google
7214
7121
  # @param [String] zone
7215
7122
  # The name of the zone for this request.
7216
7123
  # @param [String] filter
7217
- # Sets a filter `expression` for filtering listed resources. Your `expression`
7218
- # must be in the format: field_name comparison_string literal_string.
7219
- # The field_name is the name of the field you want to compare. Only atomic field
7220
- # types are supported (string, number, boolean). The comparison_string must be
7221
- # either eq (equals) or ne (not equals). The literal_string is the string value
7222
- # to filter to. The literal value must be valid for the type of field you are
7223
- # filtering by (string, number, boolean). For string fields, the literal value
7224
- # is interpreted as a regular expression using RE2 syntax. The literal value
7225
- # must match the entire field.
7226
- # For example, to filter for instances that do not have a name of example-
7227
- # instance, you would use name ne example-instance.
7228
- # You can filter on nested fields. For example, you could filter on instances
7229
- # that have set the scheduling.automaticRestart field to true. Use filtering on
7230
- # nested fields to take advantage of labels to organize and search for results
7231
- # based on label values.
7124
+ # A filter expression that filters resources listed in the response. The
7125
+ # expression must specify the field name, a comparison operator, and the value
7126
+ # that you want to use for filtering. The value must be a string, a number, or a
7127
+ # boolean. The comparison operator must be either =, !=, >, or <.
7128
+ # For example, if you are filtering Compute Engine instances, you can exclude
7129
+ # instances named example-instance by specifying name != example-instance.
7130
+ # You can also filter nested fields. For example, you could specify scheduling.
7131
+ # automaticRestart = false to include instances only if they are not scheduled
7132
+ # for automatic restarts. You can use filtering on nested fields to filter based
7133
+ # on resource labels.
7232
7134
  # To filter on multiple expressions, provide each separate expression within
7233
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
7234
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
7235
- # resources must match all expressions to pass the filters.
7135
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
7136
+ # Intel Skylake"). By default, each expression is an AND expression. However,
7137
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
7138
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
7139
+ # automaticRestart = true).
7236
7140
  # @param [Fixnum] max_results
7237
7141
  # The maximum number of results per page that should be returned. If the number
7238
7142
  # of available results is larger than maxResults, Compute Engine returns a
@@ -7297,25 +7201,22 @@ module Google
7297
7201
  # Name of the target instance scoping this request, or '-' if the request should
7298
7202
  # span over all instances in the container.
7299
7203
  # @param [String] filter
7300
- # Sets a filter `expression` for filtering listed resources. Your `expression`
7301
- # must be in the format: field_name comparison_string literal_string.
7302
- # The field_name is the name of the field you want to compare. Only atomic field
7303
- # types are supported (string, number, boolean). The comparison_string must be
7304
- # either eq (equals) or ne (not equals). The literal_string is the string value
7305
- # to filter to. The literal value must be valid for the type of field you are
7306
- # filtering by (string, number, boolean). For string fields, the literal value
7307
- # is interpreted as a regular expression using RE2 syntax. The literal value
7308
- # must match the entire field.
7309
- # For example, to filter for instances that do not have a name of example-
7310
- # instance, you would use name ne example-instance.
7311
- # You can filter on nested fields. For example, you could filter on instances
7312
- # that have set the scheduling.automaticRestart field to true. Use filtering on
7313
- # nested fields to take advantage of labels to organize and search for results
7314
- # based on label values.
7204
+ # A filter expression that filters resources listed in the response. The
7205
+ # expression must specify the field name, a comparison operator, and the value
7206
+ # that you want to use for filtering. The value must be a string, a number, or a
7207
+ # boolean. The comparison operator must be either =, !=, >, or <.
7208
+ # For example, if you are filtering Compute Engine instances, you can exclude
7209
+ # instances named example-instance by specifying name != example-instance.
7210
+ # You can also filter nested fields. For example, you could specify scheduling.
7211
+ # automaticRestart = false to include instances only if they are not scheduled
7212
+ # for automatic restarts. You can use filtering on nested fields to filter based
7213
+ # on resource labels.
7315
7214
  # To filter on multiple expressions, provide each separate expression within
7316
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
7317
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
7318
- # resources must match all expressions to pass the filters.
7215
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
7216
+ # Intel Skylake"). By default, each expression is an AND expression. However,
7217
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
7218
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
7219
+ # automaticRestart = true).
7319
7220
  # @param [Fixnum] max_results
7320
7221
  # The maximum number of results per page that should be returned. If the number
7321
7222
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8223,29 +8124,85 @@ module Google
8223
8124
  execute_or_queue_command(command, &block)
8224
8125
  end
8225
8126
 
8127
+ # Updates an instance's network interface. This method follows PATCH semantics.
8128
+ # @param [String] project
8129
+ # Project ID for this request.
8130
+ # @param [String] zone
8131
+ # The name of the zone for this request.
8132
+ # @param [String] instance
8133
+ # The instance name for this request.
8134
+ # @param [String] network_interface
8135
+ # The name of the network interface to update.
8136
+ # @param [Google::Apis::ComputeV1::NetworkInterface] network_interface_object
8137
+ # @param [String] request_id
8138
+ # An optional request ID to identify requests. Specify a unique request ID so
8139
+ # that if you must retry your request, the server will know to ignore the
8140
+ # request if it has already been completed.
8141
+ # For example, consider a situation where you make an initial request and the
8142
+ # request times out. If you make the request again with the same request ID, the
8143
+ # server can check if original operation with the same request ID was received,
8144
+ # and if so, will ignore the second request. This prevents clients from
8145
+ # accidentally creating duplicate commitments.
8146
+ # The request ID must be a valid UUID with the exception that zero UUID is not
8147
+ # supported (00000000-0000-0000-0000-000000000000).
8148
+ # @param [String] fields
8149
+ # Selector specifying which fields to include in a partial response.
8150
+ # @param [String] quota_user
8151
+ # Available to use for quota purposes for server-side applications. Can be any
8152
+ # arbitrary string assigned to a user, but should not exceed 40 characters.
8153
+ # Overrides userIp if both are provided.
8154
+ # @param [String] user_ip
8155
+ # IP address of the site where the request originates. Use this if you want to
8156
+ # enforce per-user limits.
8157
+ # @param [Google::Apis::RequestOptions] options
8158
+ # Request-specific options
8159
+ #
8160
+ # @yield [result, err] Result & error if block supplied
8161
+ # @yieldparam result [Google::Apis::ComputeV1::Operation] parsed result object
8162
+ # @yieldparam err [StandardError] error object if request failed
8163
+ #
8164
+ # @return [Google::Apis::ComputeV1::Operation]
8165
+ #
8166
+ # @raise [Google::Apis::ServerError] An error occurred on the server and the request can be retried
8167
+ # @raise [Google::Apis::ClientError] The request is invalid and should not be retried without modification
8168
+ # @raise [Google::Apis::AuthorizationError] Authorization is required
8169
+ def update_instance_network_interface(project, zone, instance, network_interface, network_interface_object = nil, request_id: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block)
8170
+ command = make_simple_command(:patch, '{project}/zones/{zone}/instances/{instance}/updateNetworkInterface', options)
8171
+ command.request_representation = Google::Apis::ComputeV1::NetworkInterface::Representation
8172
+ command.request_object = network_interface_object
8173
+ command.response_representation = Google::Apis::ComputeV1::Operation::Representation
8174
+ command.response_class = Google::Apis::ComputeV1::Operation
8175
+ command.params['project'] = project unless project.nil?
8176
+ command.params['zone'] = zone unless zone.nil?
8177
+ command.params['instance'] = instance unless instance.nil?
8178
+ command.query['networkInterface'] = network_interface unless network_interface.nil?
8179
+ command.query['requestId'] = request_id unless request_id.nil?
8180
+ command.query['fields'] = fields unless fields.nil?
8181
+ command.query['quotaUser'] = quota_user unless quota_user.nil?
8182
+ command.query['userIp'] = user_ip unless user_ip.nil?
8183
+ execute_or_queue_command(command, &block)
8184
+ end
8185
+
8226
8186
  # Retrieves an aggregated list of interconnect attachments.
8227
8187
  # @param [String] project
8228
8188
  # Project ID for this request.
8229
8189
  # @param [String] filter
8230
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8231
- # must be in the format: field_name comparison_string literal_string.
8232
- # The field_name is the name of the field you want to compare. Only atomic field
8233
- # types are supported (string, number, boolean). The comparison_string must be
8234
- # either eq (equals) or ne (not equals). The literal_string is the string value
8235
- # to filter to. The literal value must be valid for the type of field you are
8236
- # filtering by (string, number, boolean). For string fields, the literal value
8237
- # is interpreted as a regular expression using RE2 syntax. The literal value
8238
- # must match the entire field.
8239
- # For example, to filter for instances that do not have a name of example-
8240
- # instance, you would use name ne example-instance.
8241
- # You can filter on nested fields. For example, you could filter on instances
8242
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8243
- # nested fields to take advantage of labels to organize and search for results
8244
- # based on label values.
8190
+ # A filter expression that filters resources listed in the response. The
8191
+ # expression must specify the field name, a comparison operator, and the value
8192
+ # that you want to use for filtering. The value must be a string, a number, or a
8193
+ # boolean. The comparison operator must be either =, !=, >, or <.
8194
+ # For example, if you are filtering Compute Engine instances, you can exclude
8195
+ # instances named example-instance by specifying name != example-instance.
8196
+ # You can also filter nested fields. For example, you could specify scheduling.
8197
+ # automaticRestart = false to include instances only if they are not scheduled
8198
+ # for automatic restarts. You can use filtering on nested fields to filter based
8199
+ # on resource labels.
8245
8200
  # To filter on multiple expressions, provide each separate expression within
8246
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8247
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8248
- # resources must match all expressions to pass the filters.
8201
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8202
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8203
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8204
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8205
+ # automaticRestart = true).
8249
8206
  # @param [Fixnum] max_results
8250
8207
  # The maximum number of results per page that should be returned. If the number
8251
8208
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8454,25 +8411,22 @@ module Google
8454
8411
  # @param [String] region
8455
8412
  # Name of the region for this request.
8456
8413
  # @param [String] filter
8457
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8458
- # must be in the format: field_name comparison_string literal_string.
8459
- # The field_name is the name of the field you want to compare. Only atomic field
8460
- # types are supported (string, number, boolean). The comparison_string must be
8461
- # either eq (equals) or ne (not equals). The literal_string is the string value
8462
- # to filter to. The literal value must be valid for the type of field you are
8463
- # filtering by (string, number, boolean). For string fields, the literal value
8464
- # is interpreted as a regular expression using RE2 syntax. The literal value
8465
- # must match the entire field.
8466
- # For example, to filter for instances that do not have a name of example-
8467
- # instance, you would use name ne example-instance.
8468
- # You can filter on nested fields. For example, you could filter on instances
8469
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8470
- # nested fields to take advantage of labels to organize and search for results
8471
- # based on label values.
8414
+ # A filter expression that filters resources listed in the response. The
8415
+ # expression must specify the field name, a comparison operator, and the value
8416
+ # that you want to use for filtering. The value must be a string, a number, or a
8417
+ # boolean. The comparison operator must be either =, !=, >, or <.
8418
+ # For example, if you are filtering Compute Engine instances, you can exclude
8419
+ # instances named example-instance by specifying name != example-instance.
8420
+ # You can also filter nested fields. For example, you could specify scheduling.
8421
+ # automaticRestart = false to include instances only if they are not scheduled
8422
+ # for automatic restarts. You can use filtering on nested fields to filter based
8423
+ # on resource labels.
8472
8424
  # To filter on multiple expressions, provide each separate expression within
8473
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8474
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8475
- # resources must match all expressions to pass the filters.
8425
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8426
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8427
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8428
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8429
+ # automaticRestart = true).
8476
8430
  # @param [Fixnum] max_results
8477
8431
  # The maximum number of results per page that should be returned. If the number
8478
8432
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8571,25 +8525,22 @@ module Google
8571
8525
  # @param [String] project
8572
8526
  # Project ID for this request.
8573
8527
  # @param [String] filter
8574
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8575
- # must be in the format: field_name comparison_string literal_string.
8576
- # The field_name is the name of the field you want to compare. Only atomic field
8577
- # types are supported (string, number, boolean). The comparison_string must be
8578
- # either eq (equals) or ne (not equals). The literal_string is the string value
8579
- # to filter to. The literal value must be valid for the type of field you are
8580
- # filtering by (string, number, boolean). For string fields, the literal value
8581
- # is interpreted as a regular expression using RE2 syntax. The literal value
8582
- # must match the entire field.
8583
- # For example, to filter for instances that do not have a name of example-
8584
- # instance, you would use name ne example-instance.
8585
- # You can filter on nested fields. For example, you could filter on instances
8586
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8587
- # nested fields to take advantage of labels to organize and search for results
8588
- # based on label values.
8528
+ # A filter expression that filters resources listed in the response. The
8529
+ # expression must specify the field name, a comparison operator, and the value
8530
+ # that you want to use for filtering. The value must be a string, a number, or a
8531
+ # boolean. The comparison operator must be either =, !=, >, or <.
8532
+ # For example, if you are filtering Compute Engine instances, you can exclude
8533
+ # instances named example-instance by specifying name != example-instance.
8534
+ # You can also filter nested fields. For example, you could specify scheduling.
8535
+ # automaticRestart = false to include instances only if they are not scheduled
8536
+ # for automatic restarts. You can use filtering on nested fields to filter based
8537
+ # on resource labels.
8589
8538
  # To filter on multiple expressions, provide each separate expression within
8590
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8591
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8592
- # resources must match all expressions to pass the filters.
8539
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8540
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8541
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8542
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8543
+ # automaticRestart = true).
8593
8544
  # @param [Fixnum] max_results
8594
8545
  # The maximum number of results per page that should be returned. If the number
8595
8546
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8787,25 +8738,22 @@ module Google
8787
8738
  # @param [String] project
8788
8739
  # Project ID for this request.
8789
8740
  # @param [String] filter
8790
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8791
- # must be in the format: field_name comparison_string literal_string.
8792
- # The field_name is the name of the field you want to compare. Only atomic field
8793
- # types are supported (string, number, boolean). The comparison_string must be
8794
- # either eq (equals) or ne (not equals). The literal_string is the string value
8795
- # to filter to. The literal value must be valid for the type of field you are
8796
- # filtering by (string, number, boolean). For string fields, the literal value
8797
- # is interpreted as a regular expression using RE2 syntax. The literal value
8798
- # must match the entire field.
8799
- # For example, to filter for instances that do not have a name of example-
8800
- # instance, you would use name ne example-instance.
8801
- # You can filter on nested fields. For example, you could filter on instances
8802
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8803
- # nested fields to take advantage of labels to organize and search for results
8804
- # based on label values.
8741
+ # A filter expression that filters resources listed in the response. The
8742
+ # expression must specify the field name, a comparison operator, and the value
8743
+ # that you want to use for filtering. The value must be a string, a number, or a
8744
+ # boolean. The comparison operator must be either =, !=, >, or <.
8745
+ # For example, if you are filtering Compute Engine instances, you can exclude
8746
+ # instances named example-instance by specifying name != example-instance.
8747
+ # You can also filter nested fields. For example, you could specify scheduling.
8748
+ # automaticRestart = false to include instances only if they are not scheduled
8749
+ # for automatic restarts. You can use filtering on nested fields to filter based
8750
+ # on resource labels.
8805
8751
  # To filter on multiple expressions, provide each separate expression within
8806
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8807
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8808
- # resources must match all expressions to pass the filters.
8752
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8753
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8754
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8755
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8756
+ # automaticRestart = true).
8809
8757
  # @param [Fixnum] max_results
8810
8758
  # The maximum number of results per page that should be returned. If the number
8811
8759
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8956,25 +8904,22 @@ module Google
8956
8904
  # @param [String] project
8957
8905
  # Project ID for this request.
8958
8906
  # @param [String] filter
8959
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8960
- # must be in the format: field_name comparison_string literal_string.
8961
- # The field_name is the name of the field you want to compare. Only atomic field
8962
- # types are supported (string, number, boolean). The comparison_string must be
8963
- # either eq (equals) or ne (not equals). The literal_string is the string value
8964
- # to filter to. The literal value must be valid for the type of field you are
8965
- # filtering by (string, number, boolean). For string fields, the literal value
8966
- # is interpreted as a regular expression using RE2 syntax. The literal value
8967
- # must match the entire field.
8968
- # For example, to filter for instances that do not have a name of example-
8969
- # instance, you would use name ne example-instance.
8970
- # You can filter on nested fields. For example, you could filter on instances
8971
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8972
- # nested fields to take advantage of labels to organize and search for results
8973
- # based on label values.
8907
+ # A filter expression that filters resources listed in the response. The
8908
+ # expression must specify the field name, a comparison operator, and the value
8909
+ # that you want to use for filtering. The value must be a string, a number, or a
8910
+ # boolean. The comparison operator must be either =, !=, >, or <.
8911
+ # For example, if you are filtering Compute Engine instances, you can exclude
8912
+ # instances named example-instance by specifying name != example-instance.
8913
+ # You can also filter nested fields. For example, you could specify scheduling.
8914
+ # automaticRestart = false to include instances only if they are not scheduled
8915
+ # for automatic restarts. You can use filtering on nested fields to filter based
8916
+ # on resource labels.
8974
8917
  # To filter on multiple expressions, provide each separate expression within
8975
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8976
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8977
- # resources must match all expressions to pass the filters.
8918
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8919
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8920
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8921
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8922
+ # automaticRestart = true).
8978
8923
  # @param [Fixnum] max_results
8979
8924
  # The maximum number of results per page that should be returned. If the number
8980
8925
  # of available results is larger than maxResults, Compute Engine returns a
@@ -9076,25 +9021,22 @@ module Google
9076
9021
  # @param [String] zone
9077
9022
  # The name of the zone for this request.
9078
9023
  # @param [String] filter
9079
- # Sets a filter `expression` for filtering listed resources. Your `expression`
9080
- # must be in the format: field_name comparison_string literal_string.
9081
- # The field_name is the name of the field you want to compare. Only atomic field
9082
- # types are supported (string, number, boolean). The comparison_string must be
9083
- # either eq (equals) or ne (not equals). The literal_string is the string value
9084
- # to filter to. The literal value must be valid for the type of field you are
9085
- # filtering by (string, number, boolean). For string fields, the literal value
9086
- # is interpreted as a regular expression using RE2 syntax. The literal value
9087
- # must match the entire field.
9088
- # For example, to filter for instances that do not have a name of example-
9089
- # instance, you would use name ne example-instance.
9090
- # You can filter on nested fields. For example, you could filter on instances
9091
- # that have set the scheduling.automaticRestart field to true. Use filtering on
9092
- # nested fields to take advantage of labels to organize and search for results
9093
- # based on label values.
9024
+ # A filter expression that filters resources listed in the response. The
9025
+ # expression must specify the field name, a comparison operator, and the value
9026
+ # that you want to use for filtering. The value must be a string, a number, or a
9027
+ # boolean. The comparison operator must be either =, !=, >, or <.
9028
+ # For example, if you are filtering Compute Engine instances, you can exclude
9029
+ # instances named example-instance by specifying name != example-instance.
9030
+ # You can also filter nested fields. For example, you could specify scheduling.
9031
+ # automaticRestart = false to include instances only if they are not scheduled
9032
+ # for automatic restarts. You can use filtering on nested fields to filter based
9033
+ # on resource labels.
9094
9034
  # To filter on multiple expressions, provide each separate expression within
9095
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
9096
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
9097
- # resources must match all expressions to pass the filters.
9035
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
9036
+ # Intel Skylake"). By default, each expression is an AND expression. However,
9037
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
9038
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
9039
+ # automaticRestart = true).
9098
9040
  # @param [Fixnum] max_results
9099
9041
  # The maximum number of results per page that should be returned. If the number
9100
9042
  # of available results is larger than maxResults, Compute Engine returns a
@@ -9346,25 +9288,22 @@ module Google
9346
9288
  # @param [String] project
9347
9289
  # Project ID for this request.
9348
9290
  # @param [String] filter
9349
- # Sets a filter `expression` for filtering listed resources. Your `expression`
9350
- # must be in the format: field_name comparison_string literal_string.
9351
- # The field_name is the name of the field you want to compare. Only atomic field
9352
- # types are supported (string, number, boolean). The comparison_string must be
9353
- # either eq (equals) or ne (not equals). The literal_string is the string value
9354
- # to filter to. The literal value must be valid for the type of field you are
9355
- # filtering by (string, number, boolean). For string fields, the literal value
9356
- # is interpreted as a regular expression using RE2 syntax. The literal value
9357
- # must match the entire field.
9358
- # For example, to filter for instances that do not have a name of example-
9359
- # instance, you would use name ne example-instance.
9360
- # You can filter on nested fields. For example, you could filter on instances
9361
- # that have set the scheduling.automaticRestart field to true. Use filtering on
9362
- # nested fields to take advantage of labels to organize and search for results
9363
- # based on label values.
9291
+ # A filter expression that filters resources listed in the response. The
9292
+ # expression must specify the field name, a comparison operator, and the value
9293
+ # that you want to use for filtering. The value must be a string, a number, or a
9294
+ # boolean. The comparison operator must be either =, !=, >, or <.
9295
+ # For example, if you are filtering Compute Engine instances, you can exclude
9296
+ # instances named example-instance by specifying name != example-instance.
9297
+ # You can also filter nested fields. For example, you could specify scheduling.
9298
+ # automaticRestart = false to include instances only if they are not scheduled
9299
+ # for automatic restarts. You can use filtering on nested fields to filter based
9300
+ # on resource labels.
9364
9301
  # To filter on multiple expressions, provide each separate expression within
9365
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
9366
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
9367
- # resources must match all expressions to pass the filters.
9302
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
9303
+ # Intel Skylake"). By default, each expression is an AND expression. However,
9304
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
9305
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
9306
+ # automaticRestart = true).
9368
9307
  # @param [Fixnum] max_results
9369
9308
  # The maximum number of results per page that should be returned. If the number
9370
9309
  # of available results is larger than maxResults, Compute Engine returns a
@@ -10289,25 +10228,22 @@ module Google
10289
10228
  # @param [String] region
10290
10229
  # Name of the region scoping this request.
10291
10230
  # @param [String] filter
10292
- # Sets a filter `expression` for filtering listed resources. Your `expression`
10293
- # must be in the format: field_name comparison_string literal_string.
10294
- # The field_name is the name of the field you want to compare. Only atomic field
10295
- # types are supported (string, number, boolean). The comparison_string must be
10296
- # either eq (equals) or ne (not equals). The literal_string is the string value
10297
- # to filter to. The literal value must be valid for the type of field you are
10298
- # filtering by (string, number, boolean). For string fields, the literal value
10299
- # is interpreted as a regular expression using RE2 syntax. The literal value
10300
- # must match the entire field.
10301
- # For example, to filter for instances that do not have a name of example-
10302
- # instance, you would use name ne example-instance.
10303
- # You can filter on nested fields. For example, you could filter on instances
10304
- # that have set the scheduling.automaticRestart field to true. Use filtering on
10305
- # nested fields to take advantage of labels to organize and search for results
10306
- # based on label values.
10231
+ # A filter expression that filters resources listed in the response. The
10232
+ # expression must specify the field name, a comparison operator, and the value
10233
+ # that you want to use for filtering. The value must be a string, a number, or a
10234
+ # boolean. The comparison operator must be either =, !=, >, or <.
10235
+ # For example, if you are filtering Compute Engine instances, you can exclude
10236
+ # instances named example-instance by specifying name != example-instance.
10237
+ # You can also filter nested fields. For example, you could specify scheduling.
10238
+ # automaticRestart = false to include instances only if they are not scheduled
10239
+ # for automatic restarts. You can use filtering on nested fields to filter based
10240
+ # on resource labels.
10307
10241
  # To filter on multiple expressions, provide each separate expression within
10308
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
10309
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
10310
- # resources must match all expressions to pass the filters.
10242
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
10243
+ # Intel Skylake"). By default, each expression is an AND expression. However,
10244
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
10245
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
10246
+ # automaticRestart = true).
10311
10247
  # @param [Fixnum] max_results
10312
10248
  # The maximum number of results per page that should be returned. If the number
10313
10249
  # of available results is larger than maxResults, Compute Engine returns a
@@ -10677,25 +10613,22 @@ module Google
10677
10613
  # @param [String] region
10678
10614
  # Name of the region scoping this request.
10679
10615
  # @param [String] filter
10680
- # Sets a filter `expression` for filtering listed resources. Your `expression`
10681
- # must be in the format: field_name comparison_string literal_string.
10682
- # The field_name is the name of the field you want to compare. Only atomic field
10683
- # types are supported (string, number, boolean). The comparison_string must be
10684
- # either eq (equals) or ne (not equals). The literal_string is the string value
10685
- # to filter to. The literal value must be valid for the type of field you are
10686
- # filtering by (string, number, boolean). For string fields, the literal value
10687
- # is interpreted as a regular expression using RE2 syntax. The literal value
10688
- # must match the entire field.
10689
- # For example, to filter for instances that do not have a name of example-
10690
- # instance, you would use name ne example-instance.
10691
- # You can filter on nested fields. For example, you could filter on instances
10692
- # that have set the scheduling.automaticRestart field to true. Use filtering on
10693
- # nested fields to take advantage of labels to organize and search for results
10694
- # based on label values.
10616
+ # A filter expression that filters resources listed in the response. The
10617
+ # expression must specify the field name, a comparison operator, and the value
10618
+ # that you want to use for filtering. The value must be a string, a number, or a
10619
+ # boolean. The comparison operator must be either =, !=, >, or <.
10620
+ # For example, if you are filtering Compute Engine instances, you can exclude
10621
+ # instances named example-instance by specifying name != example-instance.
10622
+ # You can also filter nested fields. For example, you could specify scheduling.
10623
+ # automaticRestart = false to include instances only if they are not scheduled
10624
+ # for automatic restarts. You can use filtering on nested fields to filter based
10625
+ # on resource labels.
10695
10626
  # To filter on multiple expressions, provide each separate expression within
10696
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
10697
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
10698
- # resources must match all expressions to pass the filters.
10627
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
10628
+ # Intel Skylake"). By default, each expression is an AND expression. However,
10629
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
10630
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
10631
+ # automaticRestart = true).
10699
10632
  # @param [Fixnum] max_results
10700
10633
  # The maximum number of results per page that should be returned. If the number
10701
10634
  # of available results is larger than maxResults, Compute Engine returns a
@@ -10873,25 +10806,22 @@ module Google
10873
10806
  # @param [String] project
10874
10807
  # Project ID for this request.
10875
10808
  # @param [String] filter
10876
- # Sets a filter `expression` for filtering listed resources. Your `expression`
10877
- # must be in the format: field_name comparison_string literal_string.
10878
- # The field_name is the name of the field you want to compare. Only atomic field
10879
- # types are supported (string, number, boolean). The comparison_string must be
10880
- # either eq (equals) or ne (not equals). The literal_string is the string value
10881
- # to filter to. The literal value must be valid for the type of field you are
10882
- # filtering by (string, number, boolean). For string fields, the literal value
10883
- # is interpreted as a regular expression using RE2 syntax. The literal value
10884
- # must match the entire field.
10885
- # For example, to filter for instances that do not have a name of example-
10886
- # instance, you would use name ne example-instance.
10887
- # You can filter on nested fields. For example, you could filter on instances
10888
- # that have set the scheduling.automaticRestart field to true. Use filtering on
10889
- # nested fields to take advantage of labels to organize and search for results
10890
- # based on label values.
10809
+ # A filter expression that filters resources listed in the response. The
10810
+ # expression must specify the field name, a comparison operator, and the value
10811
+ # that you want to use for filtering. The value must be a string, a number, or a
10812
+ # boolean. The comparison operator must be either =, !=, >, or <.
10813
+ # For example, if you are filtering Compute Engine instances, you can exclude
10814
+ # instances named example-instance by specifying name != example-instance.
10815
+ # You can also filter nested fields. For example, you could specify scheduling.
10816
+ # automaticRestart = false to include instances only if they are not scheduled
10817
+ # for automatic restarts. You can use filtering on nested fields to filter based
10818
+ # on resource labels.
10891
10819
  # To filter on multiple expressions, provide each separate expression within
10892
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
10893
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
10894
- # resources must match all expressions to pass the filters.
10820
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
10821
+ # Intel Skylake"). By default, each expression is an AND expression. However,
10822
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
10823
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
10824
+ # automaticRestart = true).
10895
10825
  # @param [Fixnum] max_results
10896
10826
  # The maximum number of results per page that should be returned. If the number
10897
10827
  # of available results is larger than maxResults, Compute Engine returns a
@@ -11047,25 +10977,22 @@ module Google
11047
10977
  # @param [String] region
11048
10978
  # Name of the region for this request.
11049
10979
  # @param [String] filter
11050
- # Sets a filter `expression` for filtering listed resources. Your `expression`
11051
- # must be in the format: field_name comparison_string literal_string.
11052
- # The field_name is the name of the field you want to compare. Only atomic field
11053
- # types are supported (string, number, boolean). The comparison_string must be
11054
- # either eq (equals) or ne (not equals). The literal_string is the string value
11055
- # to filter to. The literal value must be valid for the type of field you are
11056
- # filtering by (string, number, boolean). For string fields, the literal value
11057
- # is interpreted as a regular expression using RE2 syntax. The literal value
11058
- # must match the entire field.
11059
- # For example, to filter for instances that do not have a name of example-
11060
- # instance, you would use name ne example-instance.
11061
- # You can filter on nested fields. For example, you could filter on instances
11062
- # that have set the scheduling.automaticRestart field to true. Use filtering on
11063
- # nested fields to take advantage of labels to organize and search for results
11064
- # based on label values.
10980
+ # A filter expression that filters resources listed in the response. The
10981
+ # expression must specify the field name, a comparison operator, and the value
10982
+ # that you want to use for filtering. The value must be a string, a number, or a
10983
+ # boolean. The comparison operator must be either =, !=, >, or <.
10984
+ # For example, if you are filtering Compute Engine instances, you can exclude
10985
+ # instances named example-instance by specifying name != example-instance.
10986
+ # You can also filter nested fields. For example, you could specify scheduling.
10987
+ # automaticRestart = false to include instances only if they are not scheduled
10988
+ # for automatic restarts. You can use filtering on nested fields to filter based
10989
+ # on resource labels.
11065
10990
  # To filter on multiple expressions, provide each separate expression within
11066
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
11067
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
11068
- # resources must match all expressions to pass the filters.
10991
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
10992
+ # Intel Skylake"). By default, each expression is an AND expression. However,
10993
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
10994
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
10995
+ # automaticRestart = true).
11069
10996
  # @param [Fixnum] max_results
11070
10997
  # The maximum number of results per page that should be returned. If the number
11071
10998
  # of available results is larger than maxResults, Compute Engine returns a
@@ -11414,25 +11341,22 @@ module Google
11414
11341
  # @param [String] region
11415
11342
  # Name of the region scoping this request.
11416
11343
  # @param [String] filter
11417
- # Sets a filter `expression` for filtering listed resources. Your `expression`
11418
- # must be in the format: field_name comparison_string literal_string.
11419
- # The field_name is the name of the field you want to compare. Only atomic field
11420
- # types are supported (string, number, boolean). The comparison_string must be
11421
- # either eq (equals) or ne (not equals). The literal_string is the string value
11422
- # to filter to. The literal value must be valid for the type of field you are
11423
- # filtering by (string, number, boolean). For string fields, the literal value
11424
- # is interpreted as a regular expression using RE2 syntax. The literal value
11425
- # must match the entire field.
11426
- # For example, to filter for instances that do not have a name of example-
11427
- # instance, you would use name ne example-instance.
11428
- # You can filter on nested fields. For example, you could filter on instances
11429
- # that have set the scheduling.automaticRestart field to true. Use filtering on
11430
- # nested fields to take advantage of labels to organize and search for results
11431
- # based on label values.
11344
+ # A filter expression that filters resources listed in the response. The
11345
+ # expression must specify the field name, a comparison operator, and the value
11346
+ # that you want to use for filtering. The value must be a string, a number, or a
11347
+ # boolean. The comparison operator must be either =, !=, >, or <.
11348
+ # For example, if you are filtering Compute Engine instances, you can exclude
11349
+ # instances named example-instance by specifying name != example-instance.
11350
+ # You can also filter nested fields. For example, you could specify scheduling.
11351
+ # automaticRestart = false to include instances only if they are not scheduled
11352
+ # for automatic restarts. You can use filtering on nested fields to filter based
11353
+ # on resource labels.
11432
11354
  # To filter on multiple expressions, provide each separate expression within
11433
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
11434
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
11435
- # resources must match all expressions to pass the filters.
11355
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
11356
+ # Intel Skylake"). By default, each expression is an AND expression. However,
11357
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
11358
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
11359
+ # automaticRestart = true).
11436
11360
  # @param [Fixnum] max_results
11437
11361
  # The maximum number of results per page that should be returned. If the number
11438
11362
  # of available results is larger than maxResults, Compute Engine returns a
@@ -11830,25 +11754,22 @@ module Google
11830
11754
  # @param [String] region
11831
11755
  # Name of the region scoping this request.
11832
11756
  # @param [String] filter
11833
- # Sets a filter `expression` for filtering listed resources. Your `expression`
11834
- # must be in the format: field_name comparison_string literal_string.
11835
- # The field_name is the name of the field you want to compare. Only atomic field
11836
- # types are supported (string, number, boolean). The comparison_string must be
11837
- # either eq (equals) or ne (not equals). The literal_string is the string value
11838
- # to filter to. The literal value must be valid for the type of field you are
11839
- # filtering by (string, number, boolean). For string fields, the literal value
11840
- # is interpreted as a regular expression using RE2 syntax. The literal value
11841
- # must match the entire field.
11842
- # For example, to filter for instances that do not have a name of example-
11843
- # instance, you would use name ne example-instance.
11844
- # You can filter on nested fields. For example, you could filter on instances
11845
- # that have set the scheduling.automaticRestart field to true. Use filtering on
11846
- # nested fields to take advantage of labels to organize and search for results
11847
- # based on label values.
11757
+ # A filter expression that filters resources listed in the response. The
11758
+ # expression must specify the field name, a comparison operator, and the value
11759
+ # that you want to use for filtering. The value must be a string, a number, or a
11760
+ # boolean. The comparison operator must be either =, !=, >, or <.
11761
+ # For example, if you are filtering Compute Engine instances, you can exclude
11762
+ # instances named example-instance by specifying name != example-instance.
11763
+ # You can also filter nested fields. For example, you could specify scheduling.
11764
+ # automaticRestart = false to include instances only if they are not scheduled
11765
+ # for automatic restarts. You can use filtering on nested fields to filter based
11766
+ # on resource labels.
11848
11767
  # To filter on multiple expressions, provide each separate expression within
11849
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
11850
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
11851
- # resources must match all expressions to pass the filters.
11768
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
11769
+ # Intel Skylake"). By default, each expression is an AND expression. However,
11770
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
11771
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
11772
+ # automaticRestart = true).
11852
11773
  # @param [Fixnum] max_results
11853
11774
  # The maximum number of results per page that should be returned. If the number
11854
11775
  # of available results is larger than maxResults, Compute Engine returns a
@@ -11914,25 +11835,22 @@ module Google
11914
11835
  # Name of the regional instance group for which we want to list the instances.
11915
11836
  # @param [Google::Apis::ComputeV1::RegionInstanceGroupsListInstancesRequest] region_instance_groups_list_instances_request_object
11916
11837
  # @param [String] filter
11917
- # Sets a filter `expression` for filtering listed resources. Your `expression`
11918
- # must be in the format: field_name comparison_string literal_string.
11919
- # The field_name is the name of the field you want to compare. Only atomic field
11920
- # types are supported (string, number, boolean). The comparison_string must be
11921
- # either eq (equals) or ne (not equals). The literal_string is the string value
11922
- # to filter to. The literal value must be valid for the type of field you are
11923
- # filtering by (string, number, boolean). For string fields, the literal value
11924
- # is interpreted as a regular expression using RE2 syntax. The literal value
11925
- # must match the entire field.
11926
- # For example, to filter for instances that do not have a name of example-
11927
- # instance, you would use name ne example-instance.
11928
- # You can filter on nested fields. For example, you could filter on instances
11929
- # that have set the scheduling.automaticRestart field to true. Use filtering on
11930
- # nested fields to take advantage of labels to organize and search for results
11931
- # based on label values.
11838
+ # A filter expression that filters resources listed in the response. The
11839
+ # expression must specify the field name, a comparison operator, and the value
11840
+ # that you want to use for filtering. The value must be a string, a number, or a
11841
+ # boolean. The comparison operator must be either =, !=, >, or <.
11842
+ # For example, if you are filtering Compute Engine instances, you can exclude
11843
+ # instances named example-instance by specifying name != example-instance.
11844
+ # You can also filter nested fields. For example, you could specify scheduling.
11845
+ # automaticRestart = false to include instances only if they are not scheduled
11846
+ # for automatic restarts. You can use filtering on nested fields to filter based
11847
+ # on resource labels.
11932
11848
  # To filter on multiple expressions, provide each separate expression within
11933
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
11934
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
11935
- # resources must match all expressions to pass the filters.
11849
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
11850
+ # Intel Skylake"). By default, each expression is an AND expression. However,
11851
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
11852
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
11853
+ # automaticRestart = true).
11936
11854
  # @param [Fixnum] max_results
11937
11855
  # The maximum number of results per page that should be returned. If the number
11938
11856
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12132,25 +12050,22 @@ module Google
12132
12050
  # @param [String] region
12133
12051
  # Name of the region for this request.
12134
12052
  # @param [String] filter
12135
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12136
- # must be in the format: field_name comparison_string literal_string.
12137
- # The field_name is the name of the field you want to compare. Only atomic field
12138
- # types are supported (string, number, boolean). The comparison_string must be
12139
- # either eq (equals) or ne (not equals). The literal_string is the string value
12140
- # to filter to. The literal value must be valid for the type of field you are
12141
- # filtering by (string, number, boolean). For string fields, the literal value
12142
- # is interpreted as a regular expression using RE2 syntax. The literal value
12143
- # must match the entire field.
12144
- # For example, to filter for instances that do not have a name of example-
12145
- # instance, you would use name ne example-instance.
12146
- # You can filter on nested fields. For example, you could filter on instances
12147
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12148
- # nested fields to take advantage of labels to organize and search for results
12149
- # based on label values.
12053
+ # A filter expression that filters resources listed in the response. The
12054
+ # expression must specify the field name, a comparison operator, and the value
12055
+ # that you want to use for filtering. The value must be a string, a number, or a
12056
+ # boolean. The comparison operator must be either =, !=, >, or <.
12057
+ # For example, if you are filtering Compute Engine instances, you can exclude
12058
+ # instances named example-instance by specifying name != example-instance.
12059
+ # You can also filter nested fields. For example, you could specify scheduling.
12060
+ # automaticRestart = false to include instances only if they are not scheduled
12061
+ # for automatic restarts. You can use filtering on nested fields to filter based
12062
+ # on resource labels.
12150
12063
  # To filter on multiple expressions, provide each separate expression within
12151
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12152
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12153
- # resources must match all expressions to pass the filters.
12064
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12065
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12066
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12067
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12068
+ # automaticRestart = true).
12154
12069
  # @param [Fixnum] max_results
12155
12070
  # The maximum number of results per page that should be returned. If the number
12156
12071
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12248,25 +12163,22 @@ module Google
12248
12163
  # @param [String] project
12249
12164
  # Project ID for this request.
12250
12165
  # @param [String] filter
12251
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12252
- # must be in the format: field_name comparison_string literal_string.
12253
- # The field_name is the name of the field you want to compare. Only atomic field
12254
- # types are supported (string, number, boolean). The comparison_string must be
12255
- # either eq (equals) or ne (not equals). The literal_string is the string value
12256
- # to filter to. The literal value must be valid for the type of field you are
12257
- # filtering by (string, number, boolean). For string fields, the literal value
12258
- # is interpreted as a regular expression using RE2 syntax. The literal value
12259
- # must match the entire field.
12260
- # For example, to filter for instances that do not have a name of example-
12261
- # instance, you would use name ne example-instance.
12262
- # You can filter on nested fields. For example, you could filter on instances
12263
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12264
- # nested fields to take advantage of labels to organize and search for results
12265
- # based on label values.
12166
+ # A filter expression that filters resources listed in the response. The
12167
+ # expression must specify the field name, a comparison operator, and the value
12168
+ # that you want to use for filtering. The value must be a string, a number, or a
12169
+ # boolean. The comparison operator must be either =, !=, >, or <.
12170
+ # For example, if you are filtering Compute Engine instances, you can exclude
12171
+ # instances named example-instance by specifying name != example-instance.
12172
+ # You can also filter nested fields. For example, you could specify scheduling.
12173
+ # automaticRestart = false to include instances only if they are not scheduled
12174
+ # for automatic restarts. You can use filtering on nested fields to filter based
12175
+ # on resource labels.
12266
12176
  # To filter on multiple expressions, provide each separate expression within
12267
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12268
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12269
- # resources must match all expressions to pass the filters.
12177
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12178
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12179
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12180
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12181
+ # automaticRestart = true).
12270
12182
  # @param [Fixnum] max_results
12271
12183
  # The maximum number of results per page that should be returned. If the number
12272
12184
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12324,25 +12236,22 @@ module Google
12324
12236
  # @param [String] project
12325
12237
  # Project ID for this request.
12326
12238
  # @param [String] filter
12327
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12328
- # must be in the format: field_name comparison_string literal_string.
12329
- # The field_name is the name of the field you want to compare. Only atomic field
12330
- # types are supported (string, number, boolean). The comparison_string must be
12331
- # either eq (equals) or ne (not equals). The literal_string is the string value
12332
- # to filter to. The literal value must be valid for the type of field you are
12333
- # filtering by (string, number, boolean). For string fields, the literal value
12334
- # is interpreted as a regular expression using RE2 syntax. The literal value
12335
- # must match the entire field.
12336
- # For example, to filter for instances that do not have a name of example-
12337
- # instance, you would use name ne example-instance.
12338
- # You can filter on nested fields. For example, you could filter on instances
12339
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12340
- # nested fields to take advantage of labels to organize and search for results
12341
- # based on label values.
12239
+ # A filter expression that filters resources listed in the response. The
12240
+ # expression must specify the field name, a comparison operator, and the value
12241
+ # that you want to use for filtering. The value must be a string, a number, or a
12242
+ # boolean. The comparison operator must be either =, !=, >, or <.
12243
+ # For example, if you are filtering Compute Engine instances, you can exclude
12244
+ # instances named example-instance by specifying name != example-instance.
12245
+ # You can also filter nested fields. For example, you could specify scheduling.
12246
+ # automaticRestart = false to include instances only if they are not scheduled
12247
+ # for automatic restarts. You can use filtering on nested fields to filter based
12248
+ # on resource labels.
12342
12249
  # To filter on multiple expressions, provide each separate expression within
12343
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12344
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12345
- # resources must match all expressions to pass the filters.
12250
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12251
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12252
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12253
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12254
+ # automaticRestart = true).
12346
12255
  # @param [Fixnum] max_results
12347
12256
  # The maximum number of results per page that should be returned. If the number
12348
12257
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12592,25 +12501,22 @@ module Google
12592
12501
  # @param [String] region
12593
12502
  # Name of the region for this request.
12594
12503
  # @param [String] filter
12595
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12596
- # must be in the format: field_name comparison_string literal_string.
12597
- # The field_name is the name of the field you want to compare. Only atomic field
12598
- # types are supported (string, number, boolean). The comparison_string must be
12599
- # either eq (equals) or ne (not equals). The literal_string is the string value
12600
- # to filter to. The literal value must be valid for the type of field you are
12601
- # filtering by (string, number, boolean). For string fields, the literal value
12602
- # is interpreted as a regular expression using RE2 syntax. The literal value
12603
- # must match the entire field.
12604
- # For example, to filter for instances that do not have a name of example-
12605
- # instance, you would use name ne example-instance.
12606
- # You can filter on nested fields. For example, you could filter on instances
12607
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12608
- # nested fields to take advantage of labels to organize and search for results
12609
- # based on label values.
12504
+ # A filter expression that filters resources listed in the response. The
12505
+ # expression must specify the field name, a comparison operator, and the value
12506
+ # that you want to use for filtering. The value must be a string, a number, or a
12507
+ # boolean. The comparison operator must be either =, !=, >, or <.
12508
+ # For example, if you are filtering Compute Engine instances, you can exclude
12509
+ # instances named example-instance by specifying name != example-instance.
12510
+ # You can also filter nested fields. For example, you could specify scheduling.
12511
+ # automaticRestart = false to include instances only if they are not scheduled
12512
+ # for automatic restarts. You can use filtering on nested fields to filter based
12513
+ # on resource labels.
12610
12514
  # To filter on multiple expressions, provide each separate expression within
12611
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12612
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12613
- # resources must match all expressions to pass the filters.
12515
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12516
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12517
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12518
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12519
+ # automaticRestart = true).
12614
12520
  # @param [Fixnum] max_results
12615
12521
  # The maximum number of results per page that should be returned. If the number
12616
12522
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12968,25 +12874,22 @@ module Google
12968
12874
  # @param [String] project
12969
12875
  # Project ID for this request.
12970
12876
  # @param [String] filter
12971
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12972
- # must be in the format: field_name comparison_string literal_string.
12973
- # The field_name is the name of the field you want to compare. Only atomic field
12974
- # types are supported (string, number, boolean). The comparison_string must be
12975
- # either eq (equals) or ne (not equals). The literal_string is the string value
12976
- # to filter to. The literal value must be valid for the type of field you are
12977
- # filtering by (string, number, boolean). For string fields, the literal value
12978
- # is interpreted as a regular expression using RE2 syntax. The literal value
12979
- # must match the entire field.
12980
- # For example, to filter for instances that do not have a name of example-
12981
- # instance, you would use name ne example-instance.
12982
- # You can filter on nested fields. For example, you could filter on instances
12983
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12984
- # nested fields to take advantage of labels to organize and search for results
12985
- # based on label values.
12877
+ # A filter expression that filters resources listed in the response. The
12878
+ # expression must specify the field name, a comparison operator, and the value
12879
+ # that you want to use for filtering. The value must be a string, a number, or a
12880
+ # boolean. The comparison operator must be either =, !=, >, or <.
12881
+ # For example, if you are filtering Compute Engine instances, you can exclude
12882
+ # instances named example-instance by specifying name != example-instance.
12883
+ # You can also filter nested fields. For example, you could specify scheduling.
12884
+ # automaticRestart = false to include instances only if they are not scheduled
12885
+ # for automatic restarts. You can use filtering on nested fields to filter based
12886
+ # on resource labels.
12986
12887
  # To filter on multiple expressions, provide each separate expression within
12987
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12988
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12989
- # resources must match all expressions to pass the filters.
12888
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12889
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12890
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12891
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12892
+ # automaticRestart = true).
12990
12893
  # @param [Fixnum] max_results
12991
12894
  # The maximum number of results per page that should be returned. If the number
12992
12895
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13138,25 +13041,22 @@ module Google
13138
13041
  # @param [String] project
13139
13042
  # Project ID for this request.
13140
13043
  # @param [String] filter
13141
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13142
- # must be in the format: field_name comparison_string literal_string.
13143
- # The field_name is the name of the field you want to compare. Only atomic field
13144
- # types are supported (string, number, boolean). The comparison_string must be
13145
- # either eq (equals) or ne (not equals). The literal_string is the string value
13146
- # to filter to. The literal value must be valid for the type of field you are
13147
- # filtering by (string, number, boolean). For string fields, the literal value
13148
- # is interpreted as a regular expression using RE2 syntax. The literal value
13149
- # must match the entire field.
13150
- # For example, to filter for instances that do not have a name of example-
13151
- # instance, you would use name ne example-instance.
13152
- # You can filter on nested fields. For example, you could filter on instances
13153
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13154
- # nested fields to take advantage of labels to organize and search for results
13155
- # based on label values.
13044
+ # A filter expression that filters resources listed in the response. The
13045
+ # expression must specify the field name, a comparison operator, and the value
13046
+ # that you want to use for filtering. The value must be a string, a number, or a
13047
+ # boolean. The comparison operator must be either =, !=, >, or <.
13048
+ # For example, if you are filtering Compute Engine instances, you can exclude
13049
+ # instances named example-instance by specifying name != example-instance.
13050
+ # You can also filter nested fields. For example, you could specify scheduling.
13051
+ # automaticRestart = false to include instances only if they are not scheduled
13052
+ # for automatic restarts. You can use filtering on nested fields to filter based
13053
+ # on resource labels.
13156
13054
  # To filter on multiple expressions, provide each separate expression within
13157
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13158
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13159
- # resources must match all expressions to pass the filters.
13055
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13056
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13057
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13058
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13059
+ # automaticRestart = true).
13160
13060
  # @param [Fixnum] max_results
13161
13061
  # The maximum number of results per page that should be returned. If the number
13162
13062
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13397,25 +13297,22 @@ module Google
13397
13297
  # @param [String] project
13398
13298
  # Project ID for this request.
13399
13299
  # @param [String] filter
13400
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13401
- # must be in the format: field_name comparison_string literal_string.
13402
- # The field_name is the name of the field you want to compare. Only atomic field
13403
- # types are supported (string, number, boolean). The comparison_string must be
13404
- # either eq (equals) or ne (not equals). The literal_string is the string value
13405
- # to filter to. The literal value must be valid for the type of field you are
13406
- # filtering by (string, number, boolean). For string fields, the literal value
13407
- # is interpreted as a regular expression using RE2 syntax. The literal value
13408
- # must match the entire field.
13409
- # For example, to filter for instances that do not have a name of example-
13410
- # instance, you would use name ne example-instance.
13411
- # You can filter on nested fields. For example, you could filter on instances
13412
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13413
- # nested fields to take advantage of labels to organize and search for results
13414
- # based on label values.
13300
+ # A filter expression that filters resources listed in the response. The
13301
+ # expression must specify the field name, a comparison operator, and the value
13302
+ # that you want to use for filtering. The value must be a string, a number, or a
13303
+ # boolean. The comparison operator must be either =, !=, >, or <.
13304
+ # For example, if you are filtering Compute Engine instances, you can exclude
13305
+ # instances named example-instance by specifying name != example-instance.
13306
+ # You can also filter nested fields. For example, you could specify scheduling.
13307
+ # automaticRestart = false to include instances only if they are not scheduled
13308
+ # for automatic restarts. You can use filtering on nested fields to filter based
13309
+ # on resource labels.
13415
13310
  # To filter on multiple expressions, provide each separate expression within
13416
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13417
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13418
- # resources must match all expressions to pass the filters.
13311
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13312
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13313
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13314
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13315
+ # automaticRestart = true).
13419
13316
  # @param [Fixnum] max_results
13420
13317
  # The maximum number of results per page that should be returned. If the number
13421
13318
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13473,25 +13370,22 @@ module Google
13473
13370
  # @param [String] project
13474
13371
  # Project ID for this request.
13475
13372
  # @param [String] filter
13476
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13477
- # must be in the format: field_name comparison_string literal_string.
13478
- # The field_name is the name of the field you want to compare. Only atomic field
13479
- # types are supported (string, number, boolean). The comparison_string must be
13480
- # either eq (equals) or ne (not equals). The literal_string is the string value
13481
- # to filter to. The literal value must be valid for the type of field you are
13482
- # filtering by (string, number, boolean). For string fields, the literal value
13483
- # is interpreted as a regular expression using RE2 syntax. The literal value
13484
- # must match the entire field.
13485
- # For example, to filter for instances that do not have a name of example-
13486
- # instance, you would use name ne example-instance.
13487
- # You can filter on nested fields. For example, you could filter on instances
13488
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13489
- # nested fields to take advantage of labels to organize and search for results
13490
- # based on label values.
13373
+ # A filter expression that filters resources listed in the response. The
13374
+ # expression must specify the field name, a comparison operator, and the value
13375
+ # that you want to use for filtering. The value must be a string, a number, or a
13376
+ # boolean. The comparison operator must be either =, !=, >, or <.
13377
+ # For example, if you are filtering Compute Engine instances, you can exclude
13378
+ # instances named example-instance by specifying name != example-instance.
13379
+ # You can also filter nested fields. For example, you could specify scheduling.
13380
+ # automaticRestart = false to include instances only if they are not scheduled
13381
+ # for automatic restarts. You can use filtering on nested fields to filter based
13382
+ # on resource labels.
13491
13383
  # To filter on multiple expressions, provide each separate expression within
13492
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13493
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13494
- # resources must match all expressions to pass the filters.
13384
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13385
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13386
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13387
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13388
+ # automaticRestart = true).
13495
13389
  # @param [Fixnum] max_results
13496
13390
  # The maximum number of results per page that should be returned. If the number
13497
13391
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13756,25 +13650,22 @@ module Google
13756
13650
  # @param [String] region
13757
13651
  # Name of the region scoping this request.
13758
13652
  # @param [String] filter
13759
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13760
- # must be in the format: field_name comparison_string literal_string.
13761
- # The field_name is the name of the field you want to compare. Only atomic field
13762
- # types are supported (string, number, boolean). The comparison_string must be
13763
- # either eq (equals) or ne (not equals). The literal_string is the string value
13764
- # to filter to. The literal value must be valid for the type of field you are
13765
- # filtering by (string, number, boolean). For string fields, the literal value
13766
- # is interpreted as a regular expression using RE2 syntax. The literal value
13767
- # must match the entire field.
13768
- # For example, to filter for instances that do not have a name of example-
13769
- # instance, you would use name ne example-instance.
13770
- # You can filter on nested fields. For example, you could filter on instances
13771
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13772
- # nested fields to take advantage of labels to organize and search for results
13773
- # based on label values.
13653
+ # A filter expression that filters resources listed in the response. The
13654
+ # expression must specify the field name, a comparison operator, and the value
13655
+ # that you want to use for filtering. The value must be a string, a number, or a
13656
+ # boolean. The comparison operator must be either =, !=, >, or <.
13657
+ # For example, if you are filtering Compute Engine instances, you can exclude
13658
+ # instances named example-instance by specifying name != example-instance.
13659
+ # You can also filter nested fields. For example, you could specify scheduling.
13660
+ # automaticRestart = false to include instances only if they are not scheduled
13661
+ # for automatic restarts. You can use filtering on nested fields to filter based
13662
+ # on resource labels.
13774
13663
  # To filter on multiple expressions, provide each separate expression within
13775
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13776
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13777
- # resources must match all expressions to pass the filters.
13664
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13665
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13666
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13667
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13668
+ # automaticRestart = true).
13778
13669
  # @param [Fixnum] max_results
13779
13670
  # The maximum number of results per page that should be returned. If the number
13780
13671
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13829,6 +13720,66 @@ module Google
13829
13720
  execute_or_queue_command(command, &block)
13830
13721
  end
13831
13722
 
13723
+ # Patches the specified subnetwork with the data included in the request. Only
13724
+ # the following fields within the subnetwork resource can be specified in the
13725
+ # request: secondary_ip_range and allow_subnet_cidr_routes_overlap. It is also
13726
+ # mandatory to specify the current fingeprint of the subnetwork resource being
13727
+ # patched.
13728
+ # @param [String] project
13729
+ # Project ID for this request.
13730
+ # @param [String] region
13731
+ # Name of the region scoping this request.
13732
+ # @param [String] subnetwork
13733
+ # Name of the Subnetwork resource to patch.
13734
+ # @param [Google::Apis::ComputeV1::Subnetwork] subnetwork_object
13735
+ # @param [String] request_id
13736
+ # An optional request ID to identify requests. Specify a unique request ID so
13737
+ # that if you must retry your request, the server will know to ignore the
13738
+ # request if it has already been completed.
13739
+ # For example, consider a situation where you make an initial request and the
13740
+ # request times out. If you make the request again with the same request ID, the
13741
+ # server can check if original operation with the same request ID was received,
13742
+ # and if so, will ignore the second request. This prevents clients from
13743
+ # accidentally creating duplicate commitments.
13744
+ # The request ID must be a valid UUID with the exception that zero UUID is not
13745
+ # supported (00000000-0000-0000-0000-000000000000).
13746
+ # @param [String] fields
13747
+ # Selector specifying which fields to include in a partial response.
13748
+ # @param [String] quota_user
13749
+ # Available to use for quota purposes for server-side applications. Can be any
13750
+ # arbitrary string assigned to a user, but should not exceed 40 characters.
13751
+ # Overrides userIp if both are provided.
13752
+ # @param [String] user_ip
13753
+ # IP address of the site where the request originates. Use this if you want to
13754
+ # enforce per-user limits.
13755
+ # @param [Google::Apis::RequestOptions] options
13756
+ # Request-specific options
13757
+ #
13758
+ # @yield [result, err] Result & error if block supplied
13759
+ # @yieldparam result [Google::Apis::ComputeV1::Operation] parsed result object
13760
+ # @yieldparam err [StandardError] error object if request failed
13761
+ #
13762
+ # @return [Google::Apis::ComputeV1::Operation]
13763
+ #
13764
+ # @raise [Google::Apis::ServerError] An error occurred on the server and the request can be retried
13765
+ # @raise [Google::Apis::ClientError] The request is invalid and should not be retried without modification
13766
+ # @raise [Google::Apis::AuthorizationError] Authorization is required
13767
+ def patch_subnetwork(project, region, subnetwork, subnetwork_object = nil, request_id: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block)
13768
+ command = make_simple_command(:patch, '{project}/regions/{region}/subnetworks/{subnetwork}', options)
13769
+ command.request_representation = Google::Apis::ComputeV1::Subnetwork::Representation
13770
+ command.request_object = subnetwork_object
13771
+ command.response_representation = Google::Apis::ComputeV1::Operation::Representation
13772
+ command.response_class = Google::Apis::ComputeV1::Operation
13773
+ command.params['project'] = project unless project.nil?
13774
+ command.params['region'] = region unless region.nil?
13775
+ command.params['subnetwork'] = subnetwork unless subnetwork.nil?
13776
+ command.query['requestId'] = request_id unless request_id.nil?
13777
+ command.query['fields'] = fields unless fields.nil?
13778
+ command.query['quotaUser'] = quota_user unless quota_user.nil?
13779
+ command.query['userIp'] = user_ip unless user_ip.nil?
13780
+ execute_or_queue_command(command, &block)
13781
+ end
13782
+
13832
13783
  # Set whether VMs in this subnet can access Google services without assigning
13833
13784
  # external IP addresses through Private Google Access.
13834
13785
  # @param [String] project
@@ -14031,25 +13982,22 @@ module Google
14031
13982
  # @param [String] project
14032
13983
  # Project ID for this request.
14033
13984
  # @param [String] filter
14034
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14035
- # must be in the format: field_name comparison_string literal_string.
14036
- # The field_name is the name of the field you want to compare. Only atomic field
14037
- # types are supported (string, number, boolean). The comparison_string must be
14038
- # either eq (equals) or ne (not equals). The literal_string is the string value
14039
- # to filter to. The literal value must be valid for the type of field you are
14040
- # filtering by (string, number, boolean). For string fields, the literal value
14041
- # is interpreted as a regular expression using RE2 syntax. The literal value
14042
- # must match the entire field.
14043
- # For example, to filter for instances that do not have a name of example-
14044
- # instance, you would use name ne example-instance.
14045
- # You can filter on nested fields. For example, you could filter on instances
14046
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14047
- # nested fields to take advantage of labels to organize and search for results
14048
- # based on label values.
13985
+ # A filter expression that filters resources listed in the response. The
13986
+ # expression must specify the field name, a comparison operator, and the value
13987
+ # that you want to use for filtering. The value must be a string, a number, or a
13988
+ # boolean. The comparison operator must be either =, !=, >, or <.
13989
+ # For example, if you are filtering Compute Engine instances, you can exclude
13990
+ # instances named example-instance by specifying name != example-instance.
13991
+ # You can also filter nested fields. For example, you could specify scheduling.
13992
+ # automaticRestart = false to include instances only if they are not scheduled
13993
+ # for automatic restarts. You can use filtering on nested fields to filter based
13994
+ # on resource labels.
14049
13995
  # To filter on multiple expressions, provide each separate expression within
14050
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14051
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14052
- # resources must match all expressions to pass the filters.
13996
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13997
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13998
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13999
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14000
+ # automaticRestart = true).
14053
14001
  # @param [Fixnum] max_results
14054
14002
  # The maximum number of results per page that should be returned. If the number
14055
14003
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14301,25 +14249,22 @@ module Google
14301
14249
  # @param [String] project
14302
14250
  # Project ID for this request.
14303
14251
  # @param [String] filter
14304
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14305
- # must be in the format: field_name comparison_string literal_string.
14306
- # The field_name is the name of the field you want to compare. Only atomic field
14307
- # types are supported (string, number, boolean). The comparison_string must be
14308
- # either eq (equals) or ne (not equals). The literal_string is the string value
14309
- # to filter to. The literal value must be valid for the type of field you are
14310
- # filtering by (string, number, boolean). For string fields, the literal value
14311
- # is interpreted as a regular expression using RE2 syntax. The literal value
14312
- # must match the entire field.
14313
- # For example, to filter for instances that do not have a name of example-
14314
- # instance, you would use name ne example-instance.
14315
- # You can filter on nested fields. For example, you could filter on instances
14316
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14317
- # nested fields to take advantage of labels to organize and search for results
14318
- # based on label values.
14252
+ # A filter expression that filters resources listed in the response. The
14253
+ # expression must specify the field name, a comparison operator, and the value
14254
+ # that you want to use for filtering. The value must be a string, a number, or a
14255
+ # boolean. The comparison operator must be either =, !=, >, or <.
14256
+ # For example, if you are filtering Compute Engine instances, you can exclude
14257
+ # instances named example-instance by specifying name != example-instance.
14258
+ # You can also filter nested fields. For example, you could specify scheduling.
14259
+ # automaticRestart = false to include instances only if they are not scheduled
14260
+ # for automatic restarts. You can use filtering on nested fields to filter based
14261
+ # on resource labels.
14319
14262
  # To filter on multiple expressions, provide each separate expression within
14320
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14321
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14322
- # resources must match all expressions to pass the filters.
14263
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
14264
+ # Intel Skylake"). By default, each expression is an AND expression. However,
14265
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
14266
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14267
+ # automaticRestart = true).
14323
14268
  # @param [Fixnum] max_results
14324
14269
  # The maximum number of results per page that should be returned. If the number
14325
14270
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14483,25 +14428,22 @@ module Google
14483
14428
  # @param [String] project
14484
14429
  # Project ID for this request.
14485
14430
  # @param [String] filter
14486
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14487
- # must be in the format: field_name comparison_string literal_string.
14488
- # The field_name is the name of the field you want to compare. Only atomic field
14489
- # types are supported (string, number, boolean). The comparison_string must be
14490
- # either eq (equals) or ne (not equals). The literal_string is the string value
14491
- # to filter to. The literal value must be valid for the type of field you are
14492
- # filtering by (string, number, boolean). For string fields, the literal value
14493
- # is interpreted as a regular expression using RE2 syntax. The literal value
14494
- # must match the entire field.
14495
- # For example, to filter for instances that do not have a name of example-
14496
- # instance, you would use name ne example-instance.
14497
- # You can filter on nested fields. For example, you could filter on instances
14498
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14499
- # nested fields to take advantage of labels to organize and search for results
14500
- # based on label values.
14431
+ # A filter expression that filters resources listed in the response. The
14432
+ # expression must specify the field name, a comparison operator, and the value
14433
+ # that you want to use for filtering. The value must be a string, a number, or a
14434
+ # boolean. The comparison operator must be either =, !=, >, or <.
14435
+ # For example, if you are filtering Compute Engine instances, you can exclude
14436
+ # instances named example-instance by specifying name != example-instance.
14437
+ # You can also filter nested fields. For example, you could specify scheduling.
14438
+ # automaticRestart = false to include instances only if they are not scheduled
14439
+ # for automatic restarts. You can use filtering on nested fields to filter based
14440
+ # on resource labels.
14501
14441
  # To filter on multiple expressions, provide each separate expression within
14502
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14503
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14504
- # resources must match all expressions to pass the filters.
14442
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
14443
+ # Intel Skylake"). By default, each expression is an AND expression. However,
14444
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
14445
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14446
+ # automaticRestart = true).
14505
14447
  # @param [Fixnum] max_results
14506
14448
  # The maximum number of results per page that should be returned. If the number
14507
14449
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14711,25 +14653,22 @@ module Google
14711
14653
  # @param [String] zone
14712
14654
  # Name of the zone scoping this request.
14713
14655
  # @param [String] filter
14714
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14715
- # must be in the format: field_name comparison_string literal_string.
14716
- # The field_name is the name of the field you want to compare. Only atomic field
14717
- # types are supported (string, number, boolean). The comparison_string must be
14718
- # either eq (equals) or ne (not equals). The literal_string is the string value
14719
- # to filter to. The literal value must be valid for the type of field you are
14720
- # filtering by (string, number, boolean). For string fields, the literal value
14721
- # is interpreted as a regular expression using RE2 syntax. The literal value
14722
- # must match the entire field.
14723
- # For example, to filter for instances that do not have a name of example-
14724
- # instance, you would use name ne example-instance.
14725
- # You can filter on nested fields. For example, you could filter on instances
14726
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14727
- # nested fields to take advantage of labels to organize and search for results
14728
- # based on label values.
14656
+ # A filter expression that filters resources listed in the response. The
14657
+ # expression must specify the field name, a comparison operator, and the value
14658
+ # that you want to use for filtering. The value must be a string, a number, or a
14659
+ # boolean. The comparison operator must be either =, !=, >, or <.
14660
+ # For example, if you are filtering Compute Engine instances, you can exclude
14661
+ # instances named example-instance by specifying name != example-instance.
14662
+ # You can also filter nested fields. For example, you could specify scheduling.
14663
+ # automaticRestart = false to include instances only if they are not scheduled
14664
+ # for automatic restarts. You can use filtering on nested fields to filter based
14665
+ # on resource labels.
14729
14666
  # To filter on multiple expressions, provide each separate expression within
14730
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14731
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14732
- # resources must match all expressions to pass the filters.
14667
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
14668
+ # Intel Skylake"). By default, each expression is an AND expression. However,
14669
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
14670
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14671
+ # automaticRestart = true).
14733
14672
  # @param [Fixnum] max_results
14734
14673
  # The maximum number of results per page that should be returned. If the number
14735
14674
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14900,25 +14839,22 @@ module Google
14900
14839
  # @param [String] project
14901
14840
  # Project ID for this request.
14902
14841
  # @param [String] filter
14903
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14904
- # must be in the format: field_name comparison_string literal_string.
14905
- # The field_name is the name of the field you want to compare. Only atomic field
14906
- # types are supported (string, number, boolean). The comparison_string must be
14907
- # either eq (equals) or ne (not equals). The literal_string is the string value
14908
- # to filter to. The literal value must be valid for the type of field you are
14909
- # filtering by (string, number, boolean). For string fields, the literal value
14910
- # is interpreted as a regular expression using RE2 syntax. The literal value
14911
- # must match the entire field.
14912
- # For example, to filter for instances that do not have a name of example-
14913
- # instance, you would use name ne example-instance.
14914
- # You can filter on nested fields. For example, you could filter on instances
14915
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14916
- # nested fields to take advantage of labels to organize and search for results
14917
- # based on label values.
14842
+ # A filter expression that filters resources listed in the response. The
14843
+ # expression must specify the field name, a comparison operator, and the value
14844
+ # that you want to use for filtering. The value must be a string, a number, or a
14845
+ # boolean. The comparison operator must be either =, !=, >, or <.
14846
+ # For example, if you are filtering Compute Engine instances, you can exclude
14847
+ # instances named example-instance by specifying name != example-instance.
14848
+ # You can also filter nested fields. For example, you could specify scheduling.
14849
+ # automaticRestart = false to include instances only if they are not scheduled
14850
+ # for automatic restarts. You can use filtering on nested fields to filter based
14851
+ # on resource labels.
14918
14852
  # To filter on multiple expressions, provide each separate expression within
14919
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14920
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14921
- # resources must match all expressions to pass the filters.
14853
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
14854
+ # Intel Skylake"). By default, each expression is an AND expression. However,
14855
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
14856
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14857
+ # automaticRestart = true).
14922
14858
  # @param [Fixnum] max_results
14923
14859
  # The maximum number of results per page that should be returned. If the number
14924
14860
  # of available results is larger than maxResults, Compute Engine returns a
@@ -15172,25 +15108,22 @@ module Google
15172
15108
  # @param [String] region
15173
15109
  # Name of the region scoping this request.
15174
15110
  # @param [String] filter
15175
- # Sets a filter `expression` for filtering listed resources. Your `expression`
15176
- # must be in the format: field_name comparison_string literal_string.
15177
- # The field_name is the name of the field you want to compare. Only atomic field
15178
- # types are supported (string, number, boolean). The comparison_string must be
15179
- # either eq (equals) or ne (not equals). The literal_string is the string value
15180
- # to filter to. The literal value must be valid for the type of field you are
15181
- # filtering by (string, number, boolean). For string fields, the literal value
15182
- # is interpreted as a regular expression using RE2 syntax. The literal value
15183
- # must match the entire field.
15184
- # For example, to filter for instances that do not have a name of example-
15185
- # instance, you would use name ne example-instance.
15186
- # You can filter on nested fields. For example, you could filter on instances
15187
- # that have set the scheduling.automaticRestart field to true. Use filtering on
15188
- # nested fields to take advantage of labels to organize and search for results
15189
- # based on label values.
15111
+ # A filter expression that filters resources listed in the response. The
15112
+ # expression must specify the field name, a comparison operator, and the value
15113
+ # that you want to use for filtering. The value must be a string, a number, or a
15114
+ # boolean. The comparison operator must be either =, !=, >, or <.
15115
+ # For example, if you are filtering Compute Engine instances, you can exclude
15116
+ # instances named example-instance by specifying name != example-instance.
15117
+ # You can also filter nested fields. For example, you could specify scheduling.
15118
+ # automaticRestart = false to include instances only if they are not scheduled
15119
+ # for automatic restarts. You can use filtering on nested fields to filter based
15120
+ # on resource labels.
15190
15121
  # To filter on multiple expressions, provide each separate expression within
15191
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
15192
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
15193
- # resources must match all expressions to pass the filters.
15122
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
15123
+ # Intel Skylake"). By default, each expression is an AND expression. However,
15124
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
15125
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
15126
+ # automaticRestart = true).
15194
15127
  # @param [Fixnum] max_results
15195
15128
  # The maximum number of results per page that should be returned. If the number
15196
15129
  # of available results is larger than maxResults, Compute Engine returns a
@@ -15561,25 +15494,22 @@ module Google
15561
15494
  # @param [String] project
15562
15495
  # Project ID for this request.
15563
15496
  # @param [String] filter
15564
- # Sets a filter `expression` for filtering listed resources. Your `expression`
15565
- # must be in the format: field_name comparison_string literal_string.
15566
- # The field_name is the name of the field you want to compare. Only atomic field
15567
- # types are supported (string, number, boolean). The comparison_string must be
15568
- # either eq (equals) or ne (not equals). The literal_string is the string value
15569
- # to filter to. The literal value must be valid for the type of field you are
15570
- # filtering by (string, number, boolean). For string fields, the literal value
15571
- # is interpreted as a regular expression using RE2 syntax. The literal value
15572
- # must match the entire field.
15573
- # For example, to filter for instances that do not have a name of example-
15574
- # instance, you would use name ne example-instance.
15575
- # You can filter on nested fields. For example, you could filter on instances
15576
- # that have set the scheduling.automaticRestart field to true. Use filtering on
15577
- # nested fields to take advantage of labels to organize and search for results
15578
- # based on label values.
15497
+ # A filter expression that filters resources listed in the response. The
15498
+ # expression must specify the field name, a comparison operator, and the value
15499
+ # that you want to use for filtering. The value must be a string, a number, or a
15500
+ # boolean. The comparison operator must be either =, !=, >, or <.
15501
+ # For example, if you are filtering Compute Engine instances, you can exclude
15502
+ # instances named example-instance by specifying name != example-instance.
15503
+ # You can also filter nested fields. For example, you could specify scheduling.
15504
+ # automaticRestart = false to include instances only if they are not scheduled
15505
+ # for automatic restarts. You can use filtering on nested fields to filter based
15506
+ # on resource labels.
15579
15507
  # To filter on multiple expressions, provide each separate expression within
15580
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
15581
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
15582
- # resources must match all expressions to pass the filters.
15508
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
15509
+ # Intel Skylake"). By default, each expression is an AND expression. However,
15510
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
15511
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
15512
+ # automaticRestart = true).
15583
15513
  # @param [Fixnum] max_results
15584
15514
  # The maximum number of results per page that should be returned. If the number
15585
15515
  # of available results is larger than maxResults, Compute Engine returns a
@@ -15937,25 +15867,22 @@ module Google
15937
15867
  # @param [String] project
15938
15868
  # Project ID for this request.
15939
15869
  # @param [String] filter
15940
- # Sets a filter `expression` for filtering listed resources. Your `expression`
15941
- # must be in the format: field_name comparison_string literal_string.
15942
- # The field_name is the name of the field you want to compare. Only atomic field
15943
- # types are supported (string, number, boolean). The comparison_string must be
15944
- # either eq (equals) or ne (not equals). The literal_string is the string value
15945
- # to filter to. The literal value must be valid for the type of field you are
15946
- # filtering by (string, number, boolean). For string fields, the literal value
15947
- # is interpreted as a regular expression using RE2 syntax. The literal value
15948
- # must match the entire field.
15949
- # For example, to filter for instances that do not have a name of example-
15950
- # instance, you would use name ne example-instance.
15951
- # You can filter on nested fields. For example, you could filter on instances
15952
- # that have set the scheduling.automaticRestart field to true. Use filtering on
15953
- # nested fields to take advantage of labels to organize and search for results
15954
- # based on label values.
15870
+ # A filter expression that filters resources listed in the response. The
15871
+ # expression must specify the field name, a comparison operator, and the value
15872
+ # that you want to use for filtering. The value must be a string, a number, or a
15873
+ # boolean. The comparison operator must be either =, !=, >, or <.
15874
+ # For example, if you are filtering Compute Engine instances, you can exclude
15875
+ # instances named example-instance by specifying name != example-instance.
15876
+ # You can also filter nested fields. For example, you could specify scheduling.
15877
+ # automaticRestart = false to include instances only if they are not scheduled
15878
+ # for automatic restarts. You can use filtering on nested fields to filter based
15879
+ # on resource labels.
15955
15880
  # To filter on multiple expressions, provide each separate expression within
15956
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
15957
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
15958
- # resources must match all expressions to pass the filters.
15881
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
15882
+ # Intel Skylake"). By default, each expression is an AND expression. However,
15883
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
15884
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
15885
+ # automaticRestart = true).
15959
15886
  # @param [Fixnum] max_results
15960
15887
  # The maximum number of results per page that should be returned. If the number
15961
15888
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16119,25 +16046,22 @@ module Google
16119
16046
  # @param [String] project
16120
16047
  # Project ID for this request.
16121
16048
  # @param [String] filter
16122
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16123
- # must be in the format: field_name comparison_string literal_string.
16124
- # The field_name is the name of the field you want to compare. Only atomic field
16125
- # types are supported (string, number, boolean). The comparison_string must be
16126
- # either eq (equals) or ne (not equals). The literal_string is the string value
16127
- # to filter to. The literal value must be valid for the type of field you are
16128
- # filtering by (string, number, boolean). For string fields, the literal value
16129
- # is interpreted as a regular expression using RE2 syntax. The literal value
16130
- # must match the entire field.
16131
- # For example, to filter for instances that do not have a name of example-
16132
- # instance, you would use name ne example-instance.
16133
- # You can filter on nested fields. For example, you could filter on instances
16134
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16135
- # nested fields to take advantage of labels to organize and search for results
16136
- # based on label values.
16049
+ # A filter expression that filters resources listed in the response. The
16050
+ # expression must specify the field name, a comparison operator, and the value
16051
+ # that you want to use for filtering. The value must be a string, a number, or a
16052
+ # boolean. The comparison operator must be either =, !=, >, or <.
16053
+ # For example, if you are filtering Compute Engine instances, you can exclude
16054
+ # instances named example-instance by specifying name != example-instance.
16055
+ # You can also filter nested fields. For example, you could specify scheduling.
16056
+ # automaticRestart = false to include instances only if they are not scheduled
16057
+ # for automatic restarts. You can use filtering on nested fields to filter based
16058
+ # on resource labels.
16137
16059
  # To filter on multiple expressions, provide each separate expression within
16138
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16139
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16140
- # resources must match all expressions to pass the filters.
16060
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16061
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16062
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16063
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16064
+ # automaticRestart = true).
16141
16065
  # @param [Fixnum] max_results
16142
16066
  # The maximum number of results per page that should be returned. If the number
16143
16067
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16347,25 +16271,22 @@ module Google
16347
16271
  # @param [String] region
16348
16272
  # Name of the region for this request.
16349
16273
  # @param [String] filter
16350
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16351
- # must be in the format: field_name comparison_string literal_string.
16352
- # The field_name is the name of the field you want to compare. Only atomic field
16353
- # types are supported (string, number, boolean). The comparison_string must be
16354
- # either eq (equals) or ne (not equals). The literal_string is the string value
16355
- # to filter to. The literal value must be valid for the type of field you are
16356
- # filtering by (string, number, boolean). For string fields, the literal value
16357
- # is interpreted as a regular expression using RE2 syntax. The literal value
16358
- # must match the entire field.
16359
- # For example, to filter for instances that do not have a name of example-
16360
- # instance, you would use name ne example-instance.
16361
- # You can filter on nested fields. For example, you could filter on instances
16362
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16363
- # nested fields to take advantage of labels to organize and search for results
16364
- # based on label values.
16274
+ # A filter expression that filters resources listed in the response. The
16275
+ # expression must specify the field name, a comparison operator, and the value
16276
+ # that you want to use for filtering. The value must be a string, a number, or a
16277
+ # boolean. The comparison operator must be either =, !=, >, or <.
16278
+ # For example, if you are filtering Compute Engine instances, you can exclude
16279
+ # instances named example-instance by specifying name != example-instance.
16280
+ # You can also filter nested fields. For example, you could specify scheduling.
16281
+ # automaticRestart = false to include instances only if they are not scheduled
16282
+ # for automatic restarts. You can use filtering on nested fields to filter based
16283
+ # on resource labels.
16365
16284
  # To filter on multiple expressions, provide each separate expression within
16366
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16367
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16368
- # resources must match all expressions to pass the filters.
16285
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16286
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16287
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16288
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16289
+ # automaticRestart = true).
16369
16290
  # @param [Fixnum] max_results
16370
16291
  # The maximum number of results per page that should be returned. If the number
16371
16292
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16618,25 +16539,22 @@ module Google
16618
16539
  # @param [String] project
16619
16540
  # Project ID for this request.
16620
16541
  # @param [String] filter
16621
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16622
- # must be in the format: field_name comparison_string literal_string.
16623
- # The field_name is the name of the field you want to compare. Only atomic field
16624
- # types are supported (string, number, boolean). The comparison_string must be
16625
- # either eq (equals) or ne (not equals). The literal_string is the string value
16626
- # to filter to. The literal value must be valid for the type of field you are
16627
- # filtering by (string, number, boolean). For string fields, the literal value
16628
- # is interpreted as a regular expression using RE2 syntax. The literal value
16629
- # must match the entire field.
16630
- # For example, to filter for instances that do not have a name of example-
16631
- # instance, you would use name ne example-instance.
16632
- # You can filter on nested fields. For example, you could filter on instances
16633
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16634
- # nested fields to take advantage of labels to organize and search for results
16635
- # based on label values.
16542
+ # A filter expression that filters resources listed in the response. The
16543
+ # expression must specify the field name, a comparison operator, and the value
16544
+ # that you want to use for filtering. The value must be a string, a number, or a
16545
+ # boolean. The comparison operator must be either =, !=, >, or <.
16546
+ # For example, if you are filtering Compute Engine instances, you can exclude
16547
+ # instances named example-instance by specifying name != example-instance.
16548
+ # You can also filter nested fields. For example, you could specify scheduling.
16549
+ # automaticRestart = false to include instances only if they are not scheduled
16550
+ # for automatic restarts. You can use filtering on nested fields to filter based
16551
+ # on resource labels.
16636
16552
  # To filter on multiple expressions, provide each separate expression within
16637
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16638
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16639
- # resources must match all expressions to pass the filters.
16553
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16554
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16555
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16556
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16557
+ # automaticRestart = true).
16640
16558
  # @param [Fixnum] max_results
16641
16559
  # The maximum number of results per page that should be returned. If the number
16642
16560
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16844,25 +16762,22 @@ module Google
16844
16762
  # @param [String] project
16845
16763
  # Project ID for this request.
16846
16764
  # @param [String] filter
16847
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16848
- # must be in the format: field_name comparison_string literal_string.
16849
- # The field_name is the name of the field you want to compare. Only atomic field
16850
- # types are supported (string, number, boolean). The comparison_string must be
16851
- # either eq (equals) or ne (not equals). The literal_string is the string value
16852
- # to filter to. The literal value must be valid for the type of field you are
16853
- # filtering by (string, number, boolean). For string fields, the literal value
16854
- # is interpreted as a regular expression using RE2 syntax. The literal value
16855
- # must match the entire field.
16856
- # For example, to filter for instances that do not have a name of example-
16857
- # instance, you would use name ne example-instance.
16858
- # You can filter on nested fields. For example, you could filter on instances
16859
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16860
- # nested fields to take advantage of labels to organize and search for results
16861
- # based on label values.
16765
+ # A filter expression that filters resources listed in the response. The
16766
+ # expression must specify the field name, a comparison operator, and the value
16767
+ # that you want to use for filtering. The value must be a string, a number, or a
16768
+ # boolean. The comparison operator must be either =, !=, >, or <.
16769
+ # For example, if you are filtering Compute Engine instances, you can exclude
16770
+ # instances named example-instance by specifying name != example-instance.
16771
+ # You can also filter nested fields. For example, you could specify scheduling.
16772
+ # automaticRestart = false to include instances only if they are not scheduled
16773
+ # for automatic restarts. You can use filtering on nested fields to filter based
16774
+ # on resource labels.
16862
16775
  # To filter on multiple expressions, provide each separate expression within
16863
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16864
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16865
- # resources must match all expressions to pass the filters.
16776
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16777
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16778
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16779
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16780
+ # automaticRestart = true).
16866
16781
  # @param [Fixnum] max_results
16867
16782
  # The maximum number of results per page that should be returned. If the number
16868
16783
  # of available results is larger than maxResults, Compute Engine returns a
@@ -17072,25 +16987,22 @@ module Google
17072
16987
  # @param [String] region
17073
16988
  # Name of the region for this request.
17074
16989
  # @param [String] filter
17075
- # Sets a filter `expression` for filtering listed resources. Your `expression`
17076
- # must be in the format: field_name comparison_string literal_string.
17077
- # The field_name is the name of the field you want to compare. Only atomic field
17078
- # types are supported (string, number, boolean). The comparison_string must be
17079
- # either eq (equals) or ne (not equals). The literal_string is the string value
17080
- # to filter to. The literal value must be valid for the type of field you are
17081
- # filtering by (string, number, boolean). For string fields, the literal value
17082
- # is interpreted as a regular expression using RE2 syntax. The literal value
17083
- # must match the entire field.
17084
- # For example, to filter for instances that do not have a name of example-
17085
- # instance, you would use name ne example-instance.
17086
- # You can filter on nested fields. For example, you could filter on instances
17087
- # that have set the scheduling.automaticRestart field to true. Use filtering on
17088
- # nested fields to take advantage of labels to organize and search for results
17089
- # based on label values.
16990
+ # A filter expression that filters resources listed in the response. The
16991
+ # expression must specify the field name, a comparison operator, and the value
16992
+ # that you want to use for filtering. The value must be a string, a number, or a
16993
+ # boolean. The comparison operator must be either =, !=, >, or <.
16994
+ # For example, if you are filtering Compute Engine instances, you can exclude
16995
+ # instances named example-instance by specifying name != example-instance.
16996
+ # You can also filter nested fields. For example, you could specify scheduling.
16997
+ # automaticRestart = false to include instances only if they are not scheduled
16998
+ # for automatic restarts. You can use filtering on nested fields to filter based
16999
+ # on resource labels.
17090
17000
  # To filter on multiple expressions, provide each separate expression within
17091
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
17092
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
17093
- # resources must match all expressions to pass the filters.
17001
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
17002
+ # Intel Skylake"). By default, each expression is an AND expression. However,
17003
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
17004
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
17005
+ # automaticRestart = true).
17094
17006
  # @param [Fixnum] max_results
17095
17007
  # The maximum number of results per page that should be returned. If the number
17096
17008
  # of available results is larger than maxResults, Compute Engine returns a
@@ -17231,25 +17143,22 @@ module Google
17231
17143
  # @param [String] zone
17232
17144
  # Name of the zone for request.
17233
17145
  # @param [String] filter
17234
- # Sets a filter `expression` for filtering listed resources. Your `expression`
17235
- # must be in the format: field_name comparison_string literal_string.
17236
- # The field_name is the name of the field you want to compare. Only atomic field
17237
- # types are supported (string, number, boolean). The comparison_string must be
17238
- # either eq (equals) or ne (not equals). The literal_string is the string value
17239
- # to filter to. The literal value must be valid for the type of field you are
17240
- # filtering by (string, number, boolean). For string fields, the literal value
17241
- # is interpreted as a regular expression using RE2 syntax. The literal value
17242
- # must match the entire field.
17243
- # For example, to filter for instances that do not have a name of example-
17244
- # instance, you would use name ne example-instance.
17245
- # You can filter on nested fields. For example, you could filter on instances
17246
- # that have set the scheduling.automaticRestart field to true. Use filtering on
17247
- # nested fields to take advantage of labels to organize and search for results
17248
- # based on label values.
17146
+ # A filter expression that filters resources listed in the response. The
17147
+ # expression must specify the field name, a comparison operator, and the value
17148
+ # that you want to use for filtering. The value must be a string, a number, or a
17149
+ # boolean. The comparison operator must be either =, !=, >, or <.
17150
+ # For example, if you are filtering Compute Engine instances, you can exclude
17151
+ # instances named example-instance by specifying name != example-instance.
17152
+ # You can also filter nested fields. For example, you could specify scheduling.
17153
+ # automaticRestart = false to include instances only if they are not scheduled
17154
+ # for automatic restarts. You can use filtering on nested fields to filter based
17155
+ # on resource labels.
17249
17156
  # To filter on multiple expressions, provide each separate expression within
17250
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
17251
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
17252
- # resources must match all expressions to pass the filters.
17157
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
17158
+ # Intel Skylake"). By default, each expression is an AND expression. However,
17159
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
17160
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
17161
+ # automaticRestart = true).
17253
17162
  # @param [Fixnum] max_results
17254
17163
  # The maximum number of results per page that should be returned. If the number
17255
17164
  # of available results is larger than maxResults, Compute Engine returns a
@@ -17347,25 +17256,22 @@ module Google
17347
17256
  # @param [String] project
17348
17257
  # Project ID for this request.
17349
17258
  # @param [String] filter
17350
- # Sets a filter `expression` for filtering listed resources. Your `expression`
17351
- # must be in the format: field_name comparison_string literal_string.
17352
- # The field_name is the name of the field you want to compare. Only atomic field
17353
- # types are supported (string, number, boolean). The comparison_string must be
17354
- # either eq (equals) or ne (not equals). The literal_string is the string value
17355
- # to filter to. The literal value must be valid for the type of field you are
17356
- # filtering by (string, number, boolean). For string fields, the literal value
17357
- # is interpreted as a regular expression using RE2 syntax. The literal value
17358
- # must match the entire field.
17359
- # For example, to filter for instances that do not have a name of example-
17360
- # instance, you would use name ne example-instance.
17361
- # You can filter on nested fields. For example, you could filter on instances
17362
- # that have set the scheduling.automaticRestart field to true. Use filtering on
17363
- # nested fields to take advantage of labels to organize and search for results
17364
- # based on label values.
17259
+ # A filter expression that filters resources listed in the response. The
17260
+ # expression must specify the field name, a comparison operator, and the value
17261
+ # that you want to use for filtering. The value must be a string, a number, or a
17262
+ # boolean. The comparison operator must be either =, !=, >, or <.
17263
+ # For example, if you are filtering Compute Engine instances, you can exclude
17264
+ # instances named example-instance by specifying name != example-instance.
17265
+ # You can also filter nested fields. For example, you could specify scheduling.
17266
+ # automaticRestart = false to include instances only if they are not scheduled
17267
+ # for automatic restarts. You can use filtering on nested fields to filter based
17268
+ # on resource labels.
17365
17269
  # To filter on multiple expressions, provide each separate expression within
17366
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
17367
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
17368
- # resources must match all expressions to pass the filters.
17270
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
17271
+ # Intel Skylake"). By default, each expression is an AND expression. However,
17272
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
17273
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
17274
+ # automaticRestart = true).
17369
17275
  # @param [Fixnum] max_results
17370
17276
  # The maximum number of results per page that should be returned. If the number
17371
17277
  # of available results is larger than maxResults, Compute Engine returns a