google-api-client 0.19.8 → 0.20.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
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
@@ -2722,6 +2722,12 @@ module Google
2722
2722
  include Google::Apis::Core::JsonObjectSupport
2723
2723
  end
2724
2724
 
2725
+ class SchedulingNodeAffinity
2726
+ class Representation < Google::Apis::Core::JsonRepresentation; end
2727
+
2728
+ include Google::Apis::Core::JsonObjectSupport
2729
+ end
2730
+
2725
2731
  class SecurityPolicy
2726
2732
  class Representation < Google::Apis::Core::JsonRepresentation; end
2727
2733
 
@@ -3742,7 +3748,10 @@ module Google
3742
3748
  property :label_fingerprint, :base64 => true, as: 'labelFingerprint'
3743
3749
  hash :labels, as: 'labels'
3744
3750
  property :name, as: 'name'
3751
+ property :network, as: 'network'
3745
3752
  property :network_tier, as: 'networkTier'
3753
+ property :prefix_length, as: 'prefixLength'
3754
+ property :purpose, as: 'purpose'
3746
3755
  property :region, as: 'region'
3747
3756
  property :self_link, as: 'selfLink'
3748
3757
  property :status, as: 'status'
@@ -4409,6 +4418,7 @@ module Google
4409
4418
  property :start_timestamp, as: 'startTimestamp'
4410
4419
  property :status, as: 'status'
4411
4420
  property :status_message, as: 'statusMessage'
4421
+ property :type, as: 'type'
4412
4422
  end
4413
4423
  end
4414
4424
 
@@ -7170,7 +7180,6 @@ module Google
7170
7180
 
7171
7181
  property :override, as: 'override', class: Google::Apis::ComputeAlpha::ManagedInstanceOverride, decorator: Google::Apis::ComputeAlpha::ManagedInstanceOverride::Representation
7172
7182
 
7173
- property :standby_mode, as: 'standbyMode'
7174
7183
  property :tag, as: 'tag'
7175
7184
  property :version, as: 'version', class: Google::Apis::ComputeAlpha::ManagedInstanceVersion, decorator: Google::Apis::ComputeAlpha::ManagedInstanceVersion::Representation
7176
7185
 
@@ -8571,11 +8580,22 @@ module Google
8571
8580
  # @private
8572
8581
  class Representation < Google::Apis::Core::JsonRepresentation
8573
8582
  property :automatic_restart, as: 'automaticRestart'
8583
+ collection :node_affinities, as: 'nodeAffinities', class: Google::Apis::ComputeAlpha::SchedulingNodeAffinity, decorator: Google::Apis::ComputeAlpha::SchedulingNodeAffinity::Representation
8584
+
8574
8585
  property :on_host_maintenance, as: 'onHostMaintenance'
8575
8586
  property :preemptible, as: 'preemptible'
8576
8587
  end
8577
8588
  end
8578
8589
 
8590
+ class SchedulingNodeAffinity
8591
+ # @private
8592
+ class Representation < Google::Apis::Core::JsonRepresentation
8593
+ property :key, as: 'key'
8594
+ property :operator, as: 'operator'
8595
+ collection :values, as: 'values'
8596
+ end
8597
+ end
8598
+
8579
8599
  class SecurityPolicy
8580
8600
  # @private
8581
8601
  class Representation < Google::Apis::Core::JsonRepresentation
@@ -8683,6 +8703,7 @@ module Google
8683
8703
  class ShieldedVmConfig
8684
8704
  # @private
8685
8705
  class Representation < Google::Apis::Core::JsonRepresentation
8706
+ property :enable_integrity_monitoring, as: 'enableIntegrityMonitoring'
8686
8707
  property :enable_secure_boot, as: 'enableSecureBoot'
8687
8708
  property :enable_vtpm, as: 'enableVtpm'
8688
8709
  end
@@ -8702,6 +8723,8 @@ module Google
8702
8723
  property :creation_timestamp, as: 'creationTimestamp'
8703
8724
  property :description, as: 'description'
8704
8725
  property :disk_size_gb, :numeric_string => true, as: 'diskSizeGb'
8726
+ collection :guest_os_features, as: 'guestOsFeatures', class: Google::Apis::ComputeAlpha::GuestOsFeature, decorator: Google::Apis::ComputeAlpha::GuestOsFeature::Representation
8727
+
8705
8728
  property :id, :numeric_string => true, as: 'id'
8706
8729
  property :kind, as: 'kind'
8707
8730
  property :label_fingerprint, :base64 => true, as: 'labelFingerprint'
@@ -8951,6 +8974,7 @@ module Google
8951
8974
  property :gateway_address, as: 'gatewayAddress'
8952
8975
  property :id, :numeric_string => true, as: 'id'
8953
8976
  property :ip_cidr_range, as: 'ipCidrRange'
8977
+ property :ipv6_cidr_range, as: 'ipv6CidrRange'
8954
8978
  property :kind, as: 'kind'
8955
8979
  property :name, as: 'name'
8956
8980
  property :network, as: 'network'
@@ -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
@@ -658,25 +646,22 @@ module Google
658
646
  # @param [String] project
659
647
  # Project ID for this request.
660
648
  # @param [String] filter
661
- # Sets a filter `expression` for filtering listed resources. Your `expression`
662
- # must be in the format: field_name comparison_string literal_string.
663
- # The field_name is the name of the field you want to compare. Only atomic field
664
- # types are supported (string, number, boolean). The comparison_string must be
665
- # either eq (equals) or ne (not equals). The literal_string is the string value
666
- # to filter to. The literal value must be valid for the type of field you are
667
- # filtering by (string, number, boolean). For string fields, the literal value
668
- # is interpreted as a regular expression using RE2 syntax. The literal value
669
- # must match the entire field.
670
- # For example, to filter for instances that do not have a name of example-
671
- # instance, you would use name ne example-instance.
672
- # You can filter on nested fields. For example, you could filter on instances
673
- # that have set the scheduling.automaticRestart field to true. Use filtering on
674
- # nested fields to take advantage of labels to organize and search for results
675
- # based on label values.
649
+ # A filter expression that filters resources listed in the response. The
650
+ # expression must specify the field name, a comparison operator, and the value
651
+ # that you want to use for filtering. The value must be a string, a number, or a
652
+ # boolean. The comparison operator must be either =, !=, >, or <.
653
+ # For example, if you are filtering Compute Engine instances, you can exclude
654
+ # instances named example-instance by specifying name != example-instance.
655
+ # You can also filter nested fields. For example, you could specify scheduling.
656
+ # automaticRestart = false to include instances only if they are not scheduled
657
+ # for automatic restarts. You can use filtering on nested fields to filter based
658
+ # on resource labels.
676
659
  # To filter on multiple expressions, provide each separate expression within
677
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
678
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
679
- # resources must match all expressions to pass the filters.
660
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
661
+ # Intel Skylake"). By default, each expression is an AND expression. However,
662
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
663
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
664
+ # automaticRestart = true).
680
665
  # @param [Fixnum] max_results
681
666
  # The maximum number of results per page that should be returned. If the number
682
667
  # of available results is larger than maxResults, Compute Engine returns a
@@ -885,25 +870,22 @@ module Google
885
870
  # @param [String] zone
886
871
  # Name of the zone for this request.
887
872
  # @param [String] filter
888
- # Sets a filter `expression` for filtering listed resources. Your `expression`
889
- # must be in the format: field_name comparison_string literal_string.
890
- # The field_name is the name of the field you want to compare. Only atomic field
891
- # types are supported (string, number, boolean). The comparison_string must be
892
- # either eq (equals) or ne (not equals). The literal_string is the string value
893
- # to filter to. The literal value must be valid for the type of field you are
894
- # filtering by (string, number, boolean). For string fields, the literal value
895
- # is interpreted as a regular expression using RE2 syntax. The literal value
896
- # must match the entire field.
897
- # For example, to filter for instances that do not have a name of example-
898
- # instance, you would use name ne example-instance.
899
- # You can filter on nested fields. For example, you could filter on instances
900
- # that have set the scheduling.automaticRestart field to true. Use filtering on
901
- # nested fields to take advantage of labels to organize and search for results
902
- # based on label values.
873
+ # A filter expression that filters resources listed in the response. The
874
+ # expression must specify the field name, a comparison operator, and the value
875
+ # that you want to use for filtering. The value must be a string, a number, or a
876
+ # boolean. The comparison operator must be either =, !=, >, or <.
877
+ # For example, if you are filtering Compute Engine instances, you can exclude
878
+ # instances named example-instance by specifying name != example-instance.
879
+ # You can also filter nested fields. For example, you could specify scheduling.
880
+ # automaticRestart = false to include instances only if they are not scheduled
881
+ # for automatic restarts. You can use filtering on nested fields to filter based
882
+ # on resource labels.
903
883
  # To filter on multiple expressions, provide each separate expression within
904
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
905
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
906
- # resources must match all expressions to pass the filters.
884
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
885
+ # Intel Skylake"). By default, each expression is an AND expression. However,
886
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
887
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
888
+ # automaticRestart = true).
907
889
  # @param [Fixnum] max_results
908
890
  # The maximum number of results per page that should be returned. If the number
909
891
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1409,25 +1391,22 @@ module Google
1409
1391
  # @param [String] project
1410
1392
  # Project ID for this request.
1411
1393
  # @param [String] filter
1412
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1413
- # must be in the format: field_name comparison_string literal_string.
1414
- # The field_name is the name of the field you want to compare. Only atomic field
1415
- # types are supported (string, number, boolean). The comparison_string must be
1416
- # either eq (equals) or ne (not equals). The literal_string is the string value
1417
- # to filter to. The literal value must be valid for the type of field you are
1418
- # filtering by (string, number, boolean). For string fields, the literal value
1419
- # is interpreted as a regular expression using RE2 syntax. The literal value
1420
- # must match the entire field.
1421
- # For example, to filter for instances that do not have a name of example-
1422
- # instance, you would use name ne example-instance.
1423
- # You can filter on nested fields. For example, you could filter on instances
1424
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1425
- # nested fields to take advantage of labels to organize and search for results
1426
- # based on label values.
1394
+ # A filter expression that filters resources listed in the response. The
1395
+ # expression must specify the field name, a comparison operator, and the value
1396
+ # that you want to use for filtering. The value must be a string, a number, or a
1397
+ # boolean. The comparison operator must be either =, !=, >, or <.
1398
+ # For example, if you are filtering Compute Engine instances, you can exclude
1399
+ # instances named example-instance by specifying name != example-instance.
1400
+ # You can also filter nested fields. For example, you could specify scheduling.
1401
+ # automaticRestart = false to include instances only if they are not scheduled
1402
+ # for automatic restarts. You can use filtering on nested fields to filter based
1403
+ # on resource labels.
1427
1404
  # To filter on multiple expressions, provide each separate expression within
1428
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1429
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1430
- # resources must match all expressions to pass the filters.
1405
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1406
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1407
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1408
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1409
+ # automaticRestart = true).
1431
1410
  # @param [Fixnum] max_results
1432
1411
  # The maximum number of results per page that should be returned. If the number
1433
1412
  # of available results is larger than maxResults, Compute Engine returns a
@@ -1732,25 +1711,22 @@ module Google
1732
1711
  # @param [String] project
1733
1712
  # Name of the project scoping this request.
1734
1713
  # @param [String] filter
1735
- # Sets a filter `expression` for filtering listed resources. Your `expression`
1736
- # must be in the format: field_name comparison_string literal_string.
1737
- # The field_name is the name of the field you want to compare. Only atomic field
1738
- # types are supported (string, number, boolean). The comparison_string must be
1739
- # either eq (equals) or ne (not equals). The literal_string is the string value
1740
- # to filter to. The literal value must be valid for the type of field you are
1741
- # filtering by (string, number, boolean). For string fields, the literal value
1742
- # is interpreted as a regular expression using RE2 syntax. The literal value
1743
- # must match the entire field.
1744
- # For example, to filter for instances that do not have a name of example-
1745
- # instance, you would use name ne example-instance.
1746
- # You can filter on nested fields. For example, you could filter on instances
1747
- # that have set the scheduling.automaticRestart field to true. Use filtering on
1748
- # nested fields to take advantage of labels to organize and search for results
1749
- # based on label values.
1714
+ # A filter expression that filters resources listed in the response. The
1715
+ # expression must specify the field name, a comparison operator, and the value
1716
+ # that you want to use for filtering. The value must be a string, a number, or a
1717
+ # boolean. The comparison operator must be either =, !=, >, or <.
1718
+ # For example, if you are filtering Compute Engine instances, you can exclude
1719
+ # instances named example-instance by specifying name != example-instance.
1720
+ # You can also filter nested fields. For example, you could specify scheduling.
1721
+ # automaticRestart = false to include instances only if they are not scheduled
1722
+ # for automatic restarts. You can use filtering on nested fields to filter based
1723
+ # on resource labels.
1750
1724
  # To filter on multiple expressions, provide each separate expression within
1751
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
1752
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
1753
- # resources must match all expressions to pass the filters.
1725
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
1726
+ # Intel Skylake"). By default, each expression is an AND expression. However,
1727
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
1728
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1729
+ # automaticRestart = true).
1754
1730
  # @param [Fixnum] max_results
1755
1731
  # The maximum number of results per page that should be returned. If the number
1756
1732
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2045,25 +2021,22 @@ module Google
2045
2021
  # @param [String] project
2046
2022
  # Project ID for this request.
2047
2023
  # @param [String] filter
2048
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2049
- # must be in the format: field_name comparison_string literal_string.
2050
- # The field_name is the name of the field you want to compare. Only atomic field
2051
- # types are supported (string, number, boolean). The comparison_string must be
2052
- # either eq (equals) or ne (not equals). The literal_string is the string value
2053
- # to filter to. The literal value must be valid for the type of field you are
2054
- # filtering by (string, number, boolean). For string fields, the literal value
2055
- # is interpreted as a regular expression using RE2 syntax. The literal value
2056
- # must match the entire field.
2057
- # For example, to filter for instances that do not have a name of example-
2058
- # instance, you would use name ne example-instance.
2059
- # You can filter on nested fields. For example, you could filter on instances
2060
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2061
- # nested fields to take advantage of labels to organize and search for results
2062
- # based on label values.
2024
+ # A filter expression that filters resources listed in the response. The
2025
+ # expression must specify the field name, a comparison operator, and the value
2026
+ # that you want to use for filtering. The value must be a string, a number, or a
2027
+ # boolean. The comparison operator must be either =, !=, >, or <.
2028
+ # For example, if you are filtering Compute Engine instances, you can exclude
2029
+ # instances named example-instance by specifying name != example-instance.
2030
+ # You can also filter nested fields. For example, you could specify scheduling.
2031
+ # automaticRestart = false to include instances only if they are not scheduled
2032
+ # for automatic restarts. You can use filtering on nested fields to filter based
2033
+ # on resource labels.
2063
2034
  # To filter on multiple expressions, provide each separate expression within
2064
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2065
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2066
- # resources must match all expressions to pass the filters.
2035
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2036
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2037
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2038
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2039
+ # automaticRestart = true).
2067
2040
  # @param [Fixnum] max_results
2068
2041
  # The maximum number of results per page that should be returned. If the number
2069
2042
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2370,25 +2343,22 @@ module Google
2370
2343
  # @param [String] project
2371
2344
  # Project ID for this request.
2372
2345
  # @param [String] filter
2373
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2374
- # must be in the format: field_name comparison_string literal_string.
2375
- # The field_name is the name of the field you want to compare. Only atomic field
2376
- # types are supported (string, number, boolean). The comparison_string must be
2377
- # either eq (equals) or ne (not equals). The literal_string is the string value
2378
- # to filter to. The literal value must be valid for the type of field you are
2379
- # filtering by (string, number, boolean). For string fields, the literal value
2380
- # is interpreted as a regular expression using RE2 syntax. The literal value
2381
- # must match the entire field.
2382
- # For example, to filter for instances that do not have a name of example-
2383
- # instance, you would use name ne example-instance.
2384
- # You can filter on nested fields. For example, you could filter on instances
2385
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2386
- # nested fields to take advantage of labels to organize and search for results
2387
- # based on label values.
2346
+ # A filter expression that filters resources listed in the response. The
2347
+ # expression must specify the field name, a comparison operator, and the value
2348
+ # that you want to use for filtering. The value must be a string, a number, or a
2349
+ # boolean. The comparison operator must be either =, !=, >, or <.
2350
+ # For example, if you are filtering Compute Engine instances, you can exclude
2351
+ # instances named example-instance by specifying name != example-instance.
2352
+ # You can also filter nested fields. For example, you could specify scheduling.
2353
+ # automaticRestart = false to include instances only if they are not scheduled
2354
+ # for automatic restarts. You can use filtering on nested fields to filter based
2355
+ # on resource labels.
2388
2356
  # To filter on multiple expressions, provide each separate expression within
2389
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2390
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2391
- # resources must match all expressions to pass the filters.
2357
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2358
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2359
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2360
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2361
+ # automaticRestart = true).
2392
2362
  # @param [Fixnum] max_results
2393
2363
  # The maximum number of results per page that should be returned. If the number
2394
2364
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2490,25 +2460,22 @@ module Google
2490
2460
  # @param [String] zone
2491
2461
  # The name of the zone for this request.
2492
2462
  # @param [String] filter
2493
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2494
- # must be in the format: field_name comparison_string literal_string.
2495
- # The field_name is the name of the field you want to compare. Only atomic field
2496
- # types are supported (string, number, boolean). The comparison_string must be
2497
- # either eq (equals) or ne (not equals). The literal_string is the string value
2498
- # to filter to. The literal value must be valid for the type of field you are
2499
- # filtering by (string, number, boolean). For string fields, the literal value
2500
- # is interpreted as a regular expression using RE2 syntax. The literal value
2501
- # must match the entire field.
2502
- # For example, to filter for instances that do not have a name of example-
2503
- # instance, you would use name ne example-instance.
2504
- # You can filter on nested fields. For example, you could filter on instances
2505
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2506
- # nested fields to take advantage of labels to organize and search for results
2507
- # based on label values.
2463
+ # A filter expression that filters resources listed in the response. The
2464
+ # expression must specify the field name, a comparison operator, and the value
2465
+ # that you want to use for filtering. The value must be a string, a number, or a
2466
+ # boolean. The comparison operator must be either =, !=, >, or <.
2467
+ # For example, if you are filtering Compute Engine instances, you can exclude
2468
+ # instances named example-instance by specifying name != example-instance.
2469
+ # You can also filter nested fields. For example, you could specify scheduling.
2470
+ # automaticRestart = false to include instances only if they are not scheduled
2471
+ # for automatic restarts. You can use filtering on nested fields to filter based
2472
+ # on resource labels.
2508
2473
  # To filter on multiple expressions, provide each separate expression within
2509
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2510
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2511
- # resources must match all expressions to pass the filters.
2474
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2475
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2476
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2477
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2478
+ # automaticRestart = true).
2512
2479
  # @param [Fixnum] max_results
2513
2480
  # The maximum number of results per page that should be returned. If the number
2514
2481
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2567,25 +2534,22 @@ module Google
2567
2534
  # @param [String] project
2568
2535
  # Project ID for this request.
2569
2536
  # @param [String] filter
2570
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2571
- # must be in the format: field_name comparison_string literal_string.
2572
- # The field_name is the name of the field you want to compare. Only atomic field
2573
- # types are supported (string, number, boolean). The comparison_string must be
2574
- # either eq (equals) or ne (not equals). The literal_string is the string value
2575
- # to filter to. The literal value must be valid for the type of field you are
2576
- # filtering by (string, number, boolean). For string fields, the literal value
2577
- # is interpreted as a regular expression using RE2 syntax. The literal value
2578
- # must match the entire field.
2579
- # For example, to filter for instances that do not have a name of example-
2580
- # instance, you would use name ne example-instance.
2581
- # You can filter on nested fields. For example, you could filter on instances
2582
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2583
- # nested fields to take advantage of labels to organize and search for results
2584
- # based on label values.
2537
+ # A filter expression that filters resources listed in the response. The
2538
+ # expression must specify the field name, a comparison operator, and the value
2539
+ # that you want to use for filtering. The value must be a string, a number, or a
2540
+ # boolean. The comparison operator must be either =, !=, >, or <.
2541
+ # For example, if you are filtering Compute Engine instances, you can exclude
2542
+ # instances named example-instance by specifying name != example-instance.
2543
+ # You can also filter nested fields. For example, you could specify scheduling.
2544
+ # automaticRestart = false to include instances only if they are not scheduled
2545
+ # for automatic restarts. You can use filtering on nested fields to filter based
2546
+ # on resource labels.
2585
2547
  # To filter on multiple expressions, provide each separate expression within
2586
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2587
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2588
- # resources must match all expressions to pass the filters.
2548
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2549
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2550
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2551
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2552
+ # automaticRestart = true).
2589
2553
  # @param [Fixnum] max_results
2590
2554
  # The maximum number of results per page that should be returned. If the number
2591
2555
  # of available results is larger than maxResults, Compute Engine returns a
@@ -2901,25 +2865,22 @@ module Google
2901
2865
  # @param [String] zone
2902
2866
  # The name of the zone for this request.
2903
2867
  # @param [String] filter
2904
- # Sets a filter `expression` for filtering listed resources. Your `expression`
2905
- # must be in the format: field_name comparison_string literal_string.
2906
- # The field_name is the name of the field you want to compare. Only atomic field
2907
- # types are supported (string, number, boolean). The comparison_string must be
2908
- # either eq (equals) or ne (not equals). The literal_string is the string value
2909
- # to filter to. The literal value must be valid for the type of field you are
2910
- # filtering by (string, number, boolean). For string fields, the literal value
2911
- # is interpreted as a regular expression using RE2 syntax. The literal value
2912
- # must match the entire field.
2913
- # For example, to filter for instances that do not have a name of example-
2914
- # instance, you would use name ne example-instance.
2915
- # You can filter on nested fields. For example, you could filter on instances
2916
- # that have set the scheduling.automaticRestart field to true. Use filtering on
2917
- # nested fields to take advantage of labels to organize and search for results
2918
- # based on label values.
2868
+ # A filter expression that filters resources listed in the response. The
2869
+ # expression must specify the field name, a comparison operator, and the value
2870
+ # that you want to use for filtering. The value must be a string, a number, or a
2871
+ # boolean. The comparison operator must be either =, !=, >, or <.
2872
+ # For example, if you are filtering Compute Engine instances, you can exclude
2873
+ # instances named example-instance by specifying name != example-instance.
2874
+ # You can also filter nested fields. For example, you could specify scheduling.
2875
+ # automaticRestart = false to include instances only if they are not scheduled
2876
+ # for automatic restarts. You can use filtering on nested fields to filter based
2877
+ # on resource labels.
2919
2878
  # To filter on multiple expressions, provide each separate expression within
2920
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
2921
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
2922
- # resources must match all expressions to pass the filters.
2879
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
2880
+ # Intel Skylake"). By default, each expression is an AND expression. However,
2881
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
2882
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
2883
+ # automaticRestart = true).
2923
2884
  # @param [Fixnum] max_results
2924
2885
  # The maximum number of results per page that should be returned. If the number
2925
2886
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3320,25 +3281,22 @@ module Google
3320
3281
  # @param [String] project
3321
3282
  # Project ID for this request.
3322
3283
  # @param [String] filter
3323
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3324
- # must be in the format: field_name comparison_string literal_string.
3325
- # The field_name is the name of the field you want to compare. Only atomic field
3326
- # types are supported (string, number, boolean). The comparison_string must be
3327
- # either eq (equals) or ne (not equals). The literal_string is the string value
3328
- # to filter to. The literal value must be valid for the type of field you are
3329
- # filtering by (string, number, boolean). For string fields, the literal value
3330
- # is interpreted as a regular expression using RE2 syntax. The literal value
3331
- # must match the entire field.
3332
- # For example, to filter for instances that do not have a name of example-
3333
- # instance, you would use name ne example-instance.
3334
- # You can filter on nested fields. For example, you could filter on instances
3335
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3336
- # nested fields to take advantage of labels to organize and search for results
3337
- # based on label values.
3284
+ # A filter expression that filters resources listed in the response. The
3285
+ # expression must specify the field name, a comparison operator, and the value
3286
+ # that you want to use for filtering. The value must be a string, a number, or a
3287
+ # boolean. The comparison operator must be either =, !=, >, or <.
3288
+ # For example, if you are filtering Compute Engine instances, you can exclude
3289
+ # instances named example-instance by specifying name != example-instance.
3290
+ # You can also filter nested fields. For example, you could specify scheduling.
3291
+ # automaticRestart = false to include instances only if they are not scheduled
3292
+ # for automatic restarts. You can use filtering on nested fields to filter based
3293
+ # on resource labels.
3338
3294
  # To filter on multiple expressions, provide each separate expression within
3339
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3340
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3341
- # resources must match all expressions to pass the filters.
3295
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3296
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3297
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3298
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3299
+ # automaticRestart = true).
3342
3300
  # @param [Fixnum] max_results
3343
3301
  # The maximum number of results per page that should be returned. If the number
3344
3302
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3547,25 +3505,22 @@ module Google
3547
3505
  # @param [String] project
3548
3506
  # Project ID for this request.
3549
3507
  # @param [String] filter
3550
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3551
- # must be in the format: field_name comparison_string literal_string.
3552
- # The field_name is the name of the field you want to compare. Only atomic field
3553
- # types are supported (string, number, boolean). The comparison_string must be
3554
- # either eq (equals) or ne (not equals). The literal_string is the string value
3555
- # to filter to. The literal value must be valid for the type of field you are
3556
- # filtering by (string, number, boolean). For string fields, the literal value
3557
- # is interpreted as a regular expression using RE2 syntax. The literal value
3558
- # must match the entire field.
3559
- # For example, to filter for instances that do not have a name of example-
3560
- # instance, you would use name ne example-instance.
3561
- # You can filter on nested fields. For example, you could filter on instances
3562
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3563
- # nested fields to take advantage of labels to organize and search for results
3564
- # based on label values.
3508
+ # A filter expression that filters resources listed in the response. The
3509
+ # expression must specify the field name, a comparison operator, and the value
3510
+ # that you want to use for filtering. The value must be a string, a number, or a
3511
+ # boolean. The comparison operator must be either =, !=, >, or <.
3512
+ # For example, if you are filtering Compute Engine instances, you can exclude
3513
+ # instances named example-instance by specifying name != example-instance.
3514
+ # You can also filter nested fields. For example, you could specify scheduling.
3515
+ # automaticRestart = false to include instances only if they are not scheduled
3516
+ # for automatic restarts. You can use filtering on nested fields to filter based
3517
+ # on resource labels.
3565
3518
  # To filter on multiple expressions, provide each separate expression within
3566
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3567
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3568
- # resources must match all expressions to pass the filters.
3519
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3520
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3521
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3522
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3523
+ # automaticRestart = true).
3569
3524
  # @param [Fixnum] max_results
3570
3525
  # The maximum number of results per page that should be returned. If the number
3571
3526
  # of available results is larger than maxResults, Compute Engine returns a
@@ -3774,25 +3729,22 @@ module Google
3774
3729
  # @param [String] region
3775
3730
  # Name of the region scoping this request.
3776
3731
  # @param [String] filter
3777
- # Sets a filter `expression` for filtering listed resources. Your `expression`
3778
- # must be in the format: field_name comparison_string literal_string.
3779
- # The field_name is the name of the field you want to compare. Only atomic field
3780
- # types are supported (string, number, boolean). The comparison_string must be
3781
- # either eq (equals) or ne (not equals). The literal_string is the string value
3782
- # to filter to. The literal value must be valid for the type of field you are
3783
- # filtering by (string, number, boolean). For string fields, the literal value
3784
- # is interpreted as a regular expression using RE2 syntax. The literal value
3785
- # must match the entire field.
3786
- # For example, to filter for instances that do not have a name of example-
3787
- # instance, you would use name ne example-instance.
3788
- # You can filter on nested fields. For example, you could filter on instances
3789
- # that have set the scheduling.automaticRestart field to true. Use filtering on
3790
- # nested fields to take advantage of labels to organize and search for results
3791
- # based on label values.
3732
+ # A filter expression that filters resources listed in the response. The
3733
+ # expression must specify the field name, a comparison operator, and the value
3734
+ # that you want to use for filtering. The value must be a string, a number, or a
3735
+ # boolean. The comparison operator must be either =, !=, >, or <.
3736
+ # For example, if you are filtering Compute Engine instances, you can exclude
3737
+ # instances named example-instance by specifying name != example-instance.
3738
+ # You can also filter nested fields. For example, you could specify scheduling.
3739
+ # automaticRestart = false to include instances only if they are not scheduled
3740
+ # for automatic restarts. You can use filtering on nested fields to filter based
3741
+ # on resource labels.
3792
3742
  # To filter on multiple expressions, provide each separate expression within
3793
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
3794
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
3795
- # resources must match all expressions to pass the filters.
3743
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
3744
+ # Intel Skylake"). By default, each expression is an AND expression. However,
3745
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
3746
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
3747
+ # automaticRestart = true).
3796
3748
  # @param [Fixnum] max_results
3797
3749
  # The maximum number of results per page that should be returned. If the number
3798
3750
  # of available results is larger than maxResults, Compute Engine returns a
@@ -4207,25 +4159,22 @@ module Google
4207
4159
  # @param [String] project
4208
4160
  # Project ID for this request.
4209
4161
  # @param [String] filter
4210
- # Sets a filter `expression` for filtering listed resources. Your `expression`
4211
- # must be in the format: field_name comparison_string literal_string.
4212
- # The field_name is the name of the field you want to compare. Only atomic field
4213
- # types are supported (string, number, boolean). The comparison_string must be
4214
- # either eq (equals) or ne (not equals). The literal_string is the string value
4215
- # to filter to. The literal value must be valid for the type of field you are
4216
- # filtering by (string, number, boolean). For string fields, the literal value
4217
- # is interpreted as a regular expression using RE2 syntax. The literal value
4218
- # must match the entire field.
4219
- # For example, to filter for instances that do not have a name of example-
4220
- # instance, you would use name ne example-instance.
4221
- # You can filter on nested fields. For example, you could filter on instances
4222
- # that have set the scheduling.automaticRestart field to true. Use filtering on
4223
- # nested fields to take advantage of labels to organize and search for results
4224
- # based on label values.
4162
+ # A filter expression that filters resources listed in the response. The
4163
+ # expression must specify the field name, a comparison operator, and the value
4164
+ # that you want to use for filtering. The value must be a string, a number, or a
4165
+ # boolean. The comparison operator must be either =, !=, >, or <.
4166
+ # For example, if you are filtering Compute Engine instances, you can exclude
4167
+ # instances named example-instance by specifying name != example-instance.
4168
+ # You can also filter nested fields. For example, you could specify scheduling.
4169
+ # automaticRestart = false to include instances only if they are not scheduled
4170
+ # for automatic restarts. You can use filtering on nested fields to filter based
4171
+ # on resource labels.
4225
4172
  # To filter on multiple expressions, provide each separate expression within
4226
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
4227
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
4228
- # resources must match all expressions to pass the filters.
4173
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
4174
+ # Intel Skylake"). By default, each expression is an AND expression. However,
4175
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
4176
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
4177
+ # automaticRestart = true).
4229
4178
  # @param [Fixnum] max_results
4230
4179
  # The maximum number of results per page that should be returned. If the number
4231
4180
  # of available results is larger than maxResults, Compute Engine returns a
@@ -4507,25 +4456,22 @@ module Google
4507
4456
  # @param [String] project
4508
4457
  # Project ID for this request.
4509
4458
  # @param [String] filter
4510
- # Sets a filter `expression` for filtering listed resources. Your `expression`
4511
- # must be in the format: field_name comparison_string literal_string.
4512
- # The field_name is the name of the field you want to compare. Only atomic field
4513
- # types are supported (string, number, boolean). The comparison_string must be
4514
- # either eq (equals) or ne (not equals). The literal_string is the string value
4515
- # to filter to. The literal value must be valid for the type of field you are
4516
- # filtering by (string, number, boolean). For string fields, the literal value
4517
- # is interpreted as a regular expression using RE2 syntax. The literal value
4518
- # must match the entire field.
4519
- # For example, to filter for instances that do not have a name of example-
4520
- # instance, you would use name ne example-instance.
4521
- # You can filter on nested fields. For example, you could filter on instances
4522
- # that have set the scheduling.automaticRestart field to true. Use filtering on
4523
- # nested fields to take advantage of labels to organize and search for results
4524
- # based on label values.
4459
+ # A filter expression that filters resources listed in the response. The
4460
+ # expression must specify the field name, a comparison operator, and the value
4461
+ # that you want to use for filtering. The value must be a string, a number, or a
4462
+ # boolean. The comparison operator must be either =, !=, >, or <.
4463
+ # For example, if you are filtering Compute Engine instances, you can exclude
4464
+ # instances named example-instance by specifying name != example-instance.
4465
+ # You can also filter nested fields. For example, you could specify scheduling.
4466
+ # automaticRestart = false to include instances only if they are not scheduled
4467
+ # for automatic restarts. You can use filtering on nested fields to filter based
4468
+ # on resource labels.
4525
4469
  # To filter on multiple expressions, provide each separate expression within
4526
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
4527
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
4528
- # resources must match all expressions to pass the filters.
4470
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
4471
+ # Intel Skylake"). By default, each expression is an AND expression. However,
4472
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
4473
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
4474
+ # automaticRestart = true).
4529
4475
  # @param [Fixnum] max_results
4530
4476
  # The maximum number of results per page that should be returned. If the number
4531
4477
  # of available results is larger than maxResults, Compute Engine returns a
@@ -4775,25 +4721,22 @@ module Google
4775
4721
  # @param [String] project
4776
4722
  # Project ID for this request.
4777
4723
  # @param [String] filter
4778
- # Sets a filter `expression` for filtering listed resources. Your `expression`
4779
- # must be in the format: field_name comparison_string literal_string.
4780
- # The field_name is the name of the field you want to compare. Only atomic field
4781
- # types are supported (string, number, boolean). The comparison_string must be
4782
- # either eq (equals) or ne (not equals). The literal_string is the string value
4783
- # to filter to. The literal value must be valid for the type of field you are
4784
- # filtering by (string, number, boolean). For string fields, the literal value
4785
- # is interpreted as a regular expression using RE2 syntax. The literal value
4786
- # must match the entire field.
4787
- # For example, to filter for instances that do not have a name of example-
4788
- # instance, you would use name ne example-instance.
4789
- # You can filter on nested fields. For example, you could filter on instances
4790
- # that have set the scheduling.automaticRestart field to true. Use filtering on
4791
- # nested fields to take advantage of labels to organize and search for results
4792
- # based on label values.
4724
+ # A filter expression that filters resources listed in the response. The
4725
+ # expression must specify the field name, a comparison operator, and the value
4726
+ # that you want to use for filtering. The value must be a string, a number, or a
4727
+ # boolean. The comparison operator must be either =, !=, >, or <.
4728
+ # For example, if you are filtering Compute Engine instances, you can exclude
4729
+ # instances named example-instance by specifying name != example-instance.
4730
+ # You can also filter nested fields. For example, you could specify scheduling.
4731
+ # automaticRestart = false to include instances only if they are not scheduled
4732
+ # for automatic restarts. You can use filtering on nested fields to filter based
4733
+ # on resource labels.
4793
4734
  # To filter on multiple expressions, provide each separate expression within
4794
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
4795
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
4796
- # resources must match all expressions to pass the filters.
4735
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
4736
+ # Intel Skylake"). By default, each expression is an AND expression. However,
4737
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
4738
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
4739
+ # automaticRestart = true).
4797
4740
  # @param [Fixnum] max_results
4798
4741
  # The maximum number of results per page that should be returned. If the number
4799
4742
  # of available results is larger than maxResults, Compute Engine returns a
@@ -4926,25 +4869,22 @@ module Google
4926
4869
  # @param [String] project
4927
4870
  # Project ID for this request.
4928
4871
  # @param [String] filter
4929
- # Sets a filter `expression` for filtering listed resources. Your `expression`
4930
- # must be in the format: field_name comparison_string literal_string.
4931
- # The field_name is the name of the field you want to compare. Only atomic field
4932
- # types are supported (string, number, boolean). The comparison_string must be
4933
- # either eq (equals) or ne (not equals). The literal_string is the string value
4934
- # to filter to. The literal value must be valid for the type of field you are
4935
- # filtering by (string, number, boolean). For string fields, the literal value
4936
- # is interpreted as a regular expression using RE2 syntax. The literal value
4937
- # must match the entire field.
4938
- # For example, to filter for instances that do not have a name of example-
4939
- # instance, you would use name ne example-instance.
4940
- # You can filter on nested fields. For example, you could filter on instances
4941
- # that have set the scheduling.automaticRestart field to true. Use filtering on
4942
- # nested fields to take advantage of labels to organize and search for results
4943
- # based on label values.
4872
+ # A filter expression that filters resources listed in the response. The
4873
+ # expression must specify the field name, a comparison operator, and the value
4874
+ # that you want to use for filtering. The value must be a string, a number, or a
4875
+ # boolean. The comparison operator must be either =, !=, >, or <.
4876
+ # For example, if you are filtering Compute Engine instances, you can exclude
4877
+ # instances named example-instance by specifying name != example-instance.
4878
+ # You can also filter nested fields. For example, you could specify scheduling.
4879
+ # automaticRestart = false to include instances only if they are not scheduled
4880
+ # for automatic restarts. You can use filtering on nested fields to filter based
4881
+ # on resource labels.
4944
4882
  # To filter on multiple expressions, provide each separate expression within
4945
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
4946
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
4947
- # resources must match all expressions to pass the filters.
4883
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
4884
+ # Intel Skylake"). By default, each expression is an AND expression. However,
4885
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
4886
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
4887
+ # automaticRestart = true).
4948
4888
  # @param [Fixnum] max_results
4949
4889
  # The maximum number of results per page that should be returned. If the number
4950
4890
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5142,25 +5082,22 @@ module Google
5142
5082
  # @param [String] project
5143
5083
  # Project ID for this request.
5144
5084
  # @param [String] filter
5145
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5146
- # must be in the format: field_name comparison_string literal_string.
5147
- # The field_name is the name of the field you want to compare. Only atomic field
5148
- # types are supported (string, number, boolean). The comparison_string must be
5149
- # either eq (equals) or ne (not equals). The literal_string is the string value
5150
- # to filter to. The literal value must be valid for the type of field you are
5151
- # filtering by (string, number, boolean). For string fields, the literal value
5152
- # is interpreted as a regular expression using RE2 syntax. The literal value
5153
- # must match the entire field.
5154
- # For example, to filter for instances that do not have a name of example-
5155
- # instance, you would use name ne example-instance.
5156
- # You can filter on nested fields. For example, you could filter on instances
5157
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5158
- # nested fields to take advantage of labels to organize and search for results
5159
- # based on label values.
5085
+ # A filter expression that filters resources listed in the response. The
5086
+ # expression must specify the field name, a comparison operator, and the value
5087
+ # that you want to use for filtering. The value must be a string, a number, or a
5088
+ # boolean. The comparison operator must be either =, !=, >, or <.
5089
+ # For example, if you are filtering Compute Engine instances, you can exclude
5090
+ # instances named example-instance by specifying name != example-instance.
5091
+ # You can also filter nested fields. For example, you could specify scheduling.
5092
+ # automaticRestart = false to include instances only if they are not scheduled
5093
+ # for automatic restarts. You can use filtering on nested fields to filter based
5094
+ # on resource labels.
5160
5095
  # To filter on multiple expressions, provide each separate expression within
5161
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5162
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5163
- # resources must match all expressions to pass the filters.
5096
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5097
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5098
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5099
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5100
+ # automaticRestart = true).
5164
5101
  # @param [Fixnum] max_results
5165
5102
  # The maximum number of results per page that should be returned. If the number
5166
5103
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5368,25 +5305,22 @@ module Google
5368
5305
  # @param [String] project
5369
5306
  # Project ID for this request.
5370
5307
  # @param [String] filter
5371
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5372
- # must be in the format: field_name comparison_string literal_string.
5373
- # The field_name is the name of the field you want to compare. Only atomic field
5374
- # types are supported (string, number, boolean). The comparison_string must be
5375
- # either eq (equals) or ne (not equals). The literal_string is the string value
5376
- # to filter to. The literal value must be valid for the type of field you are
5377
- # filtering by (string, number, boolean). For string fields, the literal value
5378
- # is interpreted as a regular expression using RE2 syntax. The literal value
5379
- # must match the entire field.
5380
- # For example, to filter for instances that do not have a name of example-
5381
- # instance, you would use name ne example-instance.
5382
- # You can filter on nested fields. For example, you could filter on instances
5383
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5384
- # nested fields to take advantage of labels to organize and search for results
5385
- # based on label values.
5308
+ # A filter expression that filters resources listed in the response. The
5309
+ # expression must specify the field name, a comparison operator, and the value
5310
+ # that you want to use for filtering. The value must be a string, a number, or a
5311
+ # boolean. The comparison operator must be either =, !=, >, or <.
5312
+ # For example, if you are filtering Compute Engine instances, you can exclude
5313
+ # instances named example-instance by specifying name != example-instance.
5314
+ # You can also filter nested fields. For example, you could specify scheduling.
5315
+ # automaticRestart = false to include instances only if they are not scheduled
5316
+ # for automatic restarts. You can use filtering on nested fields to filter based
5317
+ # on resource labels.
5386
5318
  # To filter on multiple expressions, provide each separate expression within
5387
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5388
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5389
- # resources must match all expressions to pass the filters.
5319
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5320
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5321
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5322
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5323
+ # automaticRestart = true).
5390
5324
  # @param [Fixnum] max_results
5391
5325
  # The maximum number of results per page that should be returned. If the number
5392
5326
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5488,25 +5422,22 @@ module Google
5488
5422
  # @param [String] zone
5489
5423
  # The name of the zone for this request.
5490
5424
  # @param [String] filter
5491
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5492
- # must be in the format: field_name comparison_string literal_string.
5493
- # The field_name is the name of the field you want to compare. Only atomic field
5494
- # types are supported (string, number, boolean). The comparison_string must be
5495
- # either eq (equals) or ne (not equals). The literal_string is the string value
5496
- # to filter to. The literal value must be valid for the type of field you are
5497
- # filtering by (string, number, boolean). For string fields, the literal value
5498
- # is interpreted as a regular expression using RE2 syntax. The literal value
5499
- # must match the entire field.
5500
- # For example, to filter for instances that do not have a name of example-
5501
- # instance, you would use name ne example-instance.
5502
- # You can filter on nested fields. For example, you could filter on instances
5503
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5504
- # nested fields to take advantage of labels to organize and search for results
5505
- # based on label values.
5425
+ # A filter expression that filters resources listed in the response. The
5426
+ # expression must specify the field name, a comparison operator, and the value
5427
+ # that you want to use for filtering. The value must be a string, a number, or a
5428
+ # boolean. The comparison operator must be either =, !=, >, or <.
5429
+ # For example, if you are filtering Compute Engine instances, you can exclude
5430
+ # instances named example-instance by specifying name != example-instance.
5431
+ # You can also filter nested fields. For example, you could specify scheduling.
5432
+ # automaticRestart = false to include instances only if they are not scheduled
5433
+ # for automatic restarts. You can use filtering on nested fields to filter based
5434
+ # on resource labels.
5506
5435
  # To filter on multiple expressions, provide each separate expression within
5507
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5508
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5509
- # resources must match all expressions to pass the filters.
5436
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5437
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5438
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5439
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5440
+ # automaticRestart = true).
5510
5441
  # @param [Fixnum] max_results
5511
5442
  # The maximum number of results per page that should be returned. If the number
5512
5443
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5565,25 +5496,22 @@ module Google
5565
5496
  # @param [String] project
5566
5497
  # Project ID for this request.
5567
5498
  # @param [String] filter
5568
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5569
- # must be in the format: field_name comparison_string literal_string.
5570
- # The field_name is the name of the field you want to compare. Only atomic field
5571
- # types are supported (string, number, boolean). The comparison_string must be
5572
- # either eq (equals) or ne (not equals). The literal_string is the string value
5573
- # to filter to. The literal value must be valid for the type of field you are
5574
- # filtering by (string, number, boolean). For string fields, the literal value
5575
- # is interpreted as a regular expression using RE2 syntax. The literal value
5576
- # must match the entire field.
5577
- # For example, to filter for instances that do not have a name of example-
5578
- # instance, you would use name ne example-instance.
5579
- # You can filter on nested fields. For example, you could filter on instances
5580
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5581
- # nested fields to take advantage of labels to organize and search for results
5582
- # based on label values.
5499
+ # A filter expression that filters resources listed in the response. The
5500
+ # expression must specify the field name, a comparison operator, and the value
5501
+ # that you want to use for filtering. The value must be a string, a number, or a
5502
+ # boolean. The comparison operator must be either =, !=, >, or <.
5503
+ # For example, if you are filtering Compute Engine instances, you can exclude
5504
+ # instances named example-instance by specifying name != example-instance.
5505
+ # You can also filter nested fields. For example, you could specify scheduling.
5506
+ # automaticRestart = false to include instances only if they are not scheduled
5507
+ # for automatic restarts. You can use filtering on nested fields to filter based
5508
+ # on resource labels.
5583
5509
  # To filter on multiple expressions, provide each separate expression within
5584
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5585
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5586
- # resources must match all expressions to pass the filters.
5510
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5511
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5512
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5513
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5514
+ # automaticRestart = true).
5587
5515
  # @param [Fixnum] max_results
5588
5516
  # The maximum number of results per page that should be returned. If the number
5589
5517
  # of available results is larger than maxResults, Compute Engine returns a
@@ -5834,25 +5762,22 @@ module Google
5834
5762
  # @param [String] zone
5835
5763
  # The name of the zone for this request.
5836
5764
  # @param [String] filter
5837
- # Sets a filter `expression` for filtering listed resources. Your `expression`
5838
- # must be in the format: field_name comparison_string literal_string.
5839
- # The field_name is the name of the field you want to compare. Only atomic field
5840
- # types are supported (string, number, boolean). The comparison_string must be
5841
- # either eq (equals) or ne (not equals). The literal_string is the string value
5842
- # to filter to. The literal value must be valid for the type of field you are
5843
- # filtering by (string, number, boolean). For string fields, the literal value
5844
- # is interpreted as a regular expression using RE2 syntax. The literal value
5845
- # must match the entire field.
5846
- # For example, to filter for instances that do not have a name of example-
5847
- # instance, you would use name ne example-instance.
5848
- # You can filter on nested fields. For example, you could filter on instances
5849
- # that have set the scheduling.automaticRestart field to true. Use filtering on
5850
- # nested fields to take advantage of labels to organize and search for results
5851
- # based on label values.
5765
+ # A filter expression that filters resources listed in the response. The
5766
+ # expression must specify the field name, a comparison operator, and the value
5767
+ # that you want to use for filtering. The value must be a string, a number, or a
5768
+ # boolean. The comparison operator must be either =, !=, >, or <.
5769
+ # For example, if you are filtering Compute Engine instances, you can exclude
5770
+ # instances named example-instance by specifying name != example-instance.
5771
+ # You can also filter nested fields. For example, you could specify scheduling.
5772
+ # automaticRestart = false to include instances only if they are not scheduled
5773
+ # for automatic restarts. You can use filtering on nested fields to filter based
5774
+ # on resource labels.
5852
5775
  # To filter on multiple expressions, provide each separate expression within
5853
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
5854
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
5855
- # resources must match all expressions to pass the filters.
5776
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
5777
+ # Intel Skylake"). By default, each expression is an AND expression. However,
5778
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
5779
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
5780
+ # automaticRestart = true).
5856
5781
  # @param [Fixnum] max_results
5857
5782
  # The maximum number of results per page that should be returned. If the number
5858
5783
  # of available results is larger than maxResults, Compute Engine returns a
@@ -6141,25 +6066,22 @@ module Google
6141
6066
  # @param [String] project
6142
6067
  # Project ID for this request.
6143
6068
  # @param [String] filter
6144
- # Sets a filter `expression` for filtering listed resources. Your `expression`
6145
- # must be in the format: field_name comparison_string literal_string.
6146
- # The field_name is the name of the field you want to compare. Only atomic field
6147
- # types are supported (string, number, boolean). The comparison_string must be
6148
- # either eq (equals) or ne (not equals). The literal_string is the string value
6149
- # to filter to. The literal value must be valid for the type of field you are
6150
- # filtering by (string, number, boolean). For string fields, the literal value
6151
- # is interpreted as a regular expression using RE2 syntax. The literal value
6152
- # must match the entire field.
6153
- # For example, to filter for instances that do not have a name of example-
6154
- # instance, you would use name ne example-instance.
6155
- # You can filter on nested fields. For example, you could filter on instances
6156
- # that have set the scheduling.automaticRestart field to true. Use filtering on
6157
- # nested fields to take advantage of labels to organize and search for results
6158
- # based on label values.
6069
+ # A filter expression that filters resources listed in the response. The
6070
+ # expression must specify the field name, a comparison operator, and the value
6071
+ # that you want to use for filtering. The value must be a string, a number, or a
6072
+ # boolean. The comparison operator must be either =, !=, >, or <.
6073
+ # For example, if you are filtering Compute Engine instances, you can exclude
6074
+ # instances named example-instance by specifying name != example-instance.
6075
+ # You can also filter nested fields. For example, you could specify scheduling.
6076
+ # automaticRestart = false to include instances only if they are not scheduled
6077
+ # for automatic restarts. You can use filtering on nested fields to filter based
6078
+ # on resource labels.
6159
6079
  # To filter on multiple expressions, provide each separate expression within
6160
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
6161
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
6162
- # resources must match all expressions to pass the filters.
6080
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
6081
+ # Intel Skylake"). By default, each expression is an AND expression. However,
6082
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
6083
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
6084
+ # automaticRestart = true).
6163
6085
  # @param [Fixnum] max_results
6164
6086
  # The maximum number of results per page that should be returned. If the number
6165
6087
  # of available results is larger than maxResults, Compute Engine returns a
@@ -6508,25 +6430,22 @@ module Google
6508
6430
  # @param [String] project
6509
6431
  # Project ID for this request.
6510
6432
  # @param [String] filter
6511
- # Sets a filter `expression` for filtering listed resources. Your `expression`
6512
- # must be in the format: field_name comparison_string literal_string.
6513
- # The field_name is the name of the field you want to compare. Only atomic field
6514
- # types are supported (string, number, boolean). The comparison_string must be
6515
- # either eq (equals) or ne (not equals). The literal_string is the string value
6516
- # to filter to. The literal value must be valid for the type of field you are
6517
- # filtering by (string, number, boolean). For string fields, the literal value
6518
- # is interpreted as a regular expression using RE2 syntax. The literal value
6519
- # must match the entire field.
6520
- # For example, to filter for instances that do not have a name of example-
6521
- # instance, you would use name ne example-instance.
6522
- # You can filter on nested fields. For example, you could filter on instances
6523
- # that have set the scheduling.automaticRestart field to true. Use filtering on
6524
- # nested fields to take advantage of labels to organize and search for results
6525
- # based on label values.
6433
+ # A filter expression that filters resources listed in the response. The
6434
+ # expression must specify the field name, a comparison operator, and the value
6435
+ # that you want to use for filtering. The value must be a string, a number, or a
6436
+ # boolean. The comparison operator must be either =, !=, >, or <.
6437
+ # For example, if you are filtering Compute Engine instances, you can exclude
6438
+ # instances named example-instance by specifying name != example-instance.
6439
+ # You can also filter nested fields. For example, you could specify scheduling.
6440
+ # automaticRestart = false to include instances only if they are not scheduled
6441
+ # for automatic restarts. You can use filtering on nested fields to filter based
6442
+ # on resource labels.
6526
6443
  # To filter on multiple expressions, provide each separate expression within
6527
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
6528
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
6529
- # resources must match all expressions to pass the filters.
6444
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
6445
+ # Intel Skylake"). By default, each expression is an AND expression. However,
6446
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
6447
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
6448
+ # automaticRestart = true).
6530
6449
  # @param [Fixnum] max_results
6531
6450
  # The maximum number of results per page that should be returned. If the number
6532
6451
  # of available results is larger than maxResults, Compute Engine returns a
@@ -7013,25 +6932,22 @@ module Google
7013
6932
  # @param [String] project
7014
6933
  # Project ID for this request.
7015
6934
  # @param [String] filter
7016
- # Sets a filter `expression` for filtering listed resources. Your `expression`
7017
- # must be in the format: field_name comparison_string literal_string.
7018
- # The field_name is the name of the field you want to compare. Only atomic field
7019
- # types are supported (string, number, boolean). The comparison_string must be
7020
- # either eq (equals) or ne (not equals). The literal_string is the string value
7021
- # to filter to. The literal value must be valid for the type of field you are
7022
- # filtering by (string, number, boolean). For string fields, the literal value
7023
- # is interpreted as a regular expression using RE2 syntax. The literal value
7024
- # must match the entire field.
7025
- # For example, to filter for instances that do not have a name of example-
7026
- # instance, you would use name ne example-instance.
7027
- # You can filter on nested fields. For example, you could filter on instances
7028
- # that have set the scheduling.automaticRestart field to true. Use filtering on
7029
- # nested fields to take advantage of labels to organize and search for results
7030
- # based on label values.
6935
+ # A filter expression that filters resources listed in the response. The
6936
+ # expression must specify the field name, a comparison operator, and the value
6937
+ # that you want to use for filtering. The value must be a string, a number, or a
6938
+ # boolean. The comparison operator must be either =, !=, >, or <.
6939
+ # For example, if you are filtering Compute Engine instances, you can exclude
6940
+ # instances named example-instance by specifying name != example-instance.
6941
+ # You can also filter nested fields. For example, you could specify scheduling.
6942
+ # automaticRestart = false to include instances only if they are not scheduled
6943
+ # for automatic restarts. You can use filtering on nested fields to filter based
6944
+ # on resource labels.
7031
6945
  # To filter on multiple expressions, provide each separate expression within
7032
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
7033
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
7034
- # resources must match all expressions to pass the filters.
6946
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
6947
+ # Intel Skylake"). By default, each expression is an AND expression. However,
6948
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
6949
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
6950
+ # automaticRestart = true).
7035
6951
  # @param [Fixnum] max_results
7036
6952
  # The maximum number of results per page that should be returned. If the number
7037
6953
  # of available results is larger than maxResults, Compute Engine returns a
@@ -7281,25 +7197,22 @@ module Google
7281
7197
  # @param [String] project
7282
7198
  # Project ID for this request.
7283
7199
  # @param [String] filter
7284
- # Sets a filter `expression` for filtering listed resources. Your `expression`
7285
- # must be in the format: field_name comparison_string literal_string.
7286
- # The field_name is the name of the field you want to compare. Only atomic field
7287
- # types are supported (string, number, boolean). The comparison_string must be
7288
- # either eq (equals) or ne (not equals). The literal_string is the string value
7289
- # to filter to. The literal value must be valid for the type of field you are
7290
- # filtering by (string, number, boolean). For string fields, the literal value
7291
- # is interpreted as a regular expression using RE2 syntax. The literal value
7292
- # must match the entire field.
7293
- # For example, to filter for instances that do not have a name of example-
7294
- # instance, you would use name ne example-instance.
7295
- # You can filter on nested fields. For example, you could filter on instances
7296
- # that have set the scheduling.automaticRestart field to true. Use filtering on
7297
- # nested fields to take advantage of labels to organize and search for results
7298
- # based on label values.
7200
+ # A filter expression that filters resources listed in the response. The
7201
+ # expression must specify the field name, a comparison operator, and the value
7202
+ # that you want to use for filtering. The value must be a string, a number, or a
7203
+ # boolean. The comparison operator must be either =, !=, >, or <.
7204
+ # For example, if you are filtering Compute Engine instances, you can exclude
7205
+ # instances named example-instance by specifying name != example-instance.
7206
+ # You can also filter nested fields. For example, you could specify scheduling.
7207
+ # automaticRestart = false to include instances only if they are not scheduled
7208
+ # for automatic restarts. You can use filtering on nested fields to filter based
7209
+ # on resource labels.
7299
7210
  # To filter on multiple expressions, provide each separate expression within
7300
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
7301
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
7302
- # resources must match all expressions to pass the filters.
7211
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
7212
+ # Intel Skylake"). By default, each expression is an AND expression. However,
7213
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
7214
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
7215
+ # automaticRestart = true).
7303
7216
  # @param [Fixnum] max_results
7304
7217
  # The maximum number of results per page that should be returned. If the number
7305
7218
  # of available results is larger than maxResults, Compute Engine returns a
@@ -7674,25 +7587,22 @@ module Google
7674
7587
  # @param [String] zone
7675
7588
  # The name of the zone where the managed instance group is located.
7676
7589
  # @param [String] filter
7677
- # Sets a filter `expression` for filtering listed resources. Your `expression`
7678
- # must be in the format: field_name comparison_string literal_string.
7679
- # The field_name is the name of the field you want to compare. Only atomic field
7680
- # types are supported (string, number, boolean). The comparison_string must be
7681
- # either eq (equals) or ne (not equals). The literal_string is the string value
7682
- # to filter to. The literal value must be valid for the type of field you are
7683
- # filtering by (string, number, boolean). For string fields, the literal value
7684
- # is interpreted as a regular expression using RE2 syntax. The literal value
7685
- # must match the entire field.
7686
- # For example, to filter for instances that do not have a name of example-
7687
- # instance, you would use name ne example-instance.
7688
- # You can filter on nested fields. For example, you could filter on instances
7689
- # that have set the scheduling.automaticRestart field to true. Use filtering on
7690
- # nested fields to take advantage of labels to organize and search for results
7691
- # based on label values.
7590
+ # A filter expression that filters resources listed in the response. The
7591
+ # expression must specify the field name, a comparison operator, and the value
7592
+ # that you want to use for filtering. The value must be a string, a number, or a
7593
+ # boolean. The comparison operator must be either =, !=, >, or <.
7594
+ # For example, if you are filtering Compute Engine instances, you can exclude
7595
+ # instances named example-instance by specifying name != example-instance.
7596
+ # You can also filter nested fields. For example, you could specify scheduling.
7597
+ # automaticRestart = false to include instances only if they are not scheduled
7598
+ # for automatic restarts. You can use filtering on nested fields to filter based
7599
+ # on resource labels.
7692
7600
  # To filter on multiple expressions, provide each separate expression within
7693
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
7694
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
7695
- # resources must match all expressions to pass the filters.
7601
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
7602
+ # Intel Skylake"). By default, each expression is an AND expression. However,
7603
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
7604
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
7605
+ # automaticRestart = true).
7696
7606
  # @param [Fixnum] max_results
7697
7607
  # The maximum number of results per page that should be returned. If the number
7698
7608
  # of available results is larger than maxResults, Compute Engine returns a
@@ -7809,25 +7719,22 @@ module Google
7809
7719
  # @param [String] instance_group_manager
7810
7720
  # The name of the managed instance group. It should conform to RFC1035.
7811
7721
  # @param [String] filter
7812
- # Sets a filter `expression` for filtering listed resources. Your `expression`
7813
- # must be in the format: field_name comparison_string literal_string.
7814
- # The field_name is the name of the field you want to compare. Only atomic field
7815
- # types are supported (string, number, boolean). The comparison_string must be
7816
- # either eq (equals) or ne (not equals). The literal_string is the string value
7817
- # to filter to. The literal value must be valid for the type of field you are
7818
- # filtering by (string, number, boolean). For string fields, the literal value
7819
- # is interpreted as a regular expression using RE2 syntax. The literal value
7820
- # must match the entire field.
7821
- # For example, to filter for instances that do not have a name of example-
7822
- # instance, you would use name ne example-instance.
7823
- # You can filter on nested fields. For example, you could filter on instances
7824
- # that have set the scheduling.automaticRestart field to true. Use filtering on
7825
- # nested fields to take advantage of labels to organize and search for results
7826
- # based on label values.
7722
+ # A filter expression that filters resources listed in the response. The
7723
+ # expression must specify the field name, a comparison operator, and the value
7724
+ # that you want to use for filtering. The value must be a string, a number, or a
7725
+ # boolean. The comparison operator must be either =, !=, >, or <.
7726
+ # For example, if you are filtering Compute Engine instances, you can exclude
7727
+ # instances named example-instance by specifying name != example-instance.
7728
+ # You can also filter nested fields. For example, you could specify scheduling.
7729
+ # automaticRestart = false to include instances only if they are not scheduled
7730
+ # for automatic restarts. You can use filtering on nested fields to filter based
7731
+ # on resource labels.
7827
7732
  # To filter on multiple expressions, provide each separate expression within
7828
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
7829
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
7830
- # resources must match all expressions to pass the filters.
7733
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
7734
+ # Intel Skylake"). By default, each expression is an AND expression. However,
7735
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
7736
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
7737
+ # automaticRestart = true).
7831
7738
  # @param [Fixnum] max_results
7832
7739
  # The maximum number of results per page that should be returned. If the number
7833
7740
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8542,25 +8449,22 @@ module Google
8542
8449
  # @param [String] project
8543
8450
  # Project ID for this request.
8544
8451
  # @param [String] filter
8545
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8546
- # must be in the format: field_name comparison_string literal_string.
8547
- # The field_name is the name of the field you want to compare. Only atomic field
8548
- # types are supported (string, number, boolean). The comparison_string must be
8549
- # either eq (equals) or ne (not equals). The literal_string is the string value
8550
- # to filter to. The literal value must be valid for the type of field you are
8551
- # filtering by (string, number, boolean). For string fields, the literal value
8552
- # is interpreted as a regular expression using RE2 syntax. The literal value
8553
- # must match the entire field.
8554
- # For example, to filter for instances that do not have a name of example-
8555
- # instance, you would use name ne example-instance.
8556
- # You can filter on nested fields. For example, you could filter on instances
8557
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8558
- # nested fields to take advantage of labels to organize and search for results
8559
- # based on label values.
8452
+ # A filter expression that filters resources listed in the response. The
8453
+ # expression must specify the field name, a comparison operator, and the value
8454
+ # that you want to use for filtering. The value must be a string, a number, or a
8455
+ # boolean. The comparison operator must be either =, !=, >, or <.
8456
+ # For example, if you are filtering Compute Engine instances, you can exclude
8457
+ # instances named example-instance by specifying name != example-instance.
8458
+ # You can also filter nested fields. For example, you could specify scheduling.
8459
+ # automaticRestart = false to include instances only if they are not scheduled
8460
+ # for automatic restarts. You can use filtering on nested fields to filter based
8461
+ # on resource labels.
8560
8462
  # To filter on multiple expressions, provide each separate expression within
8561
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8562
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8563
- # resources must match all expressions to pass the filters.
8463
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8464
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8465
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8466
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8467
+ # automaticRestart = true).
8564
8468
  # @param [Fixnum] max_results
8565
8469
  # The maximum number of results per page that should be returned. If the number
8566
8470
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8772,25 +8676,22 @@ module Google
8772
8676
  # @param [String] zone
8773
8677
  # The name of the zone where the instance group is located.
8774
8678
  # @param [String] filter
8775
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8776
- # must be in the format: field_name comparison_string literal_string.
8777
- # The field_name is the name of the field you want to compare. Only atomic field
8778
- # types are supported (string, number, boolean). The comparison_string must be
8779
- # either eq (equals) or ne (not equals). The literal_string is the string value
8780
- # to filter to. The literal value must be valid for the type of field you are
8781
- # filtering by (string, number, boolean). For string fields, the literal value
8782
- # is interpreted as a regular expression using RE2 syntax. The literal value
8783
- # must match the entire field.
8784
- # For example, to filter for instances that do not have a name of example-
8785
- # instance, you would use name ne example-instance.
8786
- # You can filter on nested fields. For example, you could filter on instances
8787
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8788
- # nested fields to take advantage of labels to organize and search for results
8789
- # based on label values.
8679
+ # A filter expression that filters resources listed in the response. The
8680
+ # expression must specify the field name, a comparison operator, and the value
8681
+ # that you want to use for filtering. The value must be a string, a number, or a
8682
+ # boolean. The comparison operator must be either =, !=, >, or <.
8683
+ # For example, if you are filtering Compute Engine instances, you can exclude
8684
+ # instances named example-instance by specifying name != example-instance.
8685
+ # You can also filter nested fields. For example, you could specify scheduling.
8686
+ # automaticRestart = false to include instances only if they are not scheduled
8687
+ # for automatic restarts. You can use filtering on nested fields to filter based
8688
+ # on resource labels.
8790
8689
  # To filter on multiple expressions, provide each separate expression within
8791
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8792
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8793
- # resources must match all expressions to pass the filters.
8690
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8691
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8692
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8693
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8694
+ # automaticRestart = true).
8794
8695
  # @param [Fixnum] max_results
8795
8696
  # The maximum number of results per page that should be returned. If the number
8796
8697
  # of available results is larger than maxResults, Compute Engine returns a
@@ -8855,25 +8756,22 @@ module Google
8855
8756
  # included instances.
8856
8757
  # @param [Google::Apis::ComputeAlpha::InstanceGroupsListInstancesRequest] instance_groups_list_instances_request_object
8857
8758
  # @param [String] filter
8858
- # Sets a filter `expression` for filtering listed resources. Your `expression`
8859
- # must be in the format: field_name comparison_string literal_string.
8860
- # The field_name is the name of the field you want to compare. Only atomic field
8861
- # types are supported (string, number, boolean). The comparison_string must be
8862
- # either eq (equals) or ne (not equals). The literal_string is the string value
8863
- # to filter to. The literal value must be valid for the type of field you are
8864
- # filtering by (string, number, boolean). For string fields, the literal value
8865
- # is interpreted as a regular expression using RE2 syntax. The literal value
8866
- # must match the entire field.
8867
- # For example, to filter for instances that do not have a name of example-
8868
- # instance, you would use name ne example-instance.
8869
- # You can filter on nested fields. For example, you could filter on instances
8870
- # that have set the scheduling.automaticRestart field to true. Use filtering on
8871
- # nested fields to take advantage of labels to organize and search for results
8872
- # based on label values.
8759
+ # A filter expression that filters resources listed in the response. The
8760
+ # expression must specify the field name, a comparison operator, and the value
8761
+ # that you want to use for filtering. The value must be a string, a number, or a
8762
+ # boolean. The comparison operator must be either =, !=, >, or <.
8763
+ # For example, if you are filtering Compute Engine instances, you can exclude
8764
+ # instances named example-instance by specifying name != example-instance.
8765
+ # You can also filter nested fields. For example, you could specify scheduling.
8766
+ # automaticRestart = false to include instances only if they are not scheduled
8767
+ # for automatic restarts. You can use filtering on nested fields to filter based
8768
+ # on resource labels.
8873
8769
  # To filter on multiple expressions, provide each separate expression within
8874
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
8875
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
8876
- # resources must match all expressions to pass the filters.
8770
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
8771
+ # Intel Skylake"). By default, each expression is an AND expression. However,
8772
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
8773
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
8774
+ # automaticRestart = true).
8877
8775
  # @param [Fixnum] max_results
8878
8776
  # The maximum number of results per page that should be returned. If the number
8879
8777
  # of available results is larger than maxResults, Compute Engine returns a
@@ -9240,25 +9138,22 @@ module Google
9240
9138
  # @param [String] project
9241
9139
  # Project ID for this request.
9242
9140
  # @param [String] filter
9243
- # Sets a filter `expression` for filtering listed resources. Your `expression`
9244
- # must be in the format: field_name comparison_string literal_string.
9245
- # The field_name is the name of the field you want to compare. Only atomic field
9246
- # types are supported (string, number, boolean). The comparison_string must be
9247
- # either eq (equals) or ne (not equals). The literal_string is the string value
9248
- # to filter to. The literal value must be valid for the type of field you are
9249
- # filtering by (string, number, boolean). For string fields, the literal value
9250
- # is interpreted as a regular expression using RE2 syntax. The literal value
9251
- # must match the entire field.
9252
- # For example, to filter for instances that do not have a name of example-
9253
- # instance, you would use name ne example-instance.
9254
- # You can filter on nested fields. For example, you could filter on instances
9255
- # that have set the scheduling.automaticRestart field to true. Use filtering on
9256
- # nested fields to take advantage of labels to organize and search for results
9257
- # based on label values.
9141
+ # A filter expression that filters resources listed in the response. The
9142
+ # expression must specify the field name, a comparison operator, and the value
9143
+ # that you want to use for filtering. The value must be a string, a number, or a
9144
+ # boolean. The comparison operator must be either =, !=, >, or <.
9145
+ # For example, if you are filtering Compute Engine instances, you can exclude
9146
+ # instances named example-instance by specifying name != example-instance.
9147
+ # You can also filter nested fields. For example, you could specify scheduling.
9148
+ # automaticRestart = false to include instances only if they are not scheduled
9149
+ # for automatic restarts. You can use filtering on nested fields to filter based
9150
+ # on resource labels.
9258
9151
  # To filter on multiple expressions, provide each separate expression within
9259
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
9260
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
9261
- # resources must match all expressions to pass the filters.
9152
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
9153
+ # Intel Skylake"). By default, each expression is an AND expression. However,
9154
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
9155
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
9156
+ # automaticRestart = true).
9262
9157
  # @param [Fixnum] max_results
9263
9158
  # The maximum number of results per page that should be returned. If the number
9264
9159
  # of available results is larger than maxResults, Compute Engine returns a
@@ -9474,25 +9369,22 @@ module Google
9474
9369
  # @param [String] project
9475
9370
  # Project ID for this request.
9476
9371
  # @param [String] filter
9477
- # Sets a filter `expression` for filtering listed resources. Your `expression`
9478
- # must be in the format: field_name comparison_string literal_string.
9479
- # The field_name is the name of the field you want to compare. Only atomic field
9480
- # types are supported (string, number, boolean). The comparison_string must be
9481
- # either eq (equals) or ne (not equals). The literal_string is the string value
9482
- # to filter to. The literal value must be valid for the type of field you are
9483
- # filtering by (string, number, boolean). For string fields, the literal value
9484
- # is interpreted as a regular expression using RE2 syntax. The literal value
9485
- # must match the entire field.
9486
- # For example, to filter for instances that do not have a name of example-
9487
- # instance, you would use name ne example-instance.
9488
- # You can filter on nested fields. For example, you could filter on instances
9489
- # that have set the scheduling.automaticRestart field to true. Use filtering on
9490
- # nested fields to take advantage of labels to organize and search for results
9491
- # based on label values.
9372
+ # A filter expression that filters resources listed in the response. The
9373
+ # expression must specify the field name, a comparison operator, and the value
9374
+ # that you want to use for filtering. The value must be a string, a number, or a
9375
+ # boolean. The comparison operator must be either =, !=, >, or <.
9376
+ # For example, if you are filtering Compute Engine instances, you can exclude
9377
+ # instances named example-instance by specifying name != example-instance.
9378
+ # You can also filter nested fields. For example, you could specify scheduling.
9379
+ # automaticRestart = false to include instances only if they are not scheduled
9380
+ # for automatic restarts. You can use filtering on nested fields to filter based
9381
+ # on resource labels.
9492
9382
  # To filter on multiple expressions, provide each separate expression within
9493
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
9494
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
9495
- # resources must match all expressions to pass the filters.
9383
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
9384
+ # Intel Skylake"). By default, each expression is an AND expression. However,
9385
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
9386
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
9387
+ # automaticRestart = true).
9496
9388
  # @param [Fixnum] max_results
9497
9389
  # The maximum number of results per page that should be returned. If the number
9498
9390
  # of available results is larger than maxResults, Compute Engine returns a
@@ -10025,25 +9917,22 @@ module Google
10025
9917
  # @param [String] zone
10026
9918
  # The name of the zone for this request.
10027
9919
  # @param [String] filter
10028
- # Sets a filter `expression` for filtering listed resources. Your `expression`
10029
- # must be in the format: field_name comparison_string literal_string.
10030
- # The field_name is the name of the field you want to compare. Only atomic field
10031
- # types are supported (string, number, boolean). The comparison_string must be
10032
- # either eq (equals) or ne (not equals). The literal_string is the string value
10033
- # to filter to. The literal value must be valid for the type of field you are
10034
- # filtering by (string, number, boolean). For string fields, the literal value
10035
- # is interpreted as a regular expression using RE2 syntax. The literal value
10036
- # must match the entire field.
10037
- # For example, to filter for instances that do not have a name of example-
10038
- # instance, you would use name ne example-instance.
10039
- # You can filter on nested fields. For example, you could filter on instances
10040
- # that have set the scheduling.automaticRestart field to true. Use filtering on
10041
- # nested fields to take advantage of labels to organize and search for results
10042
- # based on label values.
9920
+ # A filter expression that filters resources listed in the response. The
9921
+ # expression must specify the field name, a comparison operator, and the value
9922
+ # that you want to use for filtering. The value must be a string, a number, or a
9923
+ # boolean. The comparison operator must be either =, !=, >, or <.
9924
+ # For example, if you are filtering Compute Engine instances, you can exclude
9925
+ # instances named example-instance by specifying name != example-instance.
9926
+ # You can also filter nested fields. For example, you could specify scheduling.
9927
+ # automaticRestart = false to include instances only if they are not scheduled
9928
+ # for automatic restarts. You can use filtering on nested fields to filter based
9929
+ # on resource labels.
10043
9930
  # To filter on multiple expressions, provide each separate expression within
10044
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
10045
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
10046
- # resources must match all expressions to pass the filters.
9931
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
9932
+ # Intel Skylake"). By default, each expression is an AND expression. However,
9933
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
9934
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
9935
+ # automaticRestart = true).
10047
9936
  # @param [Fixnum] max_results
10048
9937
  # The maximum number of results per page that should be returned. If the number
10049
9938
  # of available results is larger than maxResults, Compute Engine returns a
@@ -10108,25 +9997,22 @@ module Google
10108
9997
  # Name of the target instance scoping this request, or '-' if the request should
10109
9998
  # span over all instances in the container.
10110
9999
  # @param [String] filter
10111
- # Sets a filter `expression` for filtering listed resources. Your `expression`
10112
- # must be in the format: field_name comparison_string literal_string.
10113
- # The field_name is the name of the field you want to compare. Only atomic field
10114
- # types are supported (string, number, boolean). The comparison_string must be
10115
- # either eq (equals) or ne (not equals). The literal_string is the string value
10116
- # to filter to. The literal value must be valid for the type of field you are
10117
- # filtering by (string, number, boolean). For string fields, the literal value
10118
- # is interpreted as a regular expression using RE2 syntax. The literal value
10119
- # must match the entire field.
10120
- # For example, to filter for instances that do not have a name of example-
10121
- # instance, you would use name ne example-instance.
10122
- # You can filter on nested fields. For example, you could filter on instances
10123
- # that have set the scheduling.automaticRestart field to true. Use filtering on
10124
- # nested fields to take advantage of labels to organize and search for results
10125
- # based on label values.
10000
+ # A filter expression that filters resources listed in the response. The
10001
+ # expression must specify the field name, a comparison operator, and the value
10002
+ # that you want to use for filtering. The value must be a string, a number, or a
10003
+ # boolean. The comparison operator must be either =, !=, >, or <.
10004
+ # For example, if you are filtering Compute Engine instances, you can exclude
10005
+ # instances named example-instance by specifying name != example-instance.
10006
+ # You can also filter nested fields. For example, you could specify scheduling.
10007
+ # automaticRestart = false to include instances only if they are not scheduled
10008
+ # for automatic restarts. You can use filtering on nested fields to filter based
10009
+ # on resource labels.
10126
10010
  # To filter on multiple expressions, provide each separate expression within
10127
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
10128
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
10129
- # resources must match all expressions to pass the filters.
10011
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
10012
+ # Intel Skylake"). By default, each expression is an AND expression. However,
10013
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
10014
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
10015
+ # automaticRestart = true).
10130
10016
  # @param [Fixnum] max_results
10131
10017
  # The maximum number of results per page that should be returned. If the number
10132
10018
  # of available results is larger than maxResults, Compute Engine returns a
@@ -11462,25 +11348,22 @@ module Google
11462
11348
  # @param [String] project
11463
11349
  # Project ID for this request.
11464
11350
  # @param [String] filter
11465
- # Sets a filter `expression` for filtering listed resources. Your `expression`
11466
- # must be in the format: field_name comparison_string literal_string.
11467
- # The field_name is the name of the field you want to compare. Only atomic field
11468
- # types are supported (string, number, boolean). The comparison_string must be
11469
- # either eq (equals) or ne (not equals). The literal_string is the string value
11470
- # to filter to. The literal value must be valid for the type of field you are
11471
- # filtering by (string, number, boolean). For string fields, the literal value
11472
- # is interpreted as a regular expression using RE2 syntax. The literal value
11473
- # must match the entire field.
11474
- # For example, to filter for instances that do not have a name of example-
11475
- # instance, you would use name ne example-instance.
11476
- # You can filter on nested fields. For example, you could filter on instances
11477
- # that have set the scheduling.automaticRestart field to true. Use filtering on
11478
- # nested fields to take advantage of labels to organize and search for results
11479
- # based on label values.
11351
+ # A filter expression that filters resources listed in the response. The
11352
+ # expression must specify the field name, a comparison operator, and the value
11353
+ # that you want to use for filtering. The value must be a string, a number, or a
11354
+ # boolean. The comparison operator must be either =, !=, >, or <.
11355
+ # For example, if you are filtering Compute Engine instances, you can exclude
11356
+ # instances named example-instance by specifying name != example-instance.
11357
+ # You can also filter nested fields. For example, you could specify scheduling.
11358
+ # automaticRestart = false to include instances only if they are not scheduled
11359
+ # for automatic restarts. You can use filtering on nested fields to filter based
11360
+ # on resource labels.
11480
11361
  # To filter on multiple expressions, provide each separate expression within
11481
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
11482
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
11483
- # resources must match all expressions to pass the filters.
11362
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
11363
+ # Intel Skylake"). By default, each expression is an AND expression. However,
11364
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
11365
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
11366
+ # automaticRestart = true).
11484
11367
  # @param [Fixnum] max_results
11485
11368
  # The maximum number of results per page that should be returned. If the number
11486
11369
  # of available results is larger than maxResults, Compute Engine returns a
@@ -11731,25 +11614,22 @@ module Google
11731
11614
  # @param [String] region
11732
11615
  # Name of the region for this request.
11733
11616
  # @param [String] filter
11734
- # Sets a filter `expression` for filtering listed resources. Your `expression`
11735
- # must be in the format: field_name comparison_string literal_string.
11736
- # The field_name is the name of the field you want to compare. Only atomic field
11737
- # types are supported (string, number, boolean). The comparison_string must be
11738
- # either eq (equals) or ne (not equals). The literal_string is the string value
11739
- # to filter to. The literal value must be valid for the type of field you are
11740
- # filtering by (string, number, boolean). For string fields, the literal value
11741
- # is interpreted as a regular expression using RE2 syntax. The literal value
11742
- # must match the entire field.
11743
- # For example, to filter for instances that do not have a name of example-
11744
- # instance, you would use name ne example-instance.
11745
- # You can filter on nested fields. For example, you could filter on instances
11746
- # that have set the scheduling.automaticRestart field to true. Use filtering on
11747
- # nested fields to take advantage of labels to organize and search for results
11748
- # based on label values.
11617
+ # A filter expression that filters resources listed in the response. The
11618
+ # expression must specify the field name, a comparison operator, and the value
11619
+ # that you want to use for filtering. The value must be a string, a number, or a
11620
+ # boolean. The comparison operator must be either =, !=, >, or <.
11621
+ # For example, if you are filtering Compute Engine instances, you can exclude
11622
+ # instances named example-instance by specifying name != example-instance.
11623
+ # You can also filter nested fields. For example, you could specify scheduling.
11624
+ # automaticRestart = false to include instances only if they are not scheduled
11625
+ # for automatic restarts. You can use filtering on nested fields to filter based
11626
+ # on resource labels.
11749
11627
  # To filter on multiple expressions, provide each separate expression within
11750
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
11751
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
11752
- # resources must match all expressions to pass the filters.
11628
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
11629
+ # Intel Skylake"). By default, each expression is an AND expression. However,
11630
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
11631
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
11632
+ # automaticRestart = true).
11753
11633
  # @param [Fixnum] max_results
11754
11634
  # The maximum number of results per page that should be returned. If the number
11755
11635
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12052,25 +11932,22 @@ module Google
12052
11932
  # @param [String] project
12053
11933
  # Project ID for this request.
12054
11934
  # @param [String] filter
12055
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12056
- # must be in the format: field_name comparison_string literal_string.
12057
- # The field_name is the name of the field you want to compare. Only atomic field
12058
- # types are supported (string, number, boolean). The comparison_string must be
12059
- # either eq (equals) or ne (not equals). The literal_string is the string value
12060
- # to filter to. The literal value must be valid for the type of field you are
12061
- # filtering by (string, number, boolean). For string fields, the literal value
12062
- # is interpreted as a regular expression using RE2 syntax. The literal value
12063
- # must match the entire field.
12064
- # For example, to filter for instances that do not have a name of example-
12065
- # instance, you would use name ne example-instance.
12066
- # You can filter on nested fields. For example, you could filter on instances
12067
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12068
- # nested fields to take advantage of labels to organize and search for results
12069
- # based on label values.
11935
+ # A filter expression that filters resources listed in the response. The
11936
+ # expression must specify the field name, a comparison operator, and the value
11937
+ # that you want to use for filtering. The value must be a string, a number, or a
11938
+ # boolean. The comparison operator must be either =, !=, >, or <.
11939
+ # For example, if you are filtering Compute Engine instances, you can exclude
11940
+ # instances named example-instance by specifying name != example-instance.
11941
+ # You can also filter nested fields. For example, you could specify scheduling.
11942
+ # automaticRestart = false to include instances only if they are not scheduled
11943
+ # for automatic restarts. You can use filtering on nested fields to filter based
11944
+ # on resource labels.
12070
11945
  # To filter on multiple expressions, provide each separate expression within
12071
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12072
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12073
- # resources must match all expressions to pass the filters.
11946
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
11947
+ # Intel Skylake"). By default, each expression is an AND expression. However,
11948
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
11949
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
11950
+ # automaticRestart = true).
12074
11951
  # @param [Fixnum] max_results
12075
11952
  # The maximum number of results per page that should be returned. If the number
12076
11953
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12348,25 +12225,22 @@ module Google
12348
12225
  # @param [String] project
12349
12226
  # Project ID for this request.
12350
12227
  # @param [String] filter
12351
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12352
- # must be in the format: field_name comparison_string literal_string.
12353
- # The field_name is the name of the field you want to compare. Only atomic field
12354
- # types are supported (string, number, boolean). The comparison_string must be
12355
- # either eq (equals) or ne (not equals). The literal_string is the string value
12356
- # to filter to. The literal value must be valid for the type of field you are
12357
- # filtering by (string, number, boolean). For string fields, the literal value
12358
- # is interpreted as a regular expression using RE2 syntax. The literal value
12359
- # must match the entire field.
12360
- # For example, to filter for instances that do not have a name of example-
12361
- # instance, you would use name ne example-instance.
12362
- # You can filter on nested fields. For example, you could filter on instances
12363
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12364
- # nested fields to take advantage of labels to organize and search for results
12365
- # based on label values.
12228
+ # A filter expression that filters resources listed in the response. The
12229
+ # expression must specify the field name, a comparison operator, and the value
12230
+ # that you want to use for filtering. The value must be a string, a number, or a
12231
+ # boolean. The comparison operator must be either =, !=, >, or <.
12232
+ # For example, if you are filtering Compute Engine instances, you can exclude
12233
+ # instances named example-instance by specifying name != example-instance.
12234
+ # You can also filter nested fields. For example, you could specify scheduling.
12235
+ # automaticRestart = false to include instances only if they are not scheduled
12236
+ # for automatic restarts. You can use filtering on nested fields to filter based
12237
+ # on resource labels.
12366
12238
  # To filter on multiple expressions, provide each separate expression within
12367
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12368
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12369
- # resources must match all expressions to pass the filters.
12239
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12240
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12241
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12242
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12243
+ # automaticRestart = true).
12370
12244
  # @param [Fixnum] max_results
12371
12245
  # The maximum number of results per page that should be returned. If the number
12372
12246
  # of available results is larger than maxResults, Compute Engine returns a
@@ -12946,25 +12820,22 @@ module Google
12946
12820
  # @param [String] project
12947
12821
  # Project ID for this request.
12948
12822
  # @param [String] filter
12949
- # Sets a filter `expression` for filtering listed resources. Your `expression`
12950
- # must be in the format: field_name comparison_string literal_string.
12951
- # The field_name is the name of the field you want to compare. Only atomic field
12952
- # types are supported (string, number, boolean). The comparison_string must be
12953
- # either eq (equals) or ne (not equals). The literal_string is the string value
12954
- # to filter to. The literal value must be valid for the type of field you are
12955
- # filtering by (string, number, boolean). For string fields, the literal value
12956
- # is interpreted as a regular expression using RE2 syntax. The literal value
12957
- # must match the entire field.
12958
- # For example, to filter for instances that do not have a name of example-
12959
- # instance, you would use name ne example-instance.
12960
- # You can filter on nested fields. For example, you could filter on instances
12961
- # that have set the scheduling.automaticRestart field to true. Use filtering on
12962
- # nested fields to take advantage of labels to organize and search for results
12963
- # based on label values.
12823
+ # A filter expression that filters resources listed in the response. The
12824
+ # expression must specify the field name, a comparison operator, and the value
12825
+ # that you want to use for filtering. The value must be a string, a number, or a
12826
+ # boolean. The comparison operator must be either =, !=, >, or <.
12827
+ # For example, if you are filtering Compute Engine instances, you can exclude
12828
+ # instances named example-instance by specifying name != example-instance.
12829
+ # You can also filter nested fields. For example, you could specify scheduling.
12830
+ # automaticRestart = false to include instances only if they are not scheduled
12831
+ # for automatic restarts. You can use filtering on nested fields to filter based
12832
+ # on resource labels.
12964
12833
  # To filter on multiple expressions, provide each separate expression within
12965
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
12966
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
12967
- # resources must match all expressions to pass the filters.
12834
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12835
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12836
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12837
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12838
+ # automaticRestart = true).
12968
12839
  # @param [Fixnum] max_results
12969
12840
  # The maximum number of results per page that should be returned. If the number
12970
12841
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13105,25 +12976,22 @@ module Google
13105
12976
  # @param [String] project
13106
12977
  # Project ID for this request.
13107
12978
  # @param [String] filter
13108
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13109
- # must be in the format: field_name comparison_string literal_string.
13110
- # The field_name is the name of the field you want to compare. Only atomic field
13111
- # types are supported (string, number, boolean). The comparison_string must be
13112
- # either eq (equals) or ne (not equals). The literal_string is the string value
13113
- # to filter to. The literal value must be valid for the type of field you are
13114
- # filtering by (string, number, boolean). For string fields, the literal value
13115
- # is interpreted as a regular expression using RE2 syntax. The literal value
13116
- # must match the entire field.
13117
- # For example, to filter for instances that do not have a name of example-
13118
- # instance, you would use name ne example-instance.
13119
- # You can filter on nested fields. For example, you could filter on instances
13120
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13121
- # nested fields to take advantage of labels to organize and search for results
13122
- # based on label values.
12979
+ # A filter expression that filters resources listed in the response. The
12980
+ # expression must specify the field name, a comparison operator, and the value
12981
+ # that you want to use for filtering. The value must be a string, a number, or a
12982
+ # boolean. The comparison operator must be either =, !=, >, or <.
12983
+ # For example, if you are filtering Compute Engine instances, you can exclude
12984
+ # instances named example-instance by specifying name != example-instance.
12985
+ # You can also filter nested fields. For example, you could specify scheduling.
12986
+ # automaticRestart = false to include instances only if they are not scheduled
12987
+ # for automatic restarts. You can use filtering on nested fields to filter based
12988
+ # on resource labels.
13123
12989
  # To filter on multiple expressions, provide each separate expression within
13124
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13125
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13126
- # resources must match all expressions to pass the filters.
12990
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
12991
+ # Intel Skylake"). By default, each expression is an AND expression. However,
12992
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
12993
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
12994
+ # automaticRestart = true).
13127
12995
  # @param [Fixnum] max_results
13128
12996
  # The maximum number of results per page that should be returned. If the number
13129
12997
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13225,25 +13093,22 @@ module Google
13225
13093
  # @param [String] zone
13226
13094
  # The name of the zone for this request.
13227
13095
  # @param [String] filter
13228
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13229
- # must be in the format: field_name comparison_string literal_string.
13230
- # The field_name is the name of the field you want to compare. Only atomic field
13231
- # types are supported (string, number, boolean). The comparison_string must be
13232
- # either eq (equals) or ne (not equals). The literal_string is the string value
13233
- # to filter to. The literal value must be valid for the type of field you are
13234
- # filtering by (string, number, boolean). For string fields, the literal value
13235
- # is interpreted as a regular expression using RE2 syntax. The literal value
13236
- # must match the entire field.
13237
- # For example, to filter for instances that do not have a name of example-
13238
- # instance, you would use name ne example-instance.
13239
- # You can filter on nested fields. For example, you could filter on instances
13240
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13241
- # nested fields to take advantage of labels to organize and search for results
13242
- # based on label values.
13096
+ # A filter expression that filters resources listed in the response. The
13097
+ # expression must specify the field name, a comparison operator, and the value
13098
+ # that you want to use for filtering. The value must be a string, a number, or a
13099
+ # boolean. The comparison operator must be either =, !=, >, or <.
13100
+ # For example, if you are filtering Compute Engine instances, you can exclude
13101
+ # instances named example-instance by specifying name != example-instance.
13102
+ # You can also filter nested fields. For example, you could specify scheduling.
13103
+ # automaticRestart = false to include instances only if they are not scheduled
13104
+ # for automatic restarts. You can use filtering on nested fields to filter based
13105
+ # on resource labels.
13243
13106
  # To filter on multiple expressions, provide each separate expression within
13244
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13245
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13246
- # resources must match all expressions to pass the filters.
13107
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13108
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13109
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13110
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13111
+ # automaticRestart = true).
13247
13112
  # @param [Fixnum] max_results
13248
13113
  # The maximum number of results per page that should be returned. If the number
13249
13114
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13302,25 +13167,22 @@ module Google
13302
13167
  # @param [String] project
13303
13168
  # Project ID for this request.
13304
13169
  # @param [String] filter
13305
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13306
- # must be in the format: field_name comparison_string literal_string.
13307
- # The field_name is the name of the field you want to compare. Only atomic field
13308
- # types are supported (string, number, boolean). The comparison_string must be
13309
- # either eq (equals) or ne (not equals). The literal_string is the string value
13310
- # to filter to. The literal value must be valid for the type of field you are
13311
- # filtering by (string, number, boolean). For string fields, the literal value
13312
- # is interpreted as a regular expression using RE2 syntax. The literal value
13313
- # must match the entire field.
13314
- # For example, to filter for instances that do not have a name of example-
13315
- # instance, you would use name ne example-instance.
13316
- # You can filter on nested fields. For example, you could filter on instances
13317
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13318
- # nested fields to take advantage of labels to organize and search for results
13319
- # based on label values.
13170
+ # A filter expression that filters resources listed in the response. The
13171
+ # expression must specify the field name, a comparison operator, and the value
13172
+ # that you want to use for filtering. The value must be a string, a number, or a
13173
+ # boolean. The comparison operator must be either =, !=, >, or <.
13174
+ # For example, if you are filtering Compute Engine instances, you can exclude
13175
+ # instances named example-instance by specifying name != example-instance.
13176
+ # You can also filter nested fields. For example, you could specify scheduling.
13177
+ # automaticRestart = false to include instances only if they are not scheduled
13178
+ # for automatic restarts. You can use filtering on nested fields to filter based
13179
+ # on resource labels.
13320
13180
  # To filter on multiple expressions, provide each separate expression within
13321
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13322
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13323
- # resources must match all expressions to pass the filters.
13181
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13182
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13183
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13184
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13185
+ # automaticRestart = true).
13324
13186
  # @param [Fixnum] max_results
13325
13187
  # The maximum number of results per page that should be returned. If the number
13326
13188
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13570,25 +13432,22 @@ module Google
13570
13432
  # @param [String] region
13571
13433
  # Name of the region for this request.
13572
13434
  # @param [String] filter
13573
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13574
- # must be in the format: field_name comparison_string literal_string.
13575
- # The field_name is the name of the field you want to compare. Only atomic field
13576
- # types are supported (string, number, boolean). The comparison_string must be
13577
- # either eq (equals) or ne (not equals). The literal_string is the string value
13578
- # to filter to. The literal value must be valid for the type of field you are
13579
- # filtering by (string, number, boolean). For string fields, the literal value
13580
- # is interpreted as a regular expression using RE2 syntax. The literal value
13581
- # must match the entire field.
13582
- # For example, to filter for instances that do not have a name of example-
13583
- # instance, you would use name ne example-instance.
13584
- # You can filter on nested fields. For example, you could filter on instances
13585
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13586
- # nested fields to take advantage of labels to organize and search for results
13587
- # based on label values.
13435
+ # A filter expression that filters resources listed in the response. The
13436
+ # expression must specify the field name, a comparison operator, and the value
13437
+ # that you want to use for filtering. The value must be a string, a number, or a
13438
+ # boolean. The comparison operator must be either =, !=, >, or <.
13439
+ # For example, if you are filtering Compute Engine instances, you can exclude
13440
+ # instances named example-instance by specifying name != example-instance.
13441
+ # You can also filter nested fields. For example, you could specify scheduling.
13442
+ # automaticRestart = false to include instances only if they are not scheduled
13443
+ # for automatic restarts. You can use filtering on nested fields to filter based
13444
+ # on resource labels.
13588
13445
  # To filter on multiple expressions, provide each separate expression within
13589
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13590
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13591
- # resources must match all expressions to pass the filters.
13446
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13447
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13448
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13449
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13450
+ # automaticRestart = true).
13592
13451
  # @param [Fixnum] max_results
13593
13452
  # The maximum number of results per page that should be returned. If the number
13594
13453
  # of available results is larger than maxResults, Compute Engine returns a
@@ -13736,25 +13595,22 @@ module Google
13736
13595
  # @param [String] project
13737
13596
  # Project ID for this request.
13738
13597
  # @param [String] filter
13739
- # Sets a filter `expression` for filtering listed resources. Your `expression`
13740
- # must be in the format: field_name comparison_string literal_string.
13741
- # The field_name is the name of the field you want to compare. Only atomic field
13742
- # types are supported (string, number, boolean). The comparison_string must be
13743
- # either eq (equals) or ne (not equals). The literal_string is the string value
13744
- # to filter to. The literal value must be valid for the type of field you are
13745
- # filtering by (string, number, boolean). For string fields, the literal value
13746
- # is interpreted as a regular expression using RE2 syntax. The literal value
13747
- # must match the entire field.
13748
- # For example, to filter for instances that do not have a name of example-
13749
- # instance, you would use name ne example-instance.
13750
- # You can filter on nested fields. For example, you could filter on instances
13751
- # that have set the scheduling.automaticRestart field to true. Use filtering on
13752
- # nested fields to take advantage of labels to organize and search for results
13753
- # based on label values.
13598
+ # A filter expression that filters resources listed in the response. The
13599
+ # expression must specify the field name, a comparison operator, and the value
13600
+ # that you want to use for filtering. The value must be a string, a number, or a
13601
+ # boolean. The comparison operator must be either =, !=, >, or <.
13602
+ # For example, if you are filtering Compute Engine instances, you can exclude
13603
+ # instances named example-instance by specifying name != example-instance.
13604
+ # You can also filter nested fields. For example, you could specify scheduling.
13605
+ # automaticRestart = false to include instances only if they are not scheduled
13606
+ # for automatic restarts. You can use filtering on nested fields to filter based
13607
+ # on resource labels.
13754
13608
  # To filter on multiple expressions, provide each separate expression within
13755
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
13756
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
13757
- # resources must match all expressions to pass the filters.
13609
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13610
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13611
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13612
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13613
+ # automaticRestart = true).
13758
13614
  # @param [Fixnum] max_results
13759
13615
  # The maximum number of results per page that should be returned. If the number
13760
13616
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14088,25 +13944,22 @@ module Google
14088
13944
  # The name of the zone where the network endpoint group is located. It should
14089
13945
  # comply with RFC1035.
14090
13946
  # @param [String] filter
14091
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14092
- # must be in the format: field_name comparison_string literal_string.
14093
- # The field_name is the name of the field you want to compare. Only atomic field
14094
- # types are supported (string, number, boolean). The comparison_string must be
14095
- # either eq (equals) or ne (not equals). The literal_string is the string value
14096
- # to filter to. The literal value must be valid for the type of field you are
14097
- # filtering by (string, number, boolean). For string fields, the literal value
14098
- # is interpreted as a regular expression using RE2 syntax. The literal value
14099
- # must match the entire field.
14100
- # For example, to filter for instances that do not have a name of example-
14101
- # instance, you would use name ne example-instance.
14102
- # You can filter on nested fields. For example, you could filter on instances
14103
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14104
- # nested fields to take advantage of labels to organize and search for results
14105
- # based on label values.
13947
+ # A filter expression that filters resources listed in the response. The
13948
+ # expression must specify the field name, a comparison operator, and the value
13949
+ # that you want to use for filtering. The value must be a string, a number, or a
13950
+ # boolean. The comparison operator must be either =, !=, >, or <.
13951
+ # For example, if you are filtering Compute Engine instances, you can exclude
13952
+ # instances named example-instance by specifying name != example-instance.
13953
+ # You can also filter nested fields. For example, you could specify scheduling.
13954
+ # automaticRestart = false to include instances only if they are not scheduled
13955
+ # for automatic restarts. You can use filtering on nested fields to filter based
13956
+ # on resource labels.
14106
13957
  # To filter on multiple expressions, provide each separate expression within
14107
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14108
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14109
- # resources must match all expressions to pass the filters.
13958
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
13959
+ # Intel Skylake"). By default, each expression is an AND expression. However,
13960
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
13961
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
13962
+ # automaticRestart = true).
14110
13963
  # @param [Fixnum] max_results
14111
13964
  # The maximum number of results per page that should be returned. If the number
14112
13965
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14172,25 +14025,22 @@ module Google
14172
14025
  # of included network endpoints. It should comply with RFC1035.
14173
14026
  # @param [Google::Apis::ComputeAlpha::NetworkEndpointGroupsListEndpointsRequest] network_endpoint_groups_list_endpoints_request_object
14174
14027
  # @param [String] filter
14175
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14176
- # must be in the format: field_name comparison_string literal_string.
14177
- # The field_name is the name of the field you want to compare. Only atomic field
14178
- # types are supported (string, number, boolean). The comparison_string must be
14179
- # either eq (equals) or ne (not equals). The literal_string is the string value
14180
- # to filter to. The literal value must be valid for the type of field you are
14181
- # filtering by (string, number, boolean). For string fields, the literal value
14182
- # is interpreted as a regular expression using RE2 syntax. The literal value
14183
- # must match the entire field.
14184
- # For example, to filter for instances that do not have a name of example-
14185
- # instance, you would use name ne example-instance.
14186
- # You can filter on nested fields. For example, you could filter on instances
14187
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14188
- # nested fields to take advantage of labels to organize and search for results
14189
- # based on label values.
14028
+ # A filter expression that filters resources listed in the response. The
14029
+ # expression must specify the field name, a comparison operator, and the value
14030
+ # that you want to use for filtering. The value must be a string, a number, or a
14031
+ # boolean. The comparison operator must be either =, !=, >, or <.
14032
+ # For example, if you are filtering Compute Engine instances, you can exclude
14033
+ # instances named example-instance by specifying name != example-instance.
14034
+ # You can also filter nested fields. For example, you could specify scheduling.
14035
+ # automaticRestart = false to include instances only if they are not scheduled
14036
+ # for automatic restarts. You can use filtering on nested fields to filter based
14037
+ # on resource labels.
14190
14038
  # To filter on multiple expressions, provide each separate expression within
14191
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14192
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14193
- # resources must match all expressions to pass the filters.
14039
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
14040
+ # Intel Skylake"). By default, each expression is an AND expression. However,
14041
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
14042
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14043
+ # automaticRestart = true).
14194
14044
  # @param [Fixnum] max_results
14195
14045
  # The maximum number of results per page that should be returned. If the number
14196
14046
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14489,25 +14339,22 @@ module Google
14489
14339
  # @param [String] project
14490
14340
  # Project ID for this request.
14491
14341
  # @param [String] filter
14492
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14493
- # must be in the format: field_name comparison_string literal_string.
14494
- # The field_name is the name of the field you want to compare. Only atomic field
14495
- # types are supported (string, number, boolean). The comparison_string must be
14496
- # either eq (equals) or ne (not equals). The literal_string is the string value
14497
- # to filter to. The literal value must be valid for the type of field you are
14498
- # filtering by (string, number, boolean). For string fields, the literal value
14499
- # is interpreted as a regular expression using RE2 syntax. The literal value
14500
- # must match the entire field.
14501
- # For example, to filter for instances that do not have a name of example-
14502
- # instance, you would use name ne example-instance.
14503
- # You can filter on nested fields. For example, you could filter on instances
14504
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14505
- # nested fields to take advantage of labels to organize and search for results
14506
- # based on label values.
14342
+ # A filter expression that filters resources listed in the response. The
14343
+ # expression must specify the field name, a comparison operator, and the value
14344
+ # that you want to use for filtering. The value must be a string, a number, or a
14345
+ # boolean. The comparison operator must be either =, !=, >, or <.
14346
+ # For example, if you are filtering Compute Engine instances, you can exclude
14347
+ # instances named example-instance by specifying name != example-instance.
14348
+ # You can also filter nested fields. For example, you could specify scheduling.
14349
+ # automaticRestart = false to include instances only if they are not scheduled
14350
+ # for automatic restarts. You can use filtering on nested fields to filter based
14351
+ # on resource labels.
14507
14352
  # To filter on multiple expressions, provide each separate expression within
14508
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14509
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14510
- # resources must match all expressions to pass the filters.
14353
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
14354
+ # Intel Skylake"). By default, each expression is an AND expression. However,
14355
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
14356
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14357
+ # automaticRestart = true).
14511
14358
  # @param [Fixnum] max_results
14512
14359
  # The maximum number of results per page that should be returned. If the number
14513
14360
  # of available results is larger than maxResults, Compute Engine returns a
@@ -14567,25 +14414,22 @@ module Google
14567
14414
  # @param [String] network
14568
14415
  # Name of the network to return.
14569
14416
  # @param [String] filter
14570
- # Sets a filter `expression` for filtering listed resources. Your `expression`
14571
- # must be in the format: field_name comparison_string literal_string.
14572
- # The field_name is the name of the field you want to compare. Only atomic field
14573
- # types are supported (string, number, boolean). The comparison_string must be
14574
- # either eq (equals) or ne (not equals). The literal_string is the string value
14575
- # to filter to. The literal value must be valid for the type of field you are
14576
- # filtering by (string, number, boolean). For string fields, the literal value
14577
- # is interpreted as a regular expression using RE2 syntax. The literal value
14578
- # must match the entire field.
14579
- # For example, to filter for instances that do not have a name of example-
14580
- # instance, you would use name ne example-instance.
14581
- # You can filter on nested fields. For example, you could filter on instances
14582
- # that have set the scheduling.automaticRestart field to true. Use filtering on
14583
- # nested fields to take advantage of labels to organize and search for results
14584
- # based on label values.
14417
+ # A filter expression that filters resources listed in the response. The
14418
+ # expression must specify the field name, a comparison operator, and the value
14419
+ # that you want to use for filtering. The value must be a string, a number, or a
14420
+ # boolean. The comparison operator must be either =, !=, >, or <.
14421
+ # For example, if you are filtering Compute Engine instances, you can exclude
14422
+ # instances named example-instance by specifying name != example-instance.
14423
+ # You can also filter nested fields. For example, you could specify scheduling.
14424
+ # automaticRestart = false to include instances only if they are not scheduled
14425
+ # for automatic restarts. You can use filtering on nested fields to filter based
14426
+ # on resource labels.
14585
14427
  # To filter on multiple expressions, provide each separate expression within
14586
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
14587
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
14588
- # resources must match all expressions to pass the filters.
14428
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
14429
+ # Intel Skylake"). By default, each expression is an AND expression. However,
14430
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
14431
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
14432
+ # automaticRestart = true).
14589
14433
  # @param [String] ip_cidr_range
14590
14434
  # (Optional) IP CIDR range filter, example: "10.128.10.0/30".
14591
14435
  # @param [Fixnum] max_results
@@ -15933,25 +15777,22 @@ module Google
15933
15777
  # @param [String] region
15934
15778
  # Name of the region scoping this request.
15935
15779
  # @param [String] filter
15936
- # Sets a filter `expression` for filtering listed resources. Your `expression`
15937
- # must be in the format: field_name comparison_string literal_string.
15938
- # The field_name is the name of the field you want to compare. Only atomic field
15939
- # types are supported (string, number, boolean). The comparison_string must be
15940
- # either eq (equals) or ne (not equals). The literal_string is the string value
15941
- # to filter to. The literal value must be valid for the type of field you are
15942
- # filtering by (string, number, boolean). For string fields, the literal value
15943
- # is interpreted as a regular expression using RE2 syntax. The literal value
15944
- # must match the entire field.
15945
- # For example, to filter for instances that do not have a name of example-
15946
- # instance, you would use name ne example-instance.
15947
- # You can filter on nested fields. For example, you could filter on instances
15948
- # that have set the scheduling.automaticRestart field to true. Use filtering on
15949
- # nested fields to take advantage of labels to organize and search for results
15950
- # based on label values.
15780
+ # A filter expression that filters resources listed in the response. The
15781
+ # expression must specify the field name, a comparison operator, and the value
15782
+ # that you want to use for filtering. The value must be a string, a number, or a
15783
+ # boolean. The comparison operator must be either =, !=, >, or <.
15784
+ # For example, if you are filtering Compute Engine instances, you can exclude
15785
+ # instances named example-instance by specifying name != example-instance.
15786
+ # You can also filter nested fields. For example, you could specify scheduling.
15787
+ # automaticRestart = false to include instances only if they are not scheduled
15788
+ # for automatic restarts. You can use filtering on nested fields to filter based
15789
+ # on resource labels.
15951
15790
  # To filter on multiple expressions, provide each separate expression within
15952
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
15953
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
15954
- # resources must match all expressions to pass the filters.
15791
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
15792
+ # Intel Skylake"). By default, each expression is an AND expression. However,
15793
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
15794
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
15795
+ # automaticRestart = true).
15955
15796
  # @param [Fixnum] max_results
15956
15797
  # The maximum number of results per page that should be returned. If the number
15957
15798
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16365,25 +16206,22 @@ module Google
16365
16206
  # @param [String] region
16366
16207
  # Name of the region scoping this request.
16367
16208
  # @param [String] filter
16368
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16369
- # must be in the format: field_name comparison_string literal_string.
16370
- # The field_name is the name of the field you want to compare. Only atomic field
16371
- # types are supported (string, number, boolean). The comparison_string must be
16372
- # either eq (equals) or ne (not equals). The literal_string is the string value
16373
- # to filter to. The literal value must be valid for the type of field you are
16374
- # filtering by (string, number, boolean). For string fields, the literal value
16375
- # is interpreted as a regular expression using RE2 syntax. The literal value
16376
- # must match the entire field.
16377
- # For example, to filter for instances that do not have a name of example-
16378
- # instance, you would use name ne example-instance.
16379
- # You can filter on nested fields. For example, you could filter on instances
16380
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16381
- # nested fields to take advantage of labels to organize and search for results
16382
- # based on label values.
16209
+ # A filter expression that filters resources listed in the response. The
16210
+ # expression must specify the field name, a comparison operator, and the value
16211
+ # that you want to use for filtering. The value must be a string, a number, or a
16212
+ # boolean. The comparison operator must be either =, !=, >, or <.
16213
+ # For example, if you are filtering Compute Engine instances, you can exclude
16214
+ # instances named example-instance by specifying name != example-instance.
16215
+ # You can also filter nested fields. For example, you could specify scheduling.
16216
+ # automaticRestart = false to include instances only if they are not scheduled
16217
+ # for automatic restarts. You can use filtering on nested fields to filter based
16218
+ # on resource labels.
16383
16219
  # To filter on multiple expressions, provide each separate expression within
16384
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16385
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16386
- # resources must match all expressions to pass the filters.
16220
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16221
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16222
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16223
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16224
+ # automaticRestart = true).
16387
16225
  # @param [Fixnum] max_results
16388
16226
  # The maximum number of results per page that should be returned. If the number
16389
16227
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16605,25 +16443,22 @@ module Google
16605
16443
  # @param [String] project
16606
16444
  # Project ID for this request.
16607
16445
  # @param [String] filter
16608
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16609
- # must be in the format: field_name comparison_string literal_string.
16610
- # The field_name is the name of the field you want to compare. Only atomic field
16611
- # types are supported (string, number, boolean). The comparison_string must be
16612
- # either eq (equals) or ne (not equals). The literal_string is the string value
16613
- # to filter to. The literal value must be valid for the type of field you are
16614
- # filtering by (string, number, boolean). For string fields, the literal value
16615
- # is interpreted as a regular expression using RE2 syntax. The literal value
16616
- # must match the entire field.
16617
- # For example, to filter for instances that do not have a name of example-
16618
- # instance, you would use name ne example-instance.
16619
- # You can filter on nested fields. For example, you could filter on instances
16620
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16621
- # nested fields to take advantage of labels to organize and search for results
16622
- # based on label values.
16446
+ # A filter expression that filters resources listed in the response. The
16447
+ # expression must specify the field name, a comparison operator, and the value
16448
+ # that you want to use for filtering. The value must be a string, a number, or a
16449
+ # boolean. The comparison operator must be either =, !=, >, or <.
16450
+ # For example, if you are filtering Compute Engine instances, you can exclude
16451
+ # instances named example-instance by specifying name != example-instance.
16452
+ # You can also filter nested fields. For example, you could specify scheduling.
16453
+ # automaticRestart = false to include instances only if they are not scheduled
16454
+ # for automatic restarts. You can use filtering on nested fields to filter based
16455
+ # on resource labels.
16623
16456
  # To filter on multiple expressions, provide each separate expression within
16624
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16625
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16626
- # resources must match all expressions to pass the filters.
16457
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16458
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16459
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16460
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16461
+ # automaticRestart = true).
16627
16462
  # @param [Fixnum] max_results
16628
16463
  # The maximum number of results per page that should be returned. If the number
16629
16464
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16779,25 +16614,22 @@ module Google
16779
16614
  # @param [String] region
16780
16615
  # Name of the region for this request.
16781
16616
  # @param [String] filter
16782
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16783
- # must be in the format: field_name comparison_string literal_string.
16784
- # The field_name is the name of the field you want to compare. Only atomic field
16785
- # types are supported (string, number, boolean). The comparison_string must be
16786
- # either eq (equals) or ne (not equals). The literal_string is the string value
16787
- # to filter to. The literal value must be valid for the type of field you are
16788
- # filtering by (string, number, boolean). For string fields, the literal value
16789
- # is interpreted as a regular expression using RE2 syntax. The literal value
16790
- # must match the entire field.
16791
- # For example, to filter for instances that do not have a name of example-
16792
- # instance, you would use name ne example-instance.
16793
- # You can filter on nested fields. For example, you could filter on instances
16794
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16795
- # nested fields to take advantage of labels to organize and search for results
16796
- # based on label values.
16617
+ # A filter expression that filters resources listed in the response. The
16618
+ # expression must specify the field name, a comparison operator, and the value
16619
+ # that you want to use for filtering. The value must be a string, a number, or a
16620
+ # boolean. The comparison operator must be either =, !=, >, or <.
16621
+ # For example, if you are filtering Compute Engine instances, you can exclude
16622
+ # instances named example-instance by specifying name != example-instance.
16623
+ # You can also filter nested fields. For example, you could specify scheduling.
16624
+ # automaticRestart = false to include instances only if they are not scheduled
16625
+ # for automatic restarts. You can use filtering on nested fields to filter based
16626
+ # on resource labels.
16797
16627
  # To filter on multiple expressions, provide each separate expression within
16798
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16799
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16800
- # resources must match all expressions to pass the filters.
16628
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16629
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16630
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16631
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16632
+ # automaticRestart = true).
16801
16633
  # @param [Fixnum] max_results
16802
16634
  # The maximum number of results per page that should be returned. If the number
16803
16635
  # of available results is larger than maxResults, Compute Engine returns a
@@ -16944,25 +16776,22 @@ module Google
16944
16776
  # @param [String] region
16945
16777
  # The name of the region for this request.
16946
16778
  # @param [String] filter
16947
- # Sets a filter `expression` for filtering listed resources. Your `expression`
16948
- # must be in the format: field_name comparison_string literal_string.
16949
- # The field_name is the name of the field you want to compare. Only atomic field
16950
- # types are supported (string, number, boolean). The comparison_string must be
16951
- # either eq (equals) or ne (not equals). The literal_string is the string value
16952
- # to filter to. The literal value must be valid for the type of field you are
16953
- # filtering by (string, number, boolean). For string fields, the literal value
16954
- # is interpreted as a regular expression using RE2 syntax. The literal value
16955
- # must match the entire field.
16956
- # For example, to filter for instances that do not have a name of example-
16957
- # instance, you would use name ne example-instance.
16958
- # You can filter on nested fields. For example, you could filter on instances
16959
- # that have set the scheduling.automaticRestart field to true. Use filtering on
16960
- # nested fields to take advantage of labels to organize and search for results
16961
- # based on label values.
16779
+ # A filter expression that filters resources listed in the response. The
16780
+ # expression must specify the field name, a comparison operator, and the value
16781
+ # that you want to use for filtering. The value must be a string, a number, or a
16782
+ # boolean. The comparison operator must be either =, !=, >, or <.
16783
+ # For example, if you are filtering Compute Engine instances, you can exclude
16784
+ # instances named example-instance by specifying name != example-instance.
16785
+ # You can also filter nested fields. For example, you could specify scheduling.
16786
+ # automaticRestart = false to include instances only if they are not scheduled
16787
+ # for automatic restarts. You can use filtering on nested fields to filter based
16788
+ # on resource labels.
16962
16789
  # To filter on multiple expressions, provide each separate expression within
16963
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
16964
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
16965
- # resources must match all expressions to pass the filters.
16790
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
16791
+ # Intel Skylake"). By default, each expression is an AND expression. However,
16792
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
16793
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
16794
+ # automaticRestart = true).
16966
16795
  # @param [Fixnum] max_results
16967
16796
  # The maximum number of results per page that should be returned. If the number
16968
16797
  # of available results is larger than maxResults, Compute Engine returns a
@@ -17235,25 +17064,22 @@ module Google
17235
17064
  # @param [String] region
17236
17065
  # Name of the region for this request.
17237
17066
  # @param [String] filter
17238
- # Sets a filter `expression` for filtering listed resources. Your `expression`
17239
- # must be in the format: field_name comparison_string literal_string.
17240
- # The field_name is the name of the field you want to compare. Only atomic field
17241
- # types are supported (string, number, boolean). The comparison_string must be
17242
- # either eq (equals) or ne (not equals). The literal_string is the string value
17243
- # to filter to. The literal value must be valid for the type of field you are
17244
- # filtering by (string, number, boolean). For string fields, the literal value
17245
- # is interpreted as a regular expression using RE2 syntax. The literal value
17246
- # must match the entire field.
17247
- # For example, to filter for instances that do not have a name of example-
17248
- # instance, you would use name ne example-instance.
17249
- # You can filter on nested fields. For example, you could filter on instances
17250
- # that have set the scheduling.automaticRestart field to true. Use filtering on
17251
- # nested fields to take advantage of labels to organize and search for results
17252
- # based on label values.
17067
+ # A filter expression that filters resources listed in the response. The
17068
+ # expression must specify the field name, a comparison operator, and the value
17069
+ # that you want to use for filtering. The value must be a string, a number, or a
17070
+ # boolean. The comparison operator must be either =, !=, >, or <.
17071
+ # For example, if you are filtering Compute Engine instances, you can exclude
17072
+ # instances named example-instance by specifying name != example-instance.
17073
+ # You can also filter nested fields. For example, you could specify scheduling.
17074
+ # automaticRestart = false to include instances only if they are not scheduled
17075
+ # for automatic restarts. You can use filtering on nested fields to filter based
17076
+ # on resource labels.
17253
17077
  # To filter on multiple expressions, provide each separate expression within
17254
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
17255
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
17256
- # resources must match all expressions to pass the filters.
17078
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
17079
+ # Intel Skylake"). By default, each expression is an AND expression. However,
17080
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
17081
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
17082
+ # automaticRestart = true).
17257
17083
  # @param [Fixnum] max_results
17258
17084
  # The maximum number of results per page that should be returned. If the number
17259
17085
  # of available results is larger than maxResults, Compute Engine returns a
@@ -17846,25 +17672,22 @@ module Google
17846
17672
  # @param [String] region
17847
17673
  # Name of the region scoping this request.
17848
17674
  # @param [String] filter
17849
- # Sets a filter `expression` for filtering listed resources. Your `expression`
17850
- # must be in the format: field_name comparison_string literal_string.
17851
- # The field_name is the name of the field you want to compare. Only atomic field
17852
- # types are supported (string, number, boolean). The comparison_string must be
17853
- # either eq (equals) or ne (not equals). The literal_string is the string value
17854
- # to filter to. The literal value must be valid for the type of field you are
17855
- # filtering by (string, number, boolean). For string fields, the literal value
17856
- # is interpreted as a regular expression using RE2 syntax. The literal value
17857
- # must match the entire field.
17858
- # For example, to filter for instances that do not have a name of example-
17859
- # instance, you would use name ne example-instance.
17860
- # You can filter on nested fields. For example, you could filter on instances
17861
- # that have set the scheduling.automaticRestart field to true. Use filtering on
17862
- # nested fields to take advantage of labels to organize and search for results
17863
- # based on label values.
17675
+ # A filter expression that filters resources listed in the response. The
17676
+ # expression must specify the field name, a comparison operator, and the value
17677
+ # that you want to use for filtering. The value must be a string, a number, or a
17678
+ # boolean. The comparison operator must be either =, !=, >, or <.
17679
+ # For example, if you are filtering Compute Engine instances, you can exclude
17680
+ # instances named example-instance by specifying name != example-instance.
17681
+ # You can also filter nested fields. For example, you could specify scheduling.
17682
+ # automaticRestart = false to include instances only if they are not scheduled
17683
+ # for automatic restarts. You can use filtering on nested fields to filter based
17684
+ # on resource labels.
17864
17685
  # To filter on multiple expressions, provide each separate expression within
17865
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
17866
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
17867
- # resources must match all expressions to pass the filters.
17686
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
17687
+ # Intel Skylake"). By default, each expression is an AND expression. However,
17688
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
17689
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
17690
+ # automaticRestart = true).
17868
17691
  # @param [Fixnum] max_results
17869
17692
  # The maximum number of results per page that should be returned. If the number
17870
17693
  # of available results is larger than maxResults, Compute Engine returns a
@@ -17978,25 +17801,22 @@ module Google
17978
17801
  # @param [String] instance_group_manager
17979
17802
  # The name of the managed instance group. It should conform to RFC1035.
17980
17803
  # @param [String] filter
17981
- # Sets a filter `expression` for filtering listed resources. Your `expression`
17982
- # must be in the format: field_name comparison_string literal_string.
17983
- # The field_name is the name of the field you want to compare. Only atomic field
17984
- # types are supported (string, number, boolean). The comparison_string must be
17985
- # either eq (equals) or ne (not equals). The literal_string is the string value
17986
- # to filter to. The literal value must be valid for the type of field you are
17987
- # filtering by (string, number, boolean). For string fields, the literal value
17988
- # is interpreted as a regular expression using RE2 syntax. The literal value
17989
- # must match the entire field.
17990
- # For example, to filter for instances that do not have a name of example-
17991
- # instance, you would use name ne example-instance.
17992
- # You can filter on nested fields. For example, you could filter on instances
17993
- # that have set the scheduling.automaticRestart field to true. Use filtering on
17994
- # nested fields to take advantage of labels to organize and search for results
17995
- # based on label values.
17804
+ # A filter expression that filters resources listed in the response. The
17805
+ # expression must specify the field name, a comparison operator, and the value
17806
+ # that you want to use for filtering. The value must be a string, a number, or a
17807
+ # boolean. The comparison operator must be either =, !=, >, or <.
17808
+ # For example, if you are filtering Compute Engine instances, you can exclude
17809
+ # instances named example-instance by specifying name != example-instance.
17810
+ # You can also filter nested fields. For example, you could specify scheduling.
17811
+ # automaticRestart = false to include instances only if they are not scheduled
17812
+ # for automatic restarts. You can use filtering on nested fields to filter based
17813
+ # on resource labels.
17996
17814
  # To filter on multiple expressions, provide each separate expression within
17997
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
17998
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
17999
- # resources must match all expressions to pass the filters.
17815
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
17816
+ # Intel Skylake"). By default, each expression is an AND expression. However,
17817
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
17818
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
17819
+ # automaticRestart = true).
18000
17820
  # @param [Fixnum] max_results
18001
17821
  # The maximum number of results per page that should be returned. If the number
18002
17822
  # of available results is larger than maxResults, Compute Engine returns a
@@ -18612,25 +18432,22 @@ module Google
18612
18432
  # @param [String] region
18613
18433
  # Name of the region scoping this request.
18614
18434
  # @param [String] filter
18615
- # Sets a filter `expression` for filtering listed resources. Your `expression`
18616
- # must be in the format: field_name comparison_string literal_string.
18617
- # The field_name is the name of the field you want to compare. Only atomic field
18618
- # types are supported (string, number, boolean). The comparison_string must be
18619
- # either eq (equals) or ne (not equals). The literal_string is the string value
18620
- # to filter to. The literal value must be valid for the type of field you are
18621
- # filtering by (string, number, boolean). For string fields, the literal value
18622
- # is interpreted as a regular expression using RE2 syntax. The literal value
18623
- # must match the entire field.
18624
- # For example, to filter for instances that do not have a name of example-
18625
- # instance, you would use name ne example-instance.
18626
- # You can filter on nested fields. For example, you could filter on instances
18627
- # that have set the scheduling.automaticRestart field to true. Use filtering on
18628
- # nested fields to take advantage of labels to organize and search for results
18629
- # based on label values.
18435
+ # A filter expression that filters resources listed in the response. The
18436
+ # expression must specify the field name, a comparison operator, and the value
18437
+ # that you want to use for filtering. The value must be a string, a number, or a
18438
+ # boolean. The comparison operator must be either =, !=, >, or <.
18439
+ # For example, if you are filtering Compute Engine instances, you can exclude
18440
+ # instances named example-instance by specifying name != example-instance.
18441
+ # You can also filter nested fields. For example, you could specify scheduling.
18442
+ # automaticRestart = false to include instances only if they are not scheduled
18443
+ # for automatic restarts. You can use filtering on nested fields to filter based
18444
+ # on resource labels.
18630
18445
  # To filter on multiple expressions, provide each separate expression within
18631
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
18632
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
18633
- # resources must match all expressions to pass the filters.
18446
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
18447
+ # Intel Skylake"). By default, each expression is an AND expression. However,
18448
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
18449
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
18450
+ # automaticRestart = true).
18634
18451
  # @param [Fixnum] max_results
18635
18452
  # The maximum number of results per page that should be returned. If the number
18636
18453
  # of available results is larger than maxResults, Compute Engine returns a
@@ -18696,25 +18513,22 @@ module Google
18696
18513
  # Name of the regional instance group for which we want to list the instances.
18697
18514
  # @param [Google::Apis::ComputeAlpha::RegionInstanceGroupsListInstancesRequest] region_instance_groups_list_instances_request_object
18698
18515
  # @param [String] filter
18699
- # Sets a filter `expression` for filtering listed resources. Your `expression`
18700
- # must be in the format: field_name comparison_string literal_string.
18701
- # The field_name is the name of the field you want to compare. Only atomic field
18702
- # types are supported (string, number, boolean). The comparison_string must be
18703
- # either eq (equals) or ne (not equals). The literal_string is the string value
18704
- # to filter to. The literal value must be valid for the type of field you are
18705
- # filtering by (string, number, boolean). For string fields, the literal value
18706
- # is interpreted as a regular expression using RE2 syntax. The literal value
18707
- # must match the entire field.
18708
- # For example, to filter for instances that do not have a name of example-
18709
- # instance, you would use name ne example-instance.
18710
- # You can filter on nested fields. For example, you could filter on instances
18711
- # that have set the scheduling.automaticRestart field to true. Use filtering on
18712
- # nested fields to take advantage of labels to organize and search for results
18713
- # based on label values.
18516
+ # A filter expression that filters resources listed in the response. The
18517
+ # expression must specify the field name, a comparison operator, and the value
18518
+ # that you want to use for filtering. The value must be a string, a number, or a
18519
+ # boolean. The comparison operator must be either =, !=, >, or <.
18520
+ # For example, if you are filtering Compute Engine instances, you can exclude
18521
+ # instances named example-instance by specifying name != example-instance.
18522
+ # You can also filter nested fields. For example, you could specify scheduling.
18523
+ # automaticRestart = false to include instances only if they are not scheduled
18524
+ # for automatic restarts. You can use filtering on nested fields to filter based
18525
+ # on resource labels.
18714
18526
  # To filter on multiple expressions, provide each separate expression within
18715
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
18716
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
18717
- # resources must match all expressions to pass the filters.
18527
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
18528
+ # Intel Skylake"). By default, each expression is an AND expression. However,
18529
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
18530
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
18531
+ # automaticRestart = true).
18718
18532
  # @param [Fixnum] max_results
18719
18533
  # The maximum number of results per page that should be returned. If the number
18720
18534
  # of available results is larger than maxResults, Compute Engine returns a
@@ -18958,25 +18772,22 @@ module Google
18958
18772
  # @param [String] region
18959
18773
  # Name of the region for this request.
18960
18774
  # @param [String] filter
18961
- # Sets a filter `expression` for filtering listed resources. Your `expression`
18962
- # must be in the format: field_name comparison_string literal_string.
18963
- # The field_name is the name of the field you want to compare. Only atomic field
18964
- # types are supported (string, number, boolean). The comparison_string must be
18965
- # either eq (equals) or ne (not equals). The literal_string is the string value
18966
- # to filter to. The literal value must be valid for the type of field you are
18967
- # filtering by (string, number, boolean). For string fields, the literal value
18968
- # is interpreted as a regular expression using RE2 syntax. The literal value
18969
- # must match the entire field.
18970
- # For example, to filter for instances that do not have a name of example-
18971
- # instance, you would use name ne example-instance.
18972
- # You can filter on nested fields. For example, you could filter on instances
18973
- # that have set the scheduling.automaticRestart field to true. Use filtering on
18974
- # nested fields to take advantage of labels to organize and search for results
18975
- # based on label values.
18775
+ # A filter expression that filters resources listed in the response. The
18776
+ # expression must specify the field name, a comparison operator, and the value
18777
+ # that you want to use for filtering. The value must be a string, a number, or a
18778
+ # boolean. The comparison operator must be either =, !=, >, or <.
18779
+ # For example, if you are filtering Compute Engine instances, you can exclude
18780
+ # instances named example-instance by specifying name != example-instance.
18781
+ # You can also filter nested fields. For example, you could specify scheduling.
18782
+ # automaticRestart = false to include instances only if they are not scheduled
18783
+ # for automatic restarts. You can use filtering on nested fields to filter based
18784
+ # on resource labels.
18976
18785
  # To filter on multiple expressions, provide each separate expression within
18977
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
18978
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
18979
- # resources must match all expressions to pass the filters.
18786
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
18787
+ # Intel Skylake"). By default, each expression is an AND expression. However,
18788
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
18789
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
18790
+ # automaticRestart = true).
18980
18791
  # @param [Fixnum] max_results
18981
18792
  # The maximum number of results per page that should be returned. If the number
18982
18793
  # of available results is larger than maxResults, Compute Engine returns a
@@ -19074,25 +18885,22 @@ module Google
19074
18885
  # @param [String] project
19075
18886
  # Project ID for this request.
19076
18887
  # @param [String] filter
19077
- # Sets a filter `expression` for filtering listed resources. Your `expression`
19078
- # must be in the format: field_name comparison_string literal_string.
19079
- # The field_name is the name of the field you want to compare. Only atomic field
19080
- # types are supported (string, number, boolean). The comparison_string must be
19081
- # either eq (equals) or ne (not equals). The literal_string is the string value
19082
- # to filter to. The literal value must be valid for the type of field you are
19083
- # filtering by (string, number, boolean). For string fields, the literal value
19084
- # is interpreted as a regular expression using RE2 syntax. The literal value
19085
- # must match the entire field.
19086
- # For example, to filter for instances that do not have a name of example-
19087
- # instance, you would use name ne example-instance.
19088
- # You can filter on nested fields. For example, you could filter on instances
19089
- # that have set the scheduling.automaticRestart field to true. Use filtering on
19090
- # nested fields to take advantage of labels to organize and search for results
19091
- # based on label values.
18888
+ # A filter expression that filters resources listed in the response. The
18889
+ # expression must specify the field name, a comparison operator, and the value
18890
+ # that you want to use for filtering. The value must be a string, a number, or a
18891
+ # boolean. The comparison operator must be either =, !=, >, or <.
18892
+ # For example, if you are filtering Compute Engine instances, you can exclude
18893
+ # instances named example-instance by specifying name != example-instance.
18894
+ # You can also filter nested fields. For example, you could specify scheduling.
18895
+ # automaticRestart = false to include instances only if they are not scheduled
18896
+ # for automatic restarts. You can use filtering on nested fields to filter based
18897
+ # on resource labels.
19092
18898
  # To filter on multiple expressions, provide each separate expression within
19093
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
19094
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
19095
- # resources must match all expressions to pass the filters.
18899
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
18900
+ # Intel Skylake"). By default, each expression is an AND expression. However,
18901
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
18902
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
18903
+ # automaticRestart = true).
19096
18904
  # @param [Fixnum] max_results
19097
18905
  # The maximum number of results per page that should be returned. If the number
19098
18906
  # of available results is larger than maxResults, Compute Engine returns a
@@ -19150,25 +18958,22 @@ module Google
19150
18958
  # @param [String] project
19151
18959
  # Project ID for this request.
19152
18960
  # @param [String] filter
19153
- # Sets a filter `expression` for filtering listed resources. Your `expression`
19154
- # must be in the format: field_name comparison_string literal_string.
19155
- # The field_name is the name of the field you want to compare. Only atomic field
19156
- # types are supported (string, number, boolean). The comparison_string must be
19157
- # either eq (equals) or ne (not equals). The literal_string is the string value
19158
- # to filter to. The literal value must be valid for the type of field you are
19159
- # filtering by (string, number, boolean). For string fields, the literal value
19160
- # is interpreted as a regular expression using RE2 syntax. The literal value
19161
- # must match the entire field.
19162
- # For example, to filter for instances that do not have a name of example-
19163
- # instance, you would use name ne example-instance.
19164
- # You can filter on nested fields. For example, you could filter on instances
19165
- # that have set the scheduling.automaticRestart field to true. Use filtering on
19166
- # nested fields to take advantage of labels to organize and search for results
19167
- # based on label values.
18961
+ # A filter expression that filters resources listed in the response. The
18962
+ # expression must specify the field name, a comparison operator, and the value
18963
+ # that you want to use for filtering. The value must be a string, a number, or a
18964
+ # boolean. The comparison operator must be either =, !=, >, or <.
18965
+ # For example, if you are filtering Compute Engine instances, you can exclude
18966
+ # instances named example-instance by specifying name != example-instance.
18967
+ # You can also filter nested fields. For example, you could specify scheduling.
18968
+ # automaticRestart = false to include instances only if they are not scheduled
18969
+ # for automatic restarts. You can use filtering on nested fields to filter based
18970
+ # on resource labels.
19168
18971
  # To filter on multiple expressions, provide each separate expression within
19169
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
19170
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
19171
- # resources must match all expressions to pass the filters.
18972
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
18973
+ # Intel Skylake"). By default, each expression is an AND expression. However,
18974
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
18975
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
18976
+ # automaticRestart = true).
19172
18977
  # @param [Fixnum] max_results
19173
18978
  # The maximum number of results per page that should be returned. If the number
19174
18979
  # of available results is larger than maxResults, Compute Engine returns a
@@ -19418,25 +19223,22 @@ module Google
19418
19223
  # @param [String] region
19419
19224
  # Name of the region for this request.
19420
19225
  # @param [String] filter
19421
- # Sets a filter `expression` for filtering listed resources. Your `expression`
19422
- # must be in the format: field_name comparison_string literal_string.
19423
- # The field_name is the name of the field you want to compare. Only atomic field
19424
- # types are supported (string, number, boolean). The comparison_string must be
19425
- # either eq (equals) or ne (not equals). The literal_string is the string value
19426
- # to filter to. The literal value must be valid for the type of field you are
19427
- # filtering by (string, number, boolean). For string fields, the literal value
19428
- # is interpreted as a regular expression using RE2 syntax. The literal value
19429
- # must match the entire field.
19430
- # For example, to filter for instances that do not have a name of example-
19431
- # instance, you would use name ne example-instance.
19432
- # You can filter on nested fields. For example, you could filter on instances
19433
- # that have set the scheduling.automaticRestart field to true. Use filtering on
19434
- # nested fields to take advantage of labels to organize and search for results
19435
- # based on label values.
19226
+ # A filter expression that filters resources listed in the response. The
19227
+ # expression must specify the field name, a comparison operator, and the value
19228
+ # that you want to use for filtering. The value must be a string, a number, or a
19229
+ # boolean. The comparison operator must be either =, !=, >, or <.
19230
+ # For example, if you are filtering Compute Engine instances, you can exclude
19231
+ # instances named example-instance by specifying name != example-instance.
19232
+ # You can also filter nested fields. For example, you could specify scheduling.
19233
+ # automaticRestart = false to include instances only if they are not scheduled
19234
+ # for automatic restarts. You can use filtering on nested fields to filter based
19235
+ # on resource labels.
19436
19236
  # To filter on multiple expressions, provide each separate expression within
19437
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
19438
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
19439
- # resources must match all expressions to pass the filters.
19237
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
19238
+ # Intel Skylake"). By default, each expression is an AND expression. However,
19239
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
19240
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
19241
+ # automaticRestart = true).
19440
19242
  # @param [Fixnum] max_results
19441
19243
  # The maximum number of results per page that should be returned. If the number
19442
19244
  # of available results is larger than maxResults, Compute Engine returns a
@@ -19838,25 +19640,22 @@ module Google
19838
19640
  # @param [String] project
19839
19641
  # Project ID for this request.
19840
19642
  # @param [String] filter
19841
- # Sets a filter `expression` for filtering listed resources. Your `expression`
19842
- # must be in the format: field_name comparison_string literal_string.
19843
- # The field_name is the name of the field you want to compare. Only atomic field
19844
- # types are supported (string, number, boolean). The comparison_string must be
19845
- # either eq (equals) or ne (not equals). The literal_string is the string value
19846
- # to filter to. The literal value must be valid for the type of field you are
19847
- # filtering by (string, number, boolean). For string fields, the literal value
19848
- # is interpreted as a regular expression using RE2 syntax. The literal value
19849
- # must match the entire field.
19850
- # For example, to filter for instances that do not have a name of example-
19851
- # instance, you would use name ne example-instance.
19852
- # You can filter on nested fields. For example, you could filter on instances
19853
- # that have set the scheduling.automaticRestart field to true. Use filtering on
19854
- # nested fields to take advantage of labels to organize and search for results
19855
- # based on label values.
19643
+ # A filter expression that filters resources listed in the response. The
19644
+ # expression must specify the field name, a comparison operator, and the value
19645
+ # that you want to use for filtering. The value must be a string, a number, or a
19646
+ # boolean. The comparison operator must be either =, !=, >, or <.
19647
+ # For example, if you are filtering Compute Engine instances, you can exclude
19648
+ # instances named example-instance by specifying name != example-instance.
19649
+ # You can also filter nested fields. For example, you could specify scheduling.
19650
+ # automaticRestart = false to include instances only if they are not scheduled
19651
+ # for automatic restarts. You can use filtering on nested fields to filter based
19652
+ # on resource labels.
19856
19653
  # To filter on multiple expressions, provide each separate expression within
19857
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
19858
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
19859
- # resources must match all expressions to pass the filters.
19654
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
19655
+ # Intel Skylake"). By default, each expression is an AND expression. However,
19656
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
19657
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
19658
+ # automaticRestart = true).
19860
19659
  # @param [Fixnum] max_results
19861
19660
  # The maximum number of results per page that should be returned. If the number
19862
19661
  # of available results is larger than maxResults, Compute Engine returns a
@@ -20140,6 +19939,8 @@ module Google
20140
19939
  # accidentally creating duplicate commitments.
20141
19940
  # The request ID must be a valid UUID with the exception that zero UUID is not
20142
19941
  # supported (00000000-0000-0000-0000-000000000000).
19942
+ # @param [Boolean] validate_only
19943
+ # If true, the request will not be committed.
20143
19944
  # @param [String] fields
20144
19945
  # Selector specifying which fields to include in a partial response.
20145
19946
  # @param [String] quota_user
@@ -20161,7 +19962,7 @@ module Google
20161
19962
  # @raise [Google::Apis::ServerError] An error occurred on the server and the request can be retried
20162
19963
  # @raise [Google::Apis::ClientError] The request is invalid and should not be retried without modification
20163
19964
  # @raise [Google::Apis::AuthorizationError] Authorization is required
20164
- def insert_security_policy(project, security_policy_object = nil, request_id: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block)
19965
+ def insert_security_policy(project, security_policy_object = nil, request_id: nil, validate_only: nil, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block)
20165
19966
  command = make_simple_command(:post, '{project}/global/securityPolicies', options)
20166
19967
  command.request_representation = Google::Apis::ComputeAlpha::SecurityPolicy::Representation
20167
19968
  command.request_object = security_policy_object
@@ -20169,6 +19970,7 @@ module Google
20169
19970
  command.response_class = Google::Apis::ComputeAlpha::Operation
20170
19971
  command.params['project'] = project unless project.nil?
20171
19972
  command.query['requestId'] = request_id unless request_id.nil?
19973
+ command.query['validateOnly'] = validate_only unless validate_only.nil?
20172
19974
  command.query['fields'] = fields unless fields.nil?
20173
19975
  command.query['quotaUser'] = quota_user unless quota_user.nil?
20174
19976
  command.query['userIp'] = user_ip unless user_ip.nil?
@@ -20179,25 +19981,22 @@ module Google
20179
19981
  # @param [String] project
20180
19982
  # Project ID for this request.
20181
19983
  # @param [String] filter
20182
- # Sets a filter `expression` for filtering listed resources. Your `expression`
20183
- # must be in the format: field_name comparison_string literal_string.
20184
- # The field_name is the name of the field you want to compare. Only atomic field
20185
- # types are supported (string, number, boolean). The comparison_string must be
20186
- # either eq (equals) or ne (not equals). The literal_string is the string value
20187
- # to filter to. The literal value must be valid for the type of field you are
20188
- # filtering by (string, number, boolean). For string fields, the literal value
20189
- # is interpreted as a regular expression using RE2 syntax. The literal value
20190
- # must match the entire field.
20191
- # For example, to filter for instances that do not have a name of example-
20192
- # instance, you would use name ne example-instance.
20193
- # You can filter on nested fields. For example, you could filter on instances
20194
- # that have set the scheduling.automaticRestart field to true. Use filtering on
20195
- # nested fields to take advantage of labels to organize and search for results
20196
- # based on label values.
19984
+ # A filter expression that filters resources listed in the response. The
19985
+ # expression must specify the field name, a comparison operator, and the value
19986
+ # that you want to use for filtering. The value must be a string, a number, or a
19987
+ # boolean. The comparison operator must be either =, !=, >, or <.
19988
+ # For example, if you are filtering Compute Engine instances, you can exclude
19989
+ # instances named example-instance by specifying name != example-instance.
19990
+ # You can also filter nested fields. For example, you could specify scheduling.
19991
+ # automaticRestart = false to include instances only if they are not scheduled
19992
+ # for automatic restarts. You can use filtering on nested fields to filter based
19993
+ # on resource labels.
20197
19994
  # To filter on multiple expressions, provide each separate expression within
20198
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
20199
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
20200
- # resources must match all expressions to pass the filters.
19995
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
19996
+ # Intel Skylake"). By default, each expression is an AND expression. However,
19997
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
19998
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
19999
+ # automaticRestart = true).
20201
20000
  # @param [Fixnum] max_results
20202
20001
  # The maximum number of results per page that should be returned. If the number
20203
20002
  # of available results is larger than maxResults, Compute Engine returns a
@@ -20570,25 +20369,22 @@ module Google
20570
20369
  # @param [String] project
20571
20370
  # Project ID for this request.
20572
20371
  # @param [String] filter
20573
- # Sets a filter `expression` for filtering listed resources. Your `expression`
20574
- # must be in the format: field_name comparison_string literal_string.
20575
- # The field_name is the name of the field you want to compare. Only atomic field
20576
- # types are supported (string, number, boolean). The comparison_string must be
20577
- # either eq (equals) or ne (not equals). The literal_string is the string value
20578
- # to filter to. The literal value must be valid for the type of field you are
20579
- # filtering by (string, number, boolean). For string fields, the literal value
20580
- # is interpreted as a regular expression using RE2 syntax. The literal value
20581
- # must match the entire field.
20582
- # For example, to filter for instances that do not have a name of example-
20583
- # instance, you would use name ne example-instance.
20584
- # You can filter on nested fields. For example, you could filter on instances
20585
- # that have set the scheduling.automaticRestart field to true. Use filtering on
20586
- # nested fields to take advantage of labels to organize and search for results
20587
- # based on label values.
20372
+ # A filter expression that filters resources listed in the response. The
20373
+ # expression must specify the field name, a comparison operator, and the value
20374
+ # that you want to use for filtering. The value must be a string, a number, or a
20375
+ # boolean. The comparison operator must be either =, !=, >, or <.
20376
+ # For example, if you are filtering Compute Engine instances, you can exclude
20377
+ # instances named example-instance by specifying name != example-instance.
20378
+ # You can also filter nested fields. For example, you could specify scheduling.
20379
+ # automaticRestart = false to include instances only if they are not scheduled
20380
+ # for automatic restarts. You can use filtering on nested fields to filter based
20381
+ # on resource labels.
20588
20382
  # To filter on multiple expressions, provide each separate expression within
20589
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
20590
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
20591
- # resources must match all expressions to pass the filters.
20383
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
20384
+ # Intel Skylake"). By default, each expression is an AND expression. However,
20385
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
20386
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
20387
+ # automaticRestart = true).
20592
20388
  # @param [Fixnum] max_results
20593
20389
  # The maximum number of results per page that should be returned. If the number
20594
20390
  # of available results is larger than maxResults, Compute Engine returns a
@@ -20912,25 +20708,22 @@ module Google
20912
20708
  # @param [String] project
20913
20709
  # Project ID for this request.
20914
20710
  # @param [String] filter
20915
- # Sets a filter `expression` for filtering listed resources. Your `expression`
20916
- # must be in the format: field_name comparison_string literal_string.
20917
- # The field_name is the name of the field you want to compare. Only atomic field
20918
- # types are supported (string, number, boolean). The comparison_string must be
20919
- # either eq (equals) or ne (not equals). The literal_string is the string value
20920
- # to filter to. The literal value must be valid for the type of field you are
20921
- # filtering by (string, number, boolean). For string fields, the literal value
20922
- # is interpreted as a regular expression using RE2 syntax. The literal value
20923
- # must match the entire field.
20924
- # For example, to filter for instances that do not have a name of example-
20925
- # instance, you would use name ne example-instance.
20926
- # You can filter on nested fields. For example, you could filter on instances
20927
- # that have set the scheduling.automaticRestart field to true. Use filtering on
20928
- # nested fields to take advantage of labels to organize and search for results
20929
- # based on label values.
20711
+ # A filter expression that filters resources listed in the response. The
20712
+ # expression must specify the field name, a comparison operator, and the value
20713
+ # that you want to use for filtering. The value must be a string, a number, or a
20714
+ # boolean. The comparison operator must be either =, !=, >, or <.
20715
+ # For example, if you are filtering Compute Engine instances, you can exclude
20716
+ # instances named example-instance by specifying name != example-instance.
20717
+ # You can also filter nested fields. For example, you could specify scheduling.
20718
+ # automaticRestart = false to include instances only if they are not scheduled
20719
+ # for automatic restarts. You can use filtering on nested fields to filter based
20720
+ # on resource labels.
20930
20721
  # To filter on multiple expressions, provide each separate expression within
20931
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
20932
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
20933
- # resources must match all expressions to pass the filters.
20722
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
20723
+ # Intel Skylake"). By default, each expression is an AND expression. However,
20724
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
20725
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
20726
+ # automaticRestart = true).
20934
20727
  # @param [Fixnum] max_results
20935
20728
  # The maximum number of results per page that should be returned. If the number
20936
20729
  # of available results is larger than maxResults, Compute Engine returns a
@@ -21171,25 +20964,22 @@ module Google
21171
20964
  # @param [String] project
21172
20965
  # Project ID for this request.
21173
20966
  # @param [String] filter
21174
- # Sets a filter `expression` for filtering listed resources. Your `expression`
21175
- # must be in the format: field_name comparison_string literal_string.
21176
- # The field_name is the name of the field you want to compare. Only atomic field
21177
- # types are supported (string, number, boolean). The comparison_string must be
21178
- # either eq (equals) or ne (not equals). The literal_string is the string value
21179
- # to filter to. The literal value must be valid for the type of field you are
21180
- # filtering by (string, number, boolean). For string fields, the literal value
21181
- # is interpreted as a regular expression using RE2 syntax. The literal value
21182
- # must match the entire field.
21183
- # For example, to filter for instances that do not have a name of example-
21184
- # instance, you would use name ne example-instance.
21185
- # You can filter on nested fields. For example, you could filter on instances
21186
- # that have set the scheduling.automaticRestart field to true. Use filtering on
21187
- # nested fields to take advantage of labels to organize and search for results
21188
- # based on label values.
20967
+ # A filter expression that filters resources listed in the response. The
20968
+ # expression must specify the field name, a comparison operator, and the value
20969
+ # that you want to use for filtering. The value must be a string, a number, or a
20970
+ # boolean. The comparison operator must be either =, !=, >, or <.
20971
+ # For example, if you are filtering Compute Engine instances, you can exclude
20972
+ # instances named example-instance by specifying name != example-instance.
20973
+ # You can also filter nested fields. For example, you could specify scheduling.
20974
+ # automaticRestart = false to include instances only if they are not scheduled
20975
+ # for automatic restarts. You can use filtering on nested fields to filter based
20976
+ # on resource labels.
21189
20977
  # To filter on multiple expressions, provide each separate expression within
21190
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
21191
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
21192
- # resources must match all expressions to pass the filters.
20978
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
20979
+ # Intel Skylake"). By default, each expression is an AND expression. However,
20980
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
20981
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
20982
+ # automaticRestart = true).
21193
20983
  # @param [Fixnum] max_results
21194
20984
  # The maximum number of results per page that should be returned. If the number
21195
20985
  # of available results is larger than maxResults, Compute Engine returns a
@@ -21248,25 +21038,22 @@ module Google
21248
21038
  # @param [String] project
21249
21039
  # Project ID for this request.
21250
21040
  # @param [String] filter
21251
- # Sets a filter `expression` for filtering listed resources. Your `expression`
21252
- # must be in the format: field_name comparison_string literal_string.
21253
- # The field_name is the name of the field you want to compare. Only atomic field
21254
- # types are supported (string, number, boolean). The comparison_string must be
21255
- # either eq (equals) or ne (not equals). The literal_string is the string value
21256
- # to filter to. The literal value must be valid for the type of field you are
21257
- # filtering by (string, number, boolean). For string fields, the literal value
21258
- # is interpreted as a regular expression using RE2 syntax. The literal value
21259
- # must match the entire field.
21260
- # For example, to filter for instances that do not have a name of example-
21261
- # instance, you would use name ne example-instance.
21262
- # You can filter on nested fields. For example, you could filter on instances
21263
- # that have set the scheduling.automaticRestart field to true. Use filtering on
21264
- # nested fields to take advantage of labels to organize and search for results
21265
- # based on label values.
21041
+ # A filter expression that filters resources listed in the response. The
21042
+ # expression must specify the field name, a comparison operator, and the value
21043
+ # that you want to use for filtering. The value must be a string, a number, or a
21044
+ # boolean. The comparison operator must be either =, !=, >, or <.
21045
+ # For example, if you are filtering Compute Engine instances, you can exclude
21046
+ # instances named example-instance by specifying name != example-instance.
21047
+ # You can also filter nested fields. For example, you could specify scheduling.
21048
+ # automaticRestart = false to include instances only if they are not scheduled
21049
+ # for automatic restarts. You can use filtering on nested fields to filter based
21050
+ # on resource labels.
21266
21051
  # To filter on multiple expressions, provide each separate expression within
21267
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
21268
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
21269
- # resources must match all expressions to pass the filters.
21052
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
21053
+ # Intel Skylake"). By default, each expression is an AND expression. However,
21054
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
21055
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
21056
+ # automaticRestart = true).
21270
21057
  # @param [Fixnum] max_results
21271
21058
  # The maximum number of results per page that should be returned. If the number
21272
21059
  # of available results is larger than maxResults, Compute Engine returns a
@@ -21419,25 +21206,22 @@ module Google
21419
21206
  # @param [String] project
21420
21207
  # Project ID for this request.
21421
21208
  # @param [String] filter
21422
- # Sets a filter `expression` for filtering listed resources. Your `expression`
21423
- # must be in the format: field_name comparison_string literal_string.
21424
- # The field_name is the name of the field you want to compare. Only atomic field
21425
- # types are supported (string, number, boolean). The comparison_string must be
21426
- # either eq (equals) or ne (not equals). The literal_string is the string value
21427
- # to filter to. The literal value must be valid for the type of field you are
21428
- # filtering by (string, number, boolean). For string fields, the literal value
21429
- # is interpreted as a regular expression using RE2 syntax. The literal value
21430
- # must match the entire field.
21431
- # For example, to filter for instances that do not have a name of example-
21432
- # instance, you would use name ne example-instance.
21433
- # You can filter on nested fields. For example, you could filter on instances
21434
- # that have set the scheduling.automaticRestart field to true. Use filtering on
21435
- # nested fields to take advantage of labels to organize and search for results
21436
- # based on label values.
21209
+ # A filter expression that filters resources listed in the response. The
21210
+ # expression must specify the field name, a comparison operator, and the value
21211
+ # that you want to use for filtering. The value must be a string, a number, or a
21212
+ # boolean. The comparison operator must be either =, !=, >, or <.
21213
+ # For example, if you are filtering Compute Engine instances, you can exclude
21214
+ # instances named example-instance by specifying name != example-instance.
21215
+ # You can also filter nested fields. For example, you could specify scheduling.
21216
+ # automaticRestart = false to include instances only if they are not scheduled
21217
+ # for automatic restarts. You can use filtering on nested fields to filter based
21218
+ # on resource labels.
21437
21219
  # To filter on multiple expressions, provide each separate expression within
21438
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
21439
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
21440
- # resources must match all expressions to pass the filters.
21220
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
21221
+ # Intel Skylake"). By default, each expression is an AND expression. However,
21222
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
21223
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
21224
+ # automaticRestart = true).
21441
21225
  # @param [Fixnum] max_results
21442
21226
  # The maximum number of results per page that should be returned. If the number
21443
21227
  # of available results is larger than maxResults, Compute Engine returns a
@@ -21744,25 +21528,22 @@ module Google
21744
21528
  # @param [String] region
21745
21529
  # Name of the region scoping this request.
21746
21530
  # @param [String] filter
21747
- # Sets a filter `expression` for filtering listed resources. Your `expression`
21748
- # must be in the format: field_name comparison_string literal_string.
21749
- # The field_name is the name of the field you want to compare. Only atomic field
21750
- # types are supported (string, number, boolean). The comparison_string must be
21751
- # either eq (equals) or ne (not equals). The literal_string is the string value
21752
- # to filter to. The literal value must be valid for the type of field you are
21753
- # filtering by (string, number, boolean). For string fields, the literal value
21754
- # is interpreted as a regular expression using RE2 syntax. The literal value
21755
- # must match the entire field.
21756
- # For example, to filter for instances that do not have a name of example-
21757
- # instance, you would use name ne example-instance.
21758
- # You can filter on nested fields. For example, you could filter on instances
21759
- # that have set the scheduling.automaticRestart field to true. Use filtering on
21760
- # nested fields to take advantage of labels to organize and search for results
21761
- # based on label values.
21531
+ # A filter expression that filters resources listed in the response. The
21532
+ # expression must specify the field name, a comparison operator, and the value
21533
+ # that you want to use for filtering. The value must be a string, a number, or a
21534
+ # boolean. The comparison operator must be either =, !=, >, or <.
21535
+ # For example, if you are filtering Compute Engine instances, you can exclude
21536
+ # instances named example-instance by specifying name != example-instance.
21537
+ # You can also filter nested fields. For example, you could specify scheduling.
21538
+ # automaticRestart = false to include instances only if they are not scheduled
21539
+ # for automatic restarts. You can use filtering on nested fields to filter based
21540
+ # on resource labels.
21762
21541
  # To filter on multiple expressions, provide each separate expression within
21763
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
21764
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
21765
- # resources must match all expressions to pass the filters.
21542
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
21543
+ # Intel Skylake"). By default, each expression is an AND expression. However,
21544
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
21545
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
21546
+ # automaticRestart = true).
21766
21547
  # @param [Fixnum] max_results
21767
21548
  # The maximum number of results per page that should be returned. If the number
21768
21549
  # of available results is larger than maxResults, Compute Engine returns a
@@ -21821,25 +21602,22 @@ module Google
21821
21602
  # @param [String] project
21822
21603
  # Project ID for this request.
21823
21604
  # @param [String] filter
21824
- # Sets a filter `expression` for filtering listed resources. Your `expression`
21825
- # must be in the format: field_name comparison_string literal_string.
21826
- # The field_name is the name of the field you want to compare. Only atomic field
21827
- # types are supported (string, number, boolean). The comparison_string must be
21828
- # either eq (equals) or ne (not equals). The literal_string is the string value
21829
- # to filter to. The literal value must be valid for the type of field you are
21830
- # filtering by (string, number, boolean). For string fields, the literal value
21831
- # is interpreted as a regular expression using RE2 syntax. The literal value
21832
- # must match the entire field.
21833
- # For example, to filter for instances that do not have a name of example-
21834
- # instance, you would use name ne example-instance.
21835
- # You can filter on nested fields. For example, you could filter on instances
21836
- # that have set the scheduling.automaticRestart field to true. Use filtering on
21837
- # nested fields to take advantage of labels to organize and search for results
21838
- # based on label values.
21605
+ # A filter expression that filters resources listed in the response. The
21606
+ # expression must specify the field name, a comparison operator, and the value
21607
+ # that you want to use for filtering. The value must be a string, a number, or a
21608
+ # boolean. The comparison operator must be either =, !=, >, or <.
21609
+ # For example, if you are filtering Compute Engine instances, you can exclude
21610
+ # instances named example-instance by specifying name != example-instance.
21611
+ # You can also filter nested fields. For example, you could specify scheduling.
21612
+ # automaticRestart = false to include instances only if they are not scheduled
21613
+ # for automatic restarts. You can use filtering on nested fields to filter based
21614
+ # on resource labels.
21839
21615
  # To filter on multiple expressions, provide each separate expression within
21840
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
21841
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
21842
- # resources must match all expressions to pass the filters.
21616
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
21617
+ # Intel Skylake"). By default, each expression is an AND expression. However,
21618
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
21619
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
21620
+ # automaticRestart = true).
21843
21621
  # @param [Fixnum] max_results
21844
21622
  # The maximum number of results per page that should be returned. If the number
21845
21623
  # of available results is larger than maxResults, Compute Engine returns a
@@ -22244,25 +22022,22 @@ module Google
22244
22022
  # @param [String] project
22245
22023
  # Project ID for this request.
22246
22024
  # @param [String] filter
22247
- # Sets a filter `expression` for filtering listed resources. Your `expression`
22248
- # must be in the format: field_name comparison_string literal_string.
22249
- # The field_name is the name of the field you want to compare. Only atomic field
22250
- # types are supported (string, number, boolean). The comparison_string must be
22251
- # either eq (equals) or ne (not equals). The literal_string is the string value
22252
- # to filter to. The literal value must be valid for the type of field you are
22253
- # filtering by (string, number, boolean). For string fields, the literal value
22254
- # is interpreted as a regular expression using RE2 syntax. The literal value
22255
- # must match the entire field.
22256
- # For example, to filter for instances that do not have a name of example-
22257
- # instance, you would use name ne example-instance.
22258
- # You can filter on nested fields. For example, you could filter on instances
22259
- # that have set the scheduling.automaticRestart field to true. Use filtering on
22260
- # nested fields to take advantage of labels to organize and search for results
22261
- # based on label values.
22025
+ # A filter expression that filters resources listed in the response. The
22026
+ # expression must specify the field name, a comparison operator, and the value
22027
+ # that you want to use for filtering. The value must be a string, a number, or a
22028
+ # boolean. The comparison operator must be either =, !=, >, or <.
22029
+ # For example, if you are filtering Compute Engine instances, you can exclude
22030
+ # instances named example-instance by specifying name != example-instance.
22031
+ # You can also filter nested fields. For example, you could specify scheduling.
22032
+ # automaticRestart = false to include instances only if they are not scheduled
22033
+ # for automatic restarts. You can use filtering on nested fields to filter based
22034
+ # on resource labels.
22262
22035
  # To filter on multiple expressions, provide each separate expression within
22263
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
22264
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
22265
- # resources must match all expressions to pass the filters.
22036
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
22037
+ # Intel Skylake"). By default, each expression is an AND expression. However,
22038
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
22039
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
22040
+ # automaticRestart = true).
22266
22041
  # @param [Fixnum] max_results
22267
22042
  # The maximum number of results per page that should be returned. If the number
22268
22043
  # of available results is larger than maxResults, Compute Engine returns a
@@ -22555,25 +22330,22 @@ module Google
22555
22330
  # @param [String] project
22556
22331
  # Project ID for this request.
22557
22332
  # @param [String] filter
22558
- # Sets a filter `expression` for filtering listed resources. Your `expression`
22559
- # must be in the format: field_name comparison_string literal_string.
22560
- # The field_name is the name of the field you want to compare. Only atomic field
22561
- # types are supported (string, number, boolean). The comparison_string must be
22562
- # either eq (equals) or ne (not equals). The literal_string is the string value
22563
- # to filter to. The literal value must be valid for the type of field you are
22564
- # filtering by (string, number, boolean). For string fields, the literal value
22565
- # is interpreted as a regular expression using RE2 syntax. The literal value
22566
- # must match the entire field.
22567
- # For example, to filter for instances that do not have a name of example-
22568
- # instance, you would use name ne example-instance.
22569
- # You can filter on nested fields. For example, you could filter on instances
22570
- # that have set the scheduling.automaticRestart field to true. Use filtering on
22571
- # nested fields to take advantage of labels to organize and search for results
22572
- # based on label values.
22333
+ # A filter expression that filters resources listed in the response. The
22334
+ # expression must specify the field name, a comparison operator, and the value
22335
+ # that you want to use for filtering. The value must be a string, a number, or a
22336
+ # boolean. The comparison operator must be either =, !=, >, or <.
22337
+ # For example, if you are filtering Compute Engine instances, you can exclude
22338
+ # instances named example-instance by specifying name != example-instance.
22339
+ # You can also filter nested fields. For example, you could specify scheduling.
22340
+ # automaticRestart = false to include instances only if they are not scheduled
22341
+ # for automatic restarts. You can use filtering on nested fields to filter based
22342
+ # on resource labels.
22573
22343
  # To filter on multiple expressions, provide each separate expression within
22574
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
22575
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
22576
- # resources must match all expressions to pass the filters.
22344
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
22345
+ # Intel Skylake"). By default, each expression is an AND expression. However,
22346
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
22347
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
22348
+ # automaticRestart = true).
22577
22349
  # @param [Fixnum] max_results
22578
22350
  # The maximum number of results per page that should be returned. If the number
22579
22351
  # of available results is larger than maxResults, Compute Engine returns a
@@ -22889,25 +22661,22 @@ module Google
22889
22661
  # @param [String] project
22890
22662
  # Project ID for this request.
22891
22663
  # @param [String] filter
22892
- # Sets a filter `expression` for filtering listed resources. Your `expression`
22893
- # must be in the format: field_name comparison_string literal_string.
22894
- # The field_name is the name of the field you want to compare. Only atomic field
22895
- # types are supported (string, number, boolean). The comparison_string must be
22896
- # either eq (equals) or ne (not equals). The literal_string is the string value
22897
- # to filter to. The literal value must be valid for the type of field you are
22898
- # filtering by (string, number, boolean). For string fields, the literal value
22899
- # is interpreted as a regular expression using RE2 syntax. The literal value
22900
- # must match the entire field.
22901
- # For example, to filter for instances that do not have a name of example-
22902
- # instance, you would use name ne example-instance.
22903
- # You can filter on nested fields. For example, you could filter on instances
22904
- # that have set the scheduling.automaticRestart field to true. Use filtering on
22905
- # nested fields to take advantage of labels to organize and search for results
22906
- # based on label values.
22664
+ # A filter expression that filters resources listed in the response. The
22665
+ # expression must specify the field name, a comparison operator, and the value
22666
+ # that you want to use for filtering. The value must be a string, a number, or a
22667
+ # boolean. The comparison operator must be either =, !=, >, or <.
22668
+ # For example, if you are filtering Compute Engine instances, you can exclude
22669
+ # instances named example-instance by specifying name != example-instance.
22670
+ # You can also filter nested fields. For example, you could specify scheduling.
22671
+ # automaticRestart = false to include instances only if they are not scheduled
22672
+ # for automatic restarts. You can use filtering on nested fields to filter based
22673
+ # on resource labels.
22907
22674
  # To filter on multiple expressions, provide each separate expression within
22908
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
22909
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
22910
- # resources must match all expressions to pass the filters.
22675
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
22676
+ # Intel Skylake"). By default, each expression is an AND expression. However,
22677
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
22678
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
22679
+ # automaticRestart = true).
22911
22680
  # @param [Fixnum] max_results
22912
22681
  # The maximum number of results per page that should be returned. If the number
22913
22682
  # of available results is larger than maxResults, Compute Engine returns a
@@ -23117,25 +22886,22 @@ module Google
23117
22886
  # @param [String] zone
23118
22887
  # Name of the zone scoping this request.
23119
22888
  # @param [String] filter
23120
- # Sets a filter `expression` for filtering listed resources. Your `expression`
23121
- # must be in the format: field_name comparison_string literal_string.
23122
- # The field_name is the name of the field you want to compare. Only atomic field
23123
- # types are supported (string, number, boolean). The comparison_string must be
23124
- # either eq (equals) or ne (not equals). The literal_string is the string value
23125
- # to filter to. The literal value must be valid for the type of field you are
23126
- # filtering by (string, number, boolean). For string fields, the literal value
23127
- # is interpreted as a regular expression using RE2 syntax. The literal value
23128
- # must match the entire field.
23129
- # For example, to filter for instances that do not have a name of example-
23130
- # instance, you would use name ne example-instance.
23131
- # You can filter on nested fields. For example, you could filter on instances
23132
- # that have set the scheduling.automaticRestart field to true. Use filtering on
23133
- # nested fields to take advantage of labels to organize and search for results
23134
- # based on label values.
22889
+ # A filter expression that filters resources listed in the response. The
22890
+ # expression must specify the field name, a comparison operator, and the value
22891
+ # that you want to use for filtering. The value must be a string, a number, or a
22892
+ # boolean. The comparison operator must be either =, !=, >, or <.
22893
+ # For example, if you are filtering Compute Engine instances, you can exclude
22894
+ # instances named example-instance by specifying name != example-instance.
22895
+ # You can also filter nested fields. For example, you could specify scheduling.
22896
+ # automaticRestart = false to include instances only if they are not scheduled
22897
+ # for automatic restarts. You can use filtering on nested fields to filter based
22898
+ # on resource labels.
23135
22899
  # To filter on multiple expressions, provide each separate expression within
23136
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
23137
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
23138
- # resources must match all expressions to pass the filters.
22900
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
22901
+ # Intel Skylake"). By default, each expression is an AND expression. However,
22902
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
22903
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
22904
+ # automaticRestart = true).
23139
22905
  # @param [Fixnum] max_results
23140
22906
  # The maximum number of results per page that should be returned. If the number
23141
22907
  # of available results is larger than maxResults, Compute Engine returns a
@@ -23350,25 +23116,22 @@ module Google
23350
23116
  # @param [String] project
23351
23117
  # Project ID for this request.
23352
23118
  # @param [String] filter
23353
- # Sets a filter `expression` for filtering listed resources. Your `expression`
23354
- # must be in the format: field_name comparison_string literal_string.
23355
- # The field_name is the name of the field you want to compare. Only atomic field
23356
- # types are supported (string, number, boolean). The comparison_string must be
23357
- # either eq (equals) or ne (not equals). The literal_string is the string value
23358
- # to filter to. The literal value must be valid for the type of field you are
23359
- # filtering by (string, number, boolean). For string fields, the literal value
23360
- # is interpreted as a regular expression using RE2 syntax. The literal value
23361
- # must match the entire field.
23362
- # For example, to filter for instances that do not have a name of example-
23363
- # instance, you would use name ne example-instance.
23364
- # You can filter on nested fields. For example, you could filter on instances
23365
- # that have set the scheduling.automaticRestart field to true. Use filtering on
23366
- # nested fields to take advantage of labels to organize and search for results
23367
- # based on label values.
23119
+ # A filter expression that filters resources listed in the response. The
23120
+ # expression must specify the field name, a comparison operator, and the value
23121
+ # that you want to use for filtering. The value must be a string, a number, or a
23122
+ # boolean. The comparison operator must be either =, !=, >, or <.
23123
+ # For example, if you are filtering Compute Engine instances, you can exclude
23124
+ # instances named example-instance by specifying name != example-instance.
23125
+ # You can also filter nested fields. For example, you could specify scheduling.
23126
+ # automaticRestart = false to include instances only if they are not scheduled
23127
+ # for automatic restarts. You can use filtering on nested fields to filter based
23128
+ # on resource labels.
23368
23129
  # To filter on multiple expressions, provide each separate expression within
23369
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
23370
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
23371
- # resources must match all expressions to pass the filters.
23130
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
23131
+ # Intel Skylake"). By default, each expression is an AND expression. However,
23132
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
23133
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
23134
+ # automaticRestart = true).
23372
23135
  # @param [Fixnum] max_results
23373
23136
  # The maximum number of results per page that should be returned. If the number
23374
23137
  # of available results is larger than maxResults, Compute Engine returns a
@@ -23622,25 +23385,22 @@ module Google
23622
23385
  # @param [String] region
23623
23386
  # Name of the region scoping this request.
23624
23387
  # @param [String] filter
23625
- # Sets a filter `expression` for filtering listed resources. Your `expression`
23626
- # must be in the format: field_name comparison_string literal_string.
23627
- # The field_name is the name of the field you want to compare. Only atomic field
23628
- # types are supported (string, number, boolean). The comparison_string must be
23629
- # either eq (equals) or ne (not equals). The literal_string is the string value
23630
- # to filter to. The literal value must be valid for the type of field you are
23631
- # filtering by (string, number, boolean). For string fields, the literal value
23632
- # is interpreted as a regular expression using RE2 syntax. The literal value
23633
- # must match the entire field.
23634
- # For example, to filter for instances that do not have a name of example-
23635
- # instance, you would use name ne example-instance.
23636
- # You can filter on nested fields. For example, you could filter on instances
23637
- # that have set the scheduling.automaticRestart field to true. Use filtering on
23638
- # nested fields to take advantage of labels to organize and search for results
23639
- # based on label values.
23388
+ # A filter expression that filters resources listed in the response. The
23389
+ # expression must specify the field name, a comparison operator, and the value
23390
+ # that you want to use for filtering. The value must be a string, a number, or a
23391
+ # boolean. The comparison operator must be either =, !=, >, or <.
23392
+ # For example, if you are filtering Compute Engine instances, you can exclude
23393
+ # instances named example-instance by specifying name != example-instance.
23394
+ # You can also filter nested fields. For example, you could specify scheduling.
23395
+ # automaticRestart = false to include instances only if they are not scheduled
23396
+ # for automatic restarts. You can use filtering on nested fields to filter based
23397
+ # on resource labels.
23640
23398
  # To filter on multiple expressions, provide each separate expression within
23641
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
23642
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
23643
- # resources must match all expressions to pass the filters.
23399
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
23400
+ # Intel Skylake"). By default, each expression is an AND expression. However,
23401
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
23402
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
23403
+ # automaticRestart = true).
23644
23404
  # @param [Fixnum] max_results
23645
23405
  # The maximum number of results per page that should be returned. If the number
23646
23406
  # of available results is larger than maxResults, Compute Engine returns a
@@ -24055,25 +23815,22 @@ module Google
24055
23815
  # @param [String] project
24056
23816
  # Project ID for this request.
24057
23817
  # @param [String] filter
24058
- # Sets a filter `expression` for filtering listed resources. Your `expression`
24059
- # must be in the format: field_name comparison_string literal_string.
24060
- # The field_name is the name of the field you want to compare. Only atomic field
24061
- # types are supported (string, number, boolean). The comparison_string must be
24062
- # either eq (equals) or ne (not equals). The literal_string is the string value
24063
- # to filter to. The literal value must be valid for the type of field you are
24064
- # filtering by (string, number, boolean). For string fields, the literal value
24065
- # is interpreted as a regular expression using RE2 syntax. The literal value
24066
- # must match the entire field.
24067
- # For example, to filter for instances that do not have a name of example-
24068
- # instance, you would use name ne example-instance.
24069
- # You can filter on nested fields. For example, you could filter on instances
24070
- # that have set the scheduling.automaticRestart field to true. Use filtering on
24071
- # nested fields to take advantage of labels to organize and search for results
24072
- # based on label values.
23818
+ # A filter expression that filters resources listed in the response. The
23819
+ # expression must specify the field name, a comparison operator, and the value
23820
+ # that you want to use for filtering. The value must be a string, a number, or a
23821
+ # boolean. The comparison operator must be either =, !=, >, or <.
23822
+ # For example, if you are filtering Compute Engine instances, you can exclude
23823
+ # instances named example-instance by specifying name != example-instance.
23824
+ # You can also filter nested fields. For example, you could specify scheduling.
23825
+ # automaticRestart = false to include instances only if they are not scheduled
23826
+ # for automatic restarts. You can use filtering on nested fields to filter based
23827
+ # on resource labels.
24073
23828
  # To filter on multiple expressions, provide each separate expression within
24074
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
24075
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
24076
- # resources must match all expressions to pass the filters.
23829
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
23830
+ # Intel Skylake"). By default, each expression is an AND expression. However,
23831
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
23832
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
23833
+ # automaticRestart = true).
24077
23834
  # @param [Fixnum] max_results
24078
23835
  # The maximum number of results per page that should be returned. If the number
24079
23836
  # of available results is larger than maxResults, Compute Engine returns a
@@ -24529,25 +24286,22 @@ module Google
24529
24286
  # @param [String] project
24530
24287
  # Project ID for this request.
24531
24288
  # @param [String] filter
24532
- # Sets a filter `expression` for filtering listed resources. Your `expression`
24533
- # must be in the format: field_name comparison_string literal_string.
24534
- # The field_name is the name of the field you want to compare. Only atomic field
24535
- # types are supported (string, number, boolean). The comparison_string must be
24536
- # either eq (equals) or ne (not equals). The literal_string is the string value
24537
- # to filter to. The literal value must be valid for the type of field you are
24538
- # filtering by (string, number, boolean). For string fields, the literal value
24539
- # is interpreted as a regular expression using RE2 syntax. The literal value
24540
- # must match the entire field.
24541
- # For example, to filter for instances that do not have a name of example-
24542
- # instance, you would use name ne example-instance.
24543
- # You can filter on nested fields. For example, you could filter on instances
24544
- # that have set the scheduling.automaticRestart field to true. Use filtering on
24545
- # nested fields to take advantage of labels to organize and search for results
24546
- # based on label values.
24289
+ # A filter expression that filters resources listed in the response. The
24290
+ # expression must specify the field name, a comparison operator, and the value
24291
+ # that you want to use for filtering. The value must be a string, a number, or a
24292
+ # boolean. The comparison operator must be either =, !=, >, or <.
24293
+ # For example, if you are filtering Compute Engine instances, you can exclude
24294
+ # instances named example-instance by specifying name != example-instance.
24295
+ # You can also filter nested fields. For example, you could specify scheduling.
24296
+ # automaticRestart = false to include instances only if they are not scheduled
24297
+ # for automatic restarts. You can use filtering on nested fields to filter based
24298
+ # on resource labels.
24547
24299
  # To filter on multiple expressions, provide each separate expression within
24548
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
24549
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
24550
- # resources must match all expressions to pass the filters.
24300
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
24301
+ # Intel Skylake"). By default, each expression is an AND expression. However,
24302
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
24303
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
24304
+ # automaticRestart = true).
24551
24305
  # @param [Fixnum] max_results
24552
24306
  # The maximum number of results per page that should be returned. If the number
24553
24307
  # of available results is larger than maxResults, Compute Engine returns a
@@ -24752,25 +24506,22 @@ module Google
24752
24506
  # @param [String] project
24753
24507
  # Project ID for this request.
24754
24508
  # @param [String] filter
24755
- # Sets a filter `expression` for filtering listed resources. Your `expression`
24756
- # must be in the format: field_name comparison_string literal_string.
24757
- # The field_name is the name of the field you want to compare. Only atomic field
24758
- # types are supported (string, number, boolean). The comparison_string must be
24759
- # either eq (equals) or ne (not equals). The literal_string is the string value
24760
- # to filter to. The literal value must be valid for the type of field you are
24761
- # filtering by (string, number, boolean). For string fields, the literal value
24762
- # is interpreted as a regular expression using RE2 syntax. The literal value
24763
- # must match the entire field.
24764
- # For example, to filter for instances that do not have a name of example-
24765
- # instance, you would use name ne example-instance.
24766
- # You can filter on nested fields. For example, you could filter on instances
24767
- # that have set the scheduling.automaticRestart field to true. Use filtering on
24768
- # nested fields to take advantage of labels to organize and search for results
24769
- # based on label values.
24509
+ # A filter expression that filters resources listed in the response. The
24510
+ # expression must specify the field name, a comparison operator, and the value
24511
+ # that you want to use for filtering. The value must be a string, a number, or a
24512
+ # boolean. The comparison operator must be either =, !=, >, or <.
24513
+ # For example, if you are filtering Compute Engine instances, you can exclude
24514
+ # instances named example-instance by specifying name != example-instance.
24515
+ # You can also filter nested fields. For example, you could specify scheduling.
24516
+ # automaticRestart = false to include instances only if they are not scheduled
24517
+ # for automatic restarts. You can use filtering on nested fields to filter based
24518
+ # on resource labels.
24770
24519
  # To filter on multiple expressions, provide each separate expression within
24771
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
24772
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
24773
- # resources must match all expressions to pass the filters.
24520
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
24521
+ # Intel Skylake"). By default, each expression is an AND expression. However,
24522
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
24523
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
24524
+ # automaticRestart = true).
24774
24525
  # @param [Fixnum] max_results
24775
24526
  # The maximum number of results per page that should be returned. If the number
24776
24527
  # of available results is larger than maxResults, Compute Engine returns a
@@ -24980,25 +24731,22 @@ module Google
24980
24731
  # @param [String] region
24981
24732
  # Name of the region for this request.
24982
24733
  # @param [String] filter
24983
- # Sets a filter `expression` for filtering listed resources. Your `expression`
24984
- # must be in the format: field_name comparison_string literal_string.
24985
- # The field_name is the name of the field you want to compare. Only atomic field
24986
- # types are supported (string, number, boolean). The comparison_string must be
24987
- # either eq (equals) or ne (not equals). The literal_string is the string value
24988
- # to filter to. The literal value must be valid for the type of field you are
24989
- # filtering by (string, number, boolean). For string fields, the literal value
24990
- # is interpreted as a regular expression using RE2 syntax. The literal value
24991
- # must match the entire field.
24992
- # For example, to filter for instances that do not have a name of example-
24993
- # instance, you would use name ne example-instance.
24994
- # You can filter on nested fields. For example, you could filter on instances
24995
- # that have set the scheduling.automaticRestart field to true. Use filtering on
24996
- # nested fields to take advantage of labels to organize and search for results
24997
- # based on label values.
24734
+ # A filter expression that filters resources listed in the response. The
24735
+ # expression must specify the field name, a comparison operator, and the value
24736
+ # that you want to use for filtering. The value must be a string, a number, or a
24737
+ # boolean. The comparison operator must be either =, !=, >, or <.
24738
+ # For example, if you are filtering Compute Engine instances, you can exclude
24739
+ # instances named example-instance by specifying name != example-instance.
24740
+ # You can also filter nested fields. For example, you could specify scheduling.
24741
+ # automaticRestart = false to include instances only if they are not scheduled
24742
+ # for automatic restarts. You can use filtering on nested fields to filter based
24743
+ # on resource labels.
24998
24744
  # To filter on multiple expressions, provide each separate expression within
24999
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
25000
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
25001
- # resources must match all expressions to pass the filters.
24745
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
24746
+ # Intel Skylake"). By default, each expression is an AND expression. However,
24747
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
24748
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
24749
+ # automaticRestart = true).
25002
24750
  # @param [Fixnum] max_results
25003
24751
  # The maximum number of results per page that should be returned. If the number
25004
24752
  # of available results is larger than maxResults, Compute Engine returns a
@@ -25352,25 +25100,22 @@ module Google
25352
25100
  # @param [String] project
25353
25101
  # Project ID for this request.
25354
25102
  # @param [String] filter
25355
- # Sets a filter `expression` for filtering listed resources. Your `expression`
25356
- # must be in the format: field_name comparison_string literal_string.
25357
- # The field_name is the name of the field you want to compare. Only atomic field
25358
- # types are supported (string, number, boolean). The comparison_string must be
25359
- # either eq (equals) or ne (not equals). The literal_string is the string value
25360
- # to filter to. The literal value must be valid for the type of field you are
25361
- # filtering by (string, number, boolean). For string fields, the literal value
25362
- # is interpreted as a regular expression using RE2 syntax. The literal value
25363
- # must match the entire field.
25364
- # For example, to filter for instances that do not have a name of example-
25365
- # instance, you would use name ne example-instance.
25366
- # You can filter on nested fields. For example, you could filter on instances
25367
- # that have set the scheduling.automaticRestart field to true. Use filtering on
25368
- # nested fields to take advantage of labels to organize and search for results
25369
- # based on label values.
25103
+ # A filter expression that filters resources listed in the response. The
25104
+ # expression must specify the field name, a comparison operator, and the value
25105
+ # that you want to use for filtering. The value must be a string, a number, or a
25106
+ # boolean. The comparison operator must be either =, !=, >, or <.
25107
+ # For example, if you are filtering Compute Engine instances, you can exclude
25108
+ # instances named example-instance by specifying name != example-instance.
25109
+ # You can also filter nested fields. For example, you could specify scheduling.
25110
+ # automaticRestart = false to include instances only if they are not scheduled
25111
+ # for automatic restarts. You can use filtering on nested fields to filter based
25112
+ # on resource labels.
25370
25113
  # To filter on multiple expressions, provide each separate expression within
25371
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
25372
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
25373
- # resources must match all expressions to pass the filters.
25114
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
25115
+ # Intel Skylake"). By default, each expression is an AND expression. However,
25116
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
25117
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
25118
+ # automaticRestart = true).
25374
25119
  # @param [Fixnum] max_results
25375
25120
  # The maximum number of results per page that should be returned. If the number
25376
25121
  # of available results is larger than maxResults, Compute Engine returns a
@@ -25619,25 +25364,22 @@ module Google
25619
25364
  # @param [String] project
25620
25365
  # Project ID for this request.
25621
25366
  # @param [String] filter
25622
- # Sets a filter `expression` for filtering listed resources. Your `expression`
25623
- # must be in the format: field_name comparison_string literal_string.
25624
- # The field_name is the name of the field you want to compare. Only atomic field
25625
- # types are supported (string, number, boolean). The comparison_string must be
25626
- # either eq (equals) or ne (not equals). The literal_string is the string value
25627
- # to filter to. The literal value must be valid for the type of field you are
25628
- # filtering by (string, number, boolean). For string fields, the literal value
25629
- # is interpreted as a regular expression using RE2 syntax. The literal value
25630
- # must match the entire field.
25631
- # For example, to filter for instances that do not have a name of example-
25632
- # instance, you would use name ne example-instance.
25633
- # You can filter on nested fields. For example, you could filter on instances
25634
- # that have set the scheduling.automaticRestart field to true. Use filtering on
25635
- # nested fields to take advantage of labels to organize and search for results
25636
- # based on label values.
25367
+ # A filter expression that filters resources listed in the response. The
25368
+ # expression must specify the field name, a comparison operator, and the value
25369
+ # that you want to use for filtering. The value must be a string, a number, or a
25370
+ # boolean. The comparison operator must be either =, !=, >, or <.
25371
+ # For example, if you are filtering Compute Engine instances, you can exclude
25372
+ # instances named example-instance by specifying name != example-instance.
25373
+ # You can also filter nested fields. For example, you could specify scheduling.
25374
+ # automaticRestart = false to include instances only if they are not scheduled
25375
+ # for automatic restarts. You can use filtering on nested fields to filter based
25376
+ # on resource labels.
25637
25377
  # To filter on multiple expressions, provide each separate expression within
25638
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
25639
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
25640
- # resources must match all expressions to pass the filters.
25378
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
25379
+ # Intel Skylake"). By default, each expression is an AND expression. However,
25380
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
25381
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
25382
+ # automaticRestart = true).
25641
25383
  # @param [Fixnum] max_results
25642
25384
  # The maximum number of results per page that should be returned. If the number
25643
25385
  # of available results is larger than maxResults, Compute Engine returns a
@@ -25847,25 +25589,22 @@ module Google
25847
25589
  # @param [String] region
25848
25590
  # Name of the region for this request.
25849
25591
  # @param [String] filter
25850
- # Sets a filter `expression` for filtering listed resources. Your `expression`
25851
- # must be in the format: field_name comparison_string literal_string.
25852
- # The field_name is the name of the field you want to compare. Only atomic field
25853
- # types are supported (string, number, boolean). The comparison_string must be
25854
- # either eq (equals) or ne (not equals). The literal_string is the string value
25855
- # to filter to. The literal value must be valid for the type of field you are
25856
- # filtering by (string, number, boolean). For string fields, the literal value
25857
- # is interpreted as a regular expression using RE2 syntax. The literal value
25858
- # must match the entire field.
25859
- # For example, to filter for instances that do not have a name of example-
25860
- # instance, you would use name ne example-instance.
25861
- # You can filter on nested fields. For example, you could filter on instances
25862
- # that have set the scheduling.automaticRestart field to true. Use filtering on
25863
- # nested fields to take advantage of labels to organize and search for results
25864
- # based on label values.
25592
+ # A filter expression that filters resources listed in the response. The
25593
+ # expression must specify the field name, a comparison operator, and the value
25594
+ # that you want to use for filtering. The value must be a string, a number, or a
25595
+ # boolean. The comparison operator must be either =, !=, >, or <.
25596
+ # For example, if you are filtering Compute Engine instances, you can exclude
25597
+ # instances named example-instance by specifying name != example-instance.
25598
+ # You can also filter nested fields. For example, you could specify scheduling.
25599
+ # automaticRestart = false to include instances only if they are not scheduled
25600
+ # for automatic restarts. You can use filtering on nested fields to filter based
25601
+ # on resource labels.
25865
25602
  # To filter on multiple expressions, provide each separate expression within
25866
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
25867
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
25868
- # resources must match all expressions to pass the filters.
25603
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
25604
+ # Intel Skylake"). By default, each expression is an AND expression. However,
25605
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
25606
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
25607
+ # automaticRestart = true).
25869
25608
  # @param [Fixnum] max_results
25870
25609
  # The maximum number of results per page that should be returned. If the number
25871
25610
  # of available results is larger than maxResults, Compute Engine returns a
@@ -26107,25 +25846,22 @@ module Google
26107
25846
  # @param [String] zone
26108
25847
  # Name of the zone for request.
26109
25848
  # @param [String] filter
26110
- # Sets a filter `expression` for filtering listed resources. Your `expression`
26111
- # must be in the format: field_name comparison_string literal_string.
26112
- # The field_name is the name of the field you want to compare. Only atomic field
26113
- # types are supported (string, number, boolean). The comparison_string must be
26114
- # either eq (equals) or ne (not equals). The literal_string is the string value
26115
- # to filter to. The literal value must be valid for the type of field you are
26116
- # filtering by (string, number, boolean). For string fields, the literal value
26117
- # is interpreted as a regular expression using RE2 syntax. The literal value
26118
- # must match the entire field.
26119
- # For example, to filter for instances that do not have a name of example-
26120
- # instance, you would use name ne example-instance.
26121
- # You can filter on nested fields. For example, you could filter on instances
26122
- # that have set the scheduling.automaticRestart field to true. Use filtering on
26123
- # nested fields to take advantage of labels to organize and search for results
26124
- # based on label values.
25849
+ # A filter expression that filters resources listed in the response. The
25850
+ # expression must specify the field name, a comparison operator, and the value
25851
+ # that you want to use for filtering. The value must be a string, a number, or a
25852
+ # boolean. The comparison operator must be either =, !=, >, or <.
25853
+ # For example, if you are filtering Compute Engine instances, you can exclude
25854
+ # instances named example-instance by specifying name != example-instance.
25855
+ # You can also filter nested fields. For example, you could specify scheduling.
25856
+ # automaticRestart = false to include instances only if they are not scheduled
25857
+ # for automatic restarts. You can use filtering on nested fields to filter based
25858
+ # on resource labels.
26125
25859
  # To filter on multiple expressions, provide each separate expression within
26126
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
26127
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
26128
- # resources must match all expressions to pass the filters.
25860
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
25861
+ # Intel Skylake"). By default, each expression is an AND expression. However,
25862
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
25863
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
25864
+ # automaticRestart = true).
26129
25865
  # @param [Fixnum] max_results
26130
25866
  # The maximum number of results per page that should be returned. If the number
26131
25867
  # of available results is larger than maxResults, Compute Engine returns a
@@ -26223,25 +25959,22 @@ module Google
26223
25959
  # @param [String] project
26224
25960
  # Project ID for this request.
26225
25961
  # @param [String] filter
26226
- # Sets a filter `expression` for filtering listed resources. Your `expression`
26227
- # must be in the format: field_name comparison_string literal_string.
26228
- # The field_name is the name of the field you want to compare. Only atomic field
26229
- # types are supported (string, number, boolean). The comparison_string must be
26230
- # either eq (equals) or ne (not equals). The literal_string is the string value
26231
- # to filter to. The literal value must be valid for the type of field you are
26232
- # filtering by (string, number, boolean). For string fields, the literal value
26233
- # is interpreted as a regular expression using RE2 syntax. The literal value
26234
- # must match the entire field.
26235
- # For example, to filter for instances that do not have a name of example-
26236
- # instance, you would use name ne example-instance.
26237
- # You can filter on nested fields. For example, you could filter on instances
26238
- # that have set the scheduling.automaticRestart field to true. Use filtering on
26239
- # nested fields to take advantage of labels to organize and search for results
26240
- # based on label values.
25962
+ # A filter expression that filters resources listed in the response. The
25963
+ # expression must specify the field name, a comparison operator, and the value
25964
+ # that you want to use for filtering. The value must be a string, a number, or a
25965
+ # boolean. The comparison operator must be either =, !=, >, or <.
25966
+ # For example, if you are filtering Compute Engine instances, you can exclude
25967
+ # instances named example-instance by specifying name != example-instance.
25968
+ # You can also filter nested fields. For example, you could specify scheduling.
25969
+ # automaticRestart = false to include instances only if they are not scheduled
25970
+ # for automatic restarts. You can use filtering on nested fields to filter based
25971
+ # on resource labels.
26241
25972
  # To filter on multiple expressions, provide each separate expression within
26242
- # parentheses. For example, (scheduling.automaticRestart eq true) (zone eq us-
26243
- # central1-f). Multiple expressions are treated as AND expressions, meaning that
26244
- # resources must match all expressions to pass the filters.
25973
+ # parentheses. For example, (scheduling.automaticRestart = true) (cpuPlatform = "
25974
+ # Intel Skylake"). By default, each expression is an AND expression. However,
25975
+ # you can include AND and OR expressions explicitly. For example, (cpuPlatform =
25976
+ # "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
25977
+ # automaticRestart = true).
26245
25978
  # @param [Fixnum] max_results
26246
25979
  # The maximum number of results per page that should be returned. If the number
26247
25980
  # of available results is larger than maxResults, Compute Engine returns a