git.iko.soy/gogol
on develop help sign in
Regenerating gogol-compute from latest service definition
ec1fb32Brendan Hay
gogol-compute/gen/Network/Google/Compute.hs+18−10
compare with develop
unifiedsplit
@@ -13,7 +13,7 @@
13-- Stability : auto-generated
13-- Stability : auto-generated
14-- Portability : non-portable (GHC extensions)
14-- Portability : non-portable (GHC extensions)
15--
15--
16−-- API for the Google Compute Engine service.
16+-- Creates and runs virtual machines on Google Cloud Platform.
17--
17--
18-- /See:/ <https://developers.google.com/compute/docs/reference/latest/ Compute Engine API Reference>
18-- /See:/ <https://developers.google.com/compute/docs/reference/latest/ Compute Engine API Reference>
19module Network.Google.Compute
19module Network.Google.Compute
@@ -118,6 +118,9 @@ module Network.Google.Compute
118 -- ** compute.disks.list
118 -- ** compute.disks.list
119 , module Network.Google.Resource.Compute.Disks.List
119 , module Network.Google.Resource.Compute.Disks.List
120
120
121+ -- ** compute.disks.resize
122+ , module Network.Google.Resource.Compute.Disks.Resize
123+
121 -- ** compute.firewalls.delete
124 -- ** compute.firewalls.delete
122 , module Network.Google.Resource.Compute.Firewalls.Delete
125 , module Network.Google.Resource.Compute.Firewalls.Delete
123
126
@@ -238,6 +241,9 @@ module Network.Google.Compute
238 -- ** compute.images.get
241 -- ** compute.images.get
239 , module Network.Google.Resource.Compute.Images.Get
242 , module Network.Google.Resource.Compute.Images.Get
240
243
244+ -- ** compute.images.getFromFamily
245+ , module Network.Google.Resource.Compute.Images.GetFromFamily
246+
241 -- ** compute.images.insert
247 -- ** compute.images.insert
242 , module Network.Google.Resource.Compute.Images.Insert
248 , module Network.Google.Resource.Compute.Images.Insert
243
249
@@ -822,6 +828,7 @@ module Network.Google.Compute
822 , iSourceDiskId
828 , iSourceDiskId
823 , iKind
829 , iKind
824 , iArchiveSizeBytes
830 , iArchiveSizeBytes
831+ , iFamily
825 , iRawDisk
832 , iRawDisk
826 , iSelfLink
833 , iSelfLink
827 , iName
834 , iName
@@ -1432,7 +1439,6 @@ module Network.Google.Compute
1432 , Zone
1439 , Zone
1433 , zone
1440 , zone
1434 , zStatus
1441 , zStatus
1435− , zMaintenanceWindows
1436 , zKind
1442 , zKind
1437 , zSelfLink
1443 , zSelfLink
1438 , zName
1444 , zName
@@ -1520,14 +1526,6 @@ module Network.Google.Compute
1520 , itDescription
1526 , itDescription
1521 , itProperties
1527 , itProperties
1522
1528
1523− -- ** ZoneMaintenanceWindowsItem
1524− , ZoneMaintenanceWindowsItem
1525− , zoneMaintenanceWindowsItem
1526− , zmwiBeginTime
1527− , zmwiName
1528− , zmwiEndTime
1529− , zmwiDescription
1530−
1531 -- ** TargetVPNGateway
1529 -- ** TargetVPNGateway
1532 , TargetVPNGateway
1530 , TargetVPNGateway
1533 , targetVPNGateway
1531 , targetVPNGateway
@@ -2020,6 +2018,11 @@ module Network.Google.Compute
2020 , salSelfLink
2018 , salSelfLink
2021 , salId
2019 , salId
2022
2020
2021+ -- ** DisksResizeRequest
2022+ , DisksResizeRequest
2023+ , disksResizeRequest
2024+ , drrSizeGb
2025+
2023 -- ** AutoscalersScopedListWarningDataItem
2026 -- ** AutoscalersScopedListWarningDataItem
2024 , AutoscalersScopedListWarningDataItem
2027 , AutoscalersScopedListWarningDataItem
2025 , autoscalersScopedListWarningDataItem
2028 , autoscalersScopedListWarningDataItem
@@ -2401,6 +2404,7 @@ module Network.Google.Compute
2401 , bsName
2404 , bsName
2402 , bsCreationTimestamp
2405 , bsCreationTimestamp
2403 , bsId
2406 , bsId
2407+ , bsRegion
2404 , bsTimeoutSec
2408 , bsTimeoutSec
2405 , bsDescription
2409 , bsDescription
2406 , bsPortName
2410 , bsPortName
@@ -2535,6 +2539,7 @@ import Network.Google.Resource.Compute.Disks.Delete
2535import Network.Google.Resource.Compute.Disks.Get
2539import Network.Google.Resource.Compute.Disks.Get
2536import Network.Google.Resource.Compute.Disks.Insert
2540import Network.Google.Resource.Compute.Disks.Insert
2537import Network.Google.Resource.Compute.Disks.List
2541import Network.Google.Resource.Compute.Disks.List
2542+import Network.Google.Resource.Compute.Disks.Resize
2538import Network.Google.Resource.Compute.DiskTypes.AggregatedList
2543import Network.Google.Resource.Compute.DiskTypes.AggregatedList
2539import Network.Google.Resource.Compute.DiskTypes.Get
2544import Network.Google.Resource.Compute.DiskTypes.Get
2540import Network.Google.Resource.Compute.DiskTypes.List
2545import Network.Google.Resource.Compute.DiskTypes.List
@@ -2578,6 +2583,7 @@ import Network.Google.Resource.Compute.HTTPSHealthChecks.Update
2578import Network.Google.Resource.Compute.Images.Delete
2583import Network.Google.Resource.Compute.Images.Delete
2579import Network.Google.Resource.Compute.Images.Deprecate
2584import Network.Google.Resource.Compute.Images.Deprecate
2580import Network.Google.Resource.Compute.Images.Get
2585import Network.Google.Resource.Compute.Images.Get
2586+import Network.Google.Resource.Compute.Images.GetFromFamily
2581import Network.Google.Resource.Compute.Images.Insert
2587import Network.Google.Resource.Compute.Images.Insert
2582import Network.Google.Resource.Compute.Images.List
2588import Network.Google.Resource.Compute.Images.List
2583import Network.Google.Resource.Compute.InstanceGroupManagers.AbandonInstances
2589import Network.Google.Resource.Compute.InstanceGroupManagers.AbandonInstances
@@ -2715,6 +2721,7 @@ TODO
2715type ComputeAPI =
2721type ComputeAPI =
2716 ImagesInsertResource :<|> ImagesListResource :<|>
2722 ImagesInsertResource :<|> ImagesListResource :<|>
2717 ImagesGetResource
2723 ImagesGetResource
2724+ :<|> ImagesGetFromFamilyResource
2718 :<|> ImagesDeprecateResource
2725 :<|> ImagesDeprecateResource
2719 :<|> ImagesDeleteResource
2726 :<|> ImagesDeleteResource
2720 :<|> URLMapsInsertResource
2727 :<|> URLMapsInsertResource
@@ -2870,6 +2877,7 @@ type ComputeAPI =
2870 :<|> TargetInstancesDeleteResource
2877 :<|> TargetInstancesDeleteResource
2871 :<|> DisksAggregatedListResource
2878 :<|> DisksAggregatedListResource
2872 :<|> DisksInsertResource
2879 :<|> DisksInsertResource
2880+ :<|> DisksResizeResource
2873 :<|> DisksListResource
2881 :<|> DisksListResource
2874 :<|> DisksGetResource
2882 :<|> DisksGetResource
2875 :<|> DisksCreateSnapshotResource
2883 :<|> DisksCreateSnapshotResource
gogol-compute/gen/Network/Google/Compute/Types.hs+7−9
@@ -225,6 +225,7 @@ module Network.Google.Compute.Types
225 , iSourceDiskId
225 , iSourceDiskId
226 , iKind
226 , iKind
227 , iArchiveSizeBytes
227 , iArchiveSizeBytes
228+ , iFamily
228 , iRawDisk
229 , iRawDisk
229 , iSelfLink
230 , iSelfLink
230 , iName
231 , iName
@@ -835,7 +836,6 @@ module Network.Google.Compute.Types
835 , Zone
836 , Zone
836 , zone
837 , zone
837 , zStatus
838 , zStatus
838− , zMaintenanceWindows
839 , zKind
839 , zKind
840 , zSelfLink
840 , zSelfLink
841 , zName
841 , zName
@@ -923,14 +923,6 @@ module Network.Google.Compute.Types
923 , itDescription
923 , itDescription
924 , itProperties
924 , itProperties
925
925
926− -- * ZoneMaintenanceWindowsItem
927− , ZoneMaintenanceWindowsItem
928− , zoneMaintenanceWindowsItem
929− , zmwiBeginTime
930− , zmwiName
931− , zmwiEndTime
932− , zmwiDescription
933−
934 -- * TargetVPNGateway
926 -- * TargetVPNGateway
935 , TargetVPNGateway
927 , TargetVPNGateway
936 , targetVPNGateway
928 , targetVPNGateway
@@ -1423,6 +1415,11 @@ module Network.Google.Compute.Types
1423 , salSelfLink
1415 , salSelfLink
1424 , salId
1416 , salId
1425
1417
1418+ -- * DisksResizeRequest
1419+ , DisksResizeRequest
1420+ , disksResizeRequest
1421+ , drrSizeGb
1422+
1426 -- * AutoscalersScopedListWarningDataItem
1423 -- * AutoscalersScopedListWarningDataItem
1427 , AutoscalersScopedListWarningDataItem
1424 , AutoscalersScopedListWarningDataItem
1428 , autoscalersScopedListWarningDataItem
1425 , autoscalersScopedListWarningDataItem
@@ -1804,6 +1801,7 @@ module Network.Google.Compute.Types
1804 , bsName
1801 , bsName
1805 , bsCreationTimestamp
1802 , bsCreationTimestamp
1806 , bsId
1803 , bsId
1804+ , bsRegion
1807 , bsTimeoutSec
1805 , bsTimeoutSec
1808 , bsDescription
1806 , bsDescription
1809 , bsPortName
1807 , bsPortName
gogol-compute/gen/Network/Google/Compute/Types/Product.hs+100−134
@@ -1656,6 +1656,7 @@ data Image = Image'
1656 , _iSourceDiskId :: !(Maybe Text)
1656 , _iSourceDiskId :: !(Maybe Text)
1657 , _iKind :: !Text
1657 , _iKind :: !Text
1658 , _iArchiveSizeBytes :: !(Maybe (Textual Int64))
1658 , _iArchiveSizeBytes :: !(Maybe (Textual Int64))
1659+ , _iFamily :: !(Maybe Text)
1659 , _iRawDisk :: !(Maybe ImageRawDisk)
1660 , _iRawDisk :: !(Maybe ImageRawDisk)
1660 , _iSelfLink :: !(Maybe Text)
1661 , _iSelfLink :: !(Maybe Text)
1661 , _iName :: !(Maybe Text)
1662 , _iName :: !(Maybe Text)
@@ -1683,6 +1684,8 @@ data Image = Image'
1683--
1684--
1684-- * 'iArchiveSizeBytes'
1685-- * 'iArchiveSizeBytes'
1685--
1686--
1687+-- * 'iFamily'
1688+--
1686-- * 'iRawDisk'
1689-- * 'iRawDisk'
1687--
1690--
1688-- * 'iSelfLink'
1691-- * 'iSelfLink'
@@ -1710,6 +1713,7 @@ image =
1710 , _iSourceDiskId = Nothing
1713 , _iSourceDiskId = Nothing
1711 , _iKind = "compute#image"
1714 , _iKind = "compute#image"
1712 , _iArchiveSizeBytes = Nothing
1715 , _iArchiveSizeBytes = Nothing
1716+ , _iFamily = Nothing
1713 , _iRawDisk = Nothing
1717 , _iRawDisk = Nothing
1714 , _iSelfLink = Nothing
1718 , _iSelfLink = Nothing
1715 , _iName = Nothing
1719 , _iName = Nothing
@@ -1760,6 +1764,12 @@ iArchiveSizeBytes
1760 (\ s a -> s{_iArchiveSizeBytes = a})
1764 (\ s a -> s{_iArchiveSizeBytes = a})
1761 . mapping _Coerce
1765 . mapping _Coerce
1762
1766
1767+-- | The name of the image family to which this image belongs. You can create
1768+-- disks by specifying an image family instead of a specific image name.
1769+-- The image family always returns its latest image that is not deprecated.
1770+iFamily :: Lens' Image (Maybe Text)
1771+iFamily = lens _iFamily (\ s a -> s{_iFamily = a})
1772+
1763-- | The parameters of the raw disk image.
1773-- | The parameters of the raw disk image.
1764iRawDisk :: Lens' Image (Maybe ImageRawDisk)
1774iRawDisk :: Lens' Image (Maybe ImageRawDisk)
1765iRawDisk = lens _iRawDisk (\ s a -> s{_iRawDisk = a})
1775iRawDisk = lens _iRawDisk (\ s a -> s{_iRawDisk = a})
@@ -1829,6 +1839,7 @@ instance FromJSON Image where
1829 <*> (o .:? "sourceDiskId")
1839 <*> (o .:? "sourceDiskId")
1830 <*> (o .:? "kind" .!= "compute#image")
1840 <*> (o .:? "kind" .!= "compute#image")
1831 <*> (o .:? "archiveSizeBytes")
1841 <*> (o .:? "archiveSizeBytes")
1842+ <*> (o .:? "family")
1832 <*> (o .:? "rawDisk")
1843 <*> (o .:? "rawDisk")
1833 <*> (o .:? "selfLink")
1844 <*> (o .:? "selfLink")
1834 <*> (o .:? "name")
1845 <*> (o .:? "name")
@@ -1849,6 +1860,7 @@ instance ToJSON Image where
1849 ("sourceDiskId" .=) <$> _iSourceDiskId,
1860 ("sourceDiskId" .=) <$> _iSourceDiskId,
1850 Just ("kind" .= _iKind),
1861 Just ("kind" .= _iKind),
1851 ("archiveSizeBytes" .=) <$> _iArchiveSizeBytes,
1862 ("archiveSizeBytes" .=) <$> _iArchiveSizeBytes,
1863+ ("family" .=) <$> _iFamily,
1852 ("rawDisk" .=) <$> _iRawDisk,
1864 ("rawDisk" .=) <$> _iRawDisk,
1853 ("selfLink" .=) <$> _iSelfLink,
1865 ("selfLink" .=) <$> _iSelfLink,
1854 ("name" .=) <$> _iName,
1866 ("name" .=) <$> _iName,
@@ -3687,7 +3699,7 @@ frName :: Lens' ForwardingRule (Maybe Text)
3687frName = lens _frName (\ s a -> s{_frName = a})
3699frName = lens _frName (\ s a -> s{_frName = a})
3688
3700
3689-- | The IP protocol to which this rule applies. Valid options are TCP, UDP,
3701-- | The IP protocol to which this rule applies. Valid options are TCP, UDP,
3690−-- ESP, AH or SCTP.
3702+-- ESP, AH, SCTP or ICMP.
3691frIPProtocol :: Lens' ForwardingRule (Maybe ForwardingRuleIPProtocol)
3703frIPProtocol :: Lens' ForwardingRule (Maybe ForwardingRuleIPProtocol)
3692frIPProtocol
3704frIPProtocol
3693 = lens _frIPProtocol (\ s a -> s{_frIPProtocol = a})
3705 = lens _frIPProtocol (\ s a -> s{_frIPProtocol = a})
@@ -4298,7 +4310,7 @@ oStartTime
4298 = lens _oStartTime (\ s a -> s{_oStartTime = a})
4310 = lens _oStartTime (\ s a -> s{_oStartTime = a})
4299
4311
4300-- | [Output Only] Type of the resource. Always compute#operation for
4312-- | [Output Only] Type of the resource. Always compute#operation for
4301−-- operation resources.
4313+-- Operation resources.
4302oKind :: Lens' Operation Text
4314oKind :: Lens' Operation Text
4303oKind = lens _oKind (\ s a -> s{_oKind = a})
4315oKind = lens _oKind (\ s a -> s{_oKind = a})
4304
4316
@@ -4631,22 +4643,17 @@ dUsers
4631 _Coerce
4643 _Coerce
4632
4644
4633-- | The source image used to create this disk. If the source image is
4645-- | The source image used to create this disk. If the source image is
4634−-- deleted from the system, this field will not be set, even if an image
4646+-- deleted, this field will not be set. To create a disk with one of the
4635−-- with the same name has been re-created. When creating a disk, you can
4647+-- public operating system images, specify the image by its family name.
4636−-- provide a private (custom) image using the following input, and Compute
4648+-- For example, specify family\/debian-8 to use the latest Debian 8 image:
4637−-- Engine will use the corresponding image from your project. For example:
4649+-- projects\/debian-cloud\/global\/images\/family\/debian-8 Alternatively,
4650+-- use a specific version of a public operating system image:
4651+-- projects\/debian-cloud\/global\/images\/debian-8-jessie-vYYYYMMDD To
4652+-- create a disk with a private image that you created, specify the image
4638−-- global\/images\/my-private-image Or you can provide an image from a
4653+-- name in the following format: global\/images\/my-private-image You can
4639−-- publicly-available project. For example, to use a Debian image from the
4640−-- debian-cloud project, make sure to include the project in the URL:
4641−-- projects\/debian-cloud\/global\/images\/debian-7-wheezy-vYYYYMMDD where
4642−-- vYYYYMMDD is the image version. The fully-qualified URL will also work
4643−-- in both cases. You can also specify the latest image for a private image
4654+-- also specify a private image by its image family, which returns the
4644−-- family by replacing the image name suffix with family\/family-name. For
4655+-- latest version of the image in that family. Replace the image name with
4645−-- example: global\/images\/family\/my-private-family Or you can specify an
4656+-- family\/family-name: global\/images\/family\/my-private-family
4646−-- image family from a publicly-available project. For example, to use the
4647−-- latest Debian 7 from the debian-cloud project, make sure to include the
4648−-- project in the URL:
4649−-- projects\/debian-cloud\/global\/images\/family\/debian-7
4650dSourceImage :: Lens' Disk (Maybe Text)
4657dSourceImage :: Lens' Disk (Maybe Text)
4651dSourceImage
4658dSourceImage
4652 = lens _dSourceImage (\ s a -> s{_dSourceImage = a})
4659 = lens _dSourceImage (\ s a -> s{_dSourceImage = a})
@@ -5023,9 +5030,8 @@ instanceGroupManager =
5023igmKind :: Lens' InstanceGroupManager Text
5030igmKind :: Lens' InstanceGroupManager Text
5024igmKind = lens _igmKind (\ s a -> s{_igmKind = a})
5031igmKind = lens _igmKind (\ s a -> s{_igmKind = a})
5025
5032
5026−-- | [Output Only] The fingerprint of the target pools information. You can
5033+-- | [Output Only] The fingerprint of the resource data. You can use this
5027−-- use this optional field for optimistic locking when you update the
5034+-- optional field for optimistic locking when you update the resource.
5028−-- target pool entries.
5029igmFingerprint :: Lens' InstanceGroupManager (Maybe Word8)
5035igmFingerprint :: Lens' InstanceGroupManager (Maybe Word8)
5030igmFingerprint
5036igmFingerprint
5031 = lens _igmFingerprint
5037 = lens _igmFingerprint
@@ -6045,15 +6051,18 @@ attachedDiskInitializeParams =
6045 , _adipDiskType = Nothing
6051 , _adipDiskType = Nothing
6046 }
6052 }
6047
6053
6048−-- | A source image used to create the disk. You can provide a private
6054+-- | The source image used to create this disk. If the source image is
6049−-- (custom) image, and Compute Engine will use the corresponding image from
6055+-- deleted, this field will not be set. To create a disk with one of the
6050−-- your project. For example: global\/images\/my-private-image Or you can
6056+-- public operating system images, specify the image by its family name.
6051−-- provide an image from a publicly-available project. For example, to use
6057+-- For example, specify family\/debian-8 to use the latest Debian 8 image:
6052−-- a Debian image from the debian-cloud project, make sure to include the
6058+-- projects\/debian-cloud\/global\/images\/family\/debian-8 Alternatively,
6053−-- project in the URL:
6059+-- use a specific version of a public operating system image:
6054−-- projects\/debian-cloud\/global\/images\/debian-7-wheezy-vYYYYMMDD where
6060+-- projects\/debian-cloud\/global\/images\/debian-8-jessie-vYYYYMMDD To
6055−-- vYYYYMMDD is the image version. The fully-qualified URL will also work
6061+-- create a disk with a private image that you created, specify the image
6056−-- in both cases.
6062+-- name in the following format: global\/images\/my-private-image You can
6063+-- also specify a private image by its image family, which returns the
6064+-- latest version of the image in that family. Replace the image name with
6065+-- family\/family-name: global\/images\/family\/my-private-family
6057adipSourceImage :: Lens' AttachedDiskInitializeParams (Maybe Text)
6066adipSourceImage :: Lens' AttachedDiskInitializeParams (Maybe Text)
6058adipSourceImage
6067adipSourceImage
6059 = lens _adipSourceImage
6068 = lens _adipSourceImage
@@ -6210,8 +6219,9 @@ niNetwork
6210niName :: Lens' NetworkInterface (Maybe Text)
6219niName :: Lens' NetworkInterface (Maybe Text)
6211niName = lens _niName (\ s a -> s{_niName = a})
6220niName = lens _niName (\ s a -> s{_niName = a})
6212
6221
6213−-- | [Output Only] An optional IPV4 internal network address assigned to the
6222+-- | An IPV4 internal network address to assign to the instance for this
6214−-- instance for this network interface.
6223+-- network interface. If not specified by user an unused internal IP is
6224+-- assigned by system.
6215niNetworkIP :: Lens' NetworkInterface (Maybe Text)
6225niNetworkIP :: Lens' NetworkInterface (Maybe Text)
6216niNetworkIP
6226niNetworkIP
6217 = lens _niNetworkIP (\ s a -> s{_niNetworkIP = a})
6227 = lens _niNetworkIP (\ s a -> s{_niNetworkIP = a})
@@ -6222,8 +6232,8 @@ niNetworkIP
6222-- network is in custom subnet mode, then this field should be specified.
6232-- network is in custom subnet mode, then this field should be specified.
6223-- If you specify this property, you can specify the subnetwork as a full
6233-- If you specify this property, you can specify the subnetwork as a full
6224-- or partial URL. For example, the following are all valid URLs: -
6234-- or partial URL. For example, the following are all valid URLs: -
6225−-- https:\/\/www.googleapis.com\/compute\/v1\/projects\/project\/zones\/zone\/subnetworks\/subnetwork
6235+-- https:\/\/www.googleapis.com\/compute\/v1\/projects\/project\/regions\/region\/subnetworks\/subnetwork
6226−-- - zones\/zone\/subnetworks\/subnetwork
6236+-- - regions\/region\/subnetworks\/subnetwork
6227niSubnetwork :: Lens' NetworkInterface (Maybe Text)
6237niSubnetwork :: Lens' NetworkInterface (Maybe Text)
6228niSubnetwork
6238niSubnetwork
6229 = lens _niSubnetwork (\ s a -> s{_niSubnetwork = a})
6239 = lens _niSubnetwork (\ s a -> s{_niSubnetwork = a})
@@ -7218,16 +7228,15 @@ instance ToJSON Address where
7218--
7228--
7219-- /See:/ 'zone' smart constructor.
7229-- /See:/ 'zone' smart constructor.
7220data Zone = Zone'
7230data Zone = Zone'
7221− { _zStatus :: !(Maybe ZoneStatus)
7231+ { _zStatus :: !(Maybe ZoneStatus)
7222− , _zMaintenanceWindows :: !(Maybe [ZoneMaintenanceWindowsItem])
7223− , _zKind :: !Text
7232+ , _zKind :: !Text
7224− , _zSelfLink :: !(Maybe Text)
7233+ , _zSelfLink :: !(Maybe Text)
7225− , _zName :: !(Maybe Text)
7234+ , _zName :: !(Maybe Text)
7226− , _zCreationTimestamp :: !(Maybe Text)
7235+ , _zCreationTimestamp :: !(Maybe Text)
7227− , _zId :: !(Maybe (Textual Word64))
7236+ , _zId :: !(Maybe (Textual Word64))
7228− , _zRegion :: !(Maybe Text)
7237+ , _zRegion :: !(Maybe Text)
7229− , _zDescription :: !(Maybe Text)
7238+ , _zDescription :: !(Maybe Text)
7230− , _zDeprecated :: !(Maybe DeprecationStatus)
7239+ , _zDeprecated :: !(Maybe DeprecationStatus)
7231 } deriving (Eq,Show,Data,Typeable,Generic)
7240 } deriving (Eq,Show,Data,Typeable,Generic)
7232
7241
7233-- | Creates a value of 'Zone' with the minimum fields required to make a request.
7242-- | Creates a value of 'Zone' with the minimum fields required to make a request.
@@ -7236,8 +7245,6 @@ data Zone = Zone'
7236--
7245--
7237-- * 'zStatus'
7246-- * 'zStatus'
7238--
7247--
7239−-- * 'zMaintenanceWindows'
7240−--
7241-- * 'zKind'
7248-- * 'zKind'
7242--
7249--
7243-- * 'zSelfLink'
7250-- * 'zSelfLink'
@@ -7258,7 +7265,6 @@ zone
7258zone =
7265zone =
7259 Zone'
7266 Zone'
7260 { _zStatus = Nothing
7267 { _zStatus = Nothing
7261− , _zMaintenanceWindows = Nothing
7262 , _zKind = "compute#zone"
7268 , _zKind = "compute#zone"
7263 , _zSelfLink = Nothing
7269 , _zSelfLink = Nothing
7264 , _zName = Nothing
7270 , _zName = Nothing
@@ -7273,16 +7279,6 @@ zone =
7273zStatus :: Lens' Zone (Maybe ZoneStatus)
7279zStatus :: Lens' Zone (Maybe ZoneStatus)
7274zStatus = lens _zStatus (\ s a -> s{_zStatus = a})
7280zStatus = lens _zStatus (\ s a -> s{_zStatus = a})
7275
7281
7276−-- | [Output Only] Any scheduled maintenance windows for this zone. When the
7277−-- zone is in a maintenance window, all resources which reside in the zone
7278−-- will be unavailable. For more information, see Maintenance Windows
7279−zMaintenanceWindows :: Lens' Zone [ZoneMaintenanceWindowsItem]
7280−zMaintenanceWindows
7281− = lens _zMaintenanceWindows
7282− (\ s a -> s{_zMaintenanceWindows = a})
7283− . _Default
7284− . _Coerce
7285−
7286-- | [Output Only] Type of the resource. Always compute#zone for zones.
7282-- | [Output Only] Type of the resource. Always compute#zone for zones.
7287zKind :: Lens' Zone Text
7283zKind :: Lens' Zone Text
7288zKind = lens _zKind (\ s a -> s{_zKind = a})
7284zKind = lens _zKind (\ s a -> s{_zKind = a})
@@ -7328,8 +7324,7 @@ instance FromJSON Zone where
7328 (\ o ->
7324 (\ o ->
7329 Zone' <$>
7325 Zone' <$>
7330 (o .:? "status") <*>
7326 (o .:? "status") <*>
7331− (o .:? "maintenanceWindows" .!= mempty)
7332− <*> (o .:? "kind" .!= "compute#zone")
7327+ (o .:? "kind" .!= "compute#zone")
7333 <*> (o .:? "selfLink")
7328 <*> (o .:? "selfLink")
7334 <*> (o .:? "name")
7329 <*> (o .:? "name")
7335 <*> (o .:? "creationTimestamp")
7330 <*> (o .:? "creationTimestamp")
@@ -7342,9 +7337,7 @@ instance ToJSON Zone where
7342 toJSON Zone'{..}
7337 toJSON Zone'{..}
7343 = object
7338 = object
7344 (catMaybes
7339 (catMaybes
7345− [("status" .=) <$> _zStatus,
7340+ [("status" .=) <$> _zStatus, Just ("kind" .= _zKind),
7346− ("maintenanceWindows" .=) <$> _zMaintenanceWindows,
7347− Just ("kind" .= _zKind),
7348 ("selfLink" .=) <$> _zSelfLink,
7341 ("selfLink" .=) <$> _zSelfLink,
7349 ("name" .=) <$> _zName,
7342 ("name" .=) <$> _zName,
7350 ("creationTimestamp" .=) <$> _zCreationTimestamp,
7343 ("creationTimestamp" .=) <$> _zCreationTimestamp,
@@ -8066,76 +8059,6 @@ instance ToJSON InstanceTemplate where
8066 ("description" .=) <$> _itDescription,
8059 ("description" .=) <$> _itDescription,
8067 ("properties" .=) <$> _itProperties])
8060 ("properties" .=) <$> _itProperties])
8068
8061
8069−--
8070−-- /See:/ 'zoneMaintenanceWindowsItem' smart constructor.
8071−data ZoneMaintenanceWindowsItem = ZoneMaintenanceWindowsItem'
8072− { _zmwiBeginTime :: !(Maybe Text)
8073− , _zmwiName :: !(Maybe Text)
8074− , _zmwiEndTime :: !(Maybe Text)
8075− , _zmwiDescription :: !(Maybe Text)
8076− } deriving (Eq,Show,Data,Typeable,Generic)
8077−
8078−-- | Creates a value of 'ZoneMaintenanceWindowsItem' with the minimum fields required to make a request.
8079−--
8080−-- Use one of the following lenses to modify other fields as desired:
8081−--
8082−-- * 'zmwiBeginTime'
8083−--
8084−-- * 'zmwiName'
8085−--
8086−-- * 'zmwiEndTime'
8087−--
8088−-- * 'zmwiDescription'
8089−zoneMaintenanceWindowsItem
8090− :: ZoneMaintenanceWindowsItem
8091−zoneMaintenanceWindowsItem =
8092− ZoneMaintenanceWindowsItem'
8093− { _zmwiBeginTime = Nothing
8094− , _zmwiName = Nothing
8095− , _zmwiEndTime = Nothing
8096− , _zmwiDescription = Nothing
8097− }
8098−
8099−-- | [Output Only] Starting time of the maintenance window, in RFC3339
8100−-- format.
8101−zmwiBeginTime :: Lens' ZoneMaintenanceWindowsItem (Maybe Text)
8102−zmwiBeginTime
8103− = lens _zmwiBeginTime
8104− (\ s a -> s{_zmwiBeginTime = a})
8105−
8106−-- | [Output Only] Name of the maintenance window.
8107−zmwiName :: Lens' ZoneMaintenanceWindowsItem (Maybe Text)
8108−zmwiName = lens _zmwiName (\ s a -> s{_zmwiName = a})
8109−
8110−-- | [Output Only] Ending time of the maintenance window, in RFC3339 format.
8111−zmwiEndTime :: Lens' ZoneMaintenanceWindowsItem (Maybe Text)
8112−zmwiEndTime
8113− = lens _zmwiEndTime (\ s a -> s{_zmwiEndTime = a})
8114−
8115−-- | [Output Only] Textual description of the maintenance window.
8116−zmwiDescription :: Lens' ZoneMaintenanceWindowsItem (Maybe Text)
8117−zmwiDescription
8118− = lens _zmwiDescription
8119− (\ s a -> s{_zmwiDescription = a})
8120−
8121−instance FromJSON ZoneMaintenanceWindowsItem where
8122− parseJSON
8123− = withObject "ZoneMaintenanceWindowsItem"
8124− (\ o ->
8125− ZoneMaintenanceWindowsItem' <$>
8126− (o .:? "beginTime") <*> (o .:? "name") <*>
8127− (o .:? "endTime")
8128− <*> (o .:? "description"))
8129−
8130−instance ToJSON ZoneMaintenanceWindowsItem where
8131− toJSON ZoneMaintenanceWindowsItem'{..}
8132− = object
8133− (catMaybes
8134− [("beginTime" .=) <$> _zmwiBeginTime,
8135− ("name" .=) <$> _zmwiName,
8136− ("endTime" .=) <$> _zmwiEndTime,
8137− ("description" .=) <$> _zmwiDescription])
8138−
8139-- | Represents a Target VPN gateway resource.
8062-- | Represents a Target VPN gateway resource.
8140--
8063--
8141-- /See:/ 'targetVPNGateway' smart constructor.
8064-- /See:/ 'targetVPNGateway' smart constructor.
@@ -11362,7 +11285,7 @@ subId
11362 = lens _subId (\ s a -> s{_subId = a}) .
11285 = lens _subId (\ s a -> s{_subId = a}) .
11363 mapping _Coerce
11286 mapping _Coerce
11364
11287
11365−-- | [Output Only] URL of the region where the Subnetwork resides.
11288+-- | URL of the region where the Subnetwork resides.
11366subRegion :: Lens' Subnetwork (Maybe Text)
11289subRegion :: Lens' Subnetwork (Maybe Text)
11367subRegion
11290subRegion
11368 = lens _subRegion (\ s a -> s{_subRegion = a})
11291 = lens _subRegion (\ s a -> s{_subRegion = a})
@@ -12447,6 +12370,39 @@ instance ToJSON SubnetworkAggregatedList where
12447 ("selfLink" .=) <$> _salSelfLink,
12370 ("selfLink" .=) <$> _salSelfLink,
12448 ("id" .=) <$> _salId])
12371 ("id" .=) <$> _salId])
12449
12372
12373+--
12374+-- /See:/ 'disksResizeRequest' smart constructor.
12375+newtype DisksResizeRequest = DisksResizeRequest'
12376+ { _drrSizeGb :: Maybe (Textual Int64)
12377+ } deriving (Eq,Show,Data,Typeable,Generic)
12378+
12379+-- | Creates a value of 'DisksResizeRequest' with the minimum fields required to make a request.
12380+--
12381+-- Use one of the following lenses to modify other fields as desired:
12382+--
12383+-- * 'drrSizeGb'
12384+disksResizeRequest
12385+ :: DisksResizeRequest
12386+disksResizeRequest =
12387+ DisksResizeRequest'
12388+ { _drrSizeGb = Nothing
12389+ }
12390+
12391+-- | The new size of the persistent disk, which is specified in GB.
12392+drrSizeGb :: Lens' DisksResizeRequest (Maybe Int64)
12393+drrSizeGb
12394+ = lens _drrSizeGb (\ s a -> s{_drrSizeGb = a}) .
12395+ mapping _Coerce
12396+
12397+instance FromJSON DisksResizeRequest where
12398+ parseJSON
12399+ = withObject "DisksResizeRequest"
12400+ (\ o -> DisksResizeRequest' <$> (o .:? "sizeGb"))
12401+
12402+instance ToJSON DisksResizeRequest where
12403+ toJSON DisksResizeRequest'{..}
12404+ = object (catMaybes [("sizeGb" .=) <$> _drrSizeGb])
12405+
12450--
12406--
12451-- /See:/ 'autoscalersScopedListWarningDataItem' smart constructor.
12407-- /See:/ 'autoscalersScopedListWarningDataItem' smart constructor.
12452data AutoscalersScopedListWarningDataItem = AutoscalersScopedListWarningDataItem'
12408data AutoscalersScopedListWarningDataItem = AutoscalersScopedListWarningDataItem'
@@ -15832,6 +15788,7 @@ data BackendService = BackendService'
15832 , _bsName :: !(Maybe Text)
15788 , _bsName :: !(Maybe Text)
15833 , _bsCreationTimestamp :: !(Maybe Text)
15789 , _bsCreationTimestamp :: !(Maybe Text)
15834 , _bsId :: !(Maybe (Textual Word64))
15790 , _bsId :: !(Maybe (Textual Word64))
15791+ , _bsRegion :: !(Maybe Text)
15835 , _bsTimeoutSec :: !(Maybe (Textual Int32))
15792 , _bsTimeoutSec :: !(Maybe (Textual Int32))
15836 , _bsDescription :: !(Maybe Text)
15793 , _bsDescription :: !(Maybe Text)
15837 , _bsPortName :: !(Maybe Text)
15794 , _bsPortName :: !(Maybe Text)
@@ -15859,6 +15816,8 @@ data BackendService = BackendService'
15859--
15816--
15860-- * 'bsId'
15817-- * 'bsId'
15861--
15818--
15819+-- * 'bsRegion'
15820+--
15862-- * 'bsTimeoutSec'
15821-- * 'bsTimeoutSec'
15863--
15822--
15864-- * 'bsDescription'
15823-- * 'bsDescription'
@@ -15880,6 +15839,7 @@ backendService =
15880 , _bsName = Nothing
15839 , _bsName = Nothing
15881 , _bsCreationTimestamp = Nothing
15840 , _bsCreationTimestamp = Nothing
15882 , _bsId = Nothing
15841 , _bsId = Nothing
15842+ , _bsRegion = Nothing
15883 , _bsTimeoutSec = Nothing
15843 , _bsTimeoutSec = Nothing
15884 , _bsDescription = Nothing
15844 , _bsDescription = Nothing
15885 , _bsPortName = Nothing
15845 , _bsPortName = Nothing
@@ -15943,6 +15903,11 @@ bsId
15943 = lens _bsId (\ s a -> s{_bsId = a}) .
15903 = lens _bsId (\ s a -> s{_bsId = a}) .
15944 mapping _Coerce
15904 mapping _Coerce
15945
15905
15906+-- | [Output Only] URL of the region where the regional backend service
15907+-- resides. This field is not applicable to global backend services.
15908+bsRegion :: Lens' BackendService (Maybe Text)
15909+bsRegion = lens _bsRegion (\ s a -> s{_bsRegion = a})
15910+
15946-- | How many seconds to wait for the backend before considering it a failed
15911-- | How many seconds to wait for the backend before considering it a failed
15947-- request. Default is 30 seconds.
15912-- request. Default is 30 seconds.
15948bsTimeoutSec :: Lens' BackendService (Maybe Int32)
15913bsTimeoutSec :: Lens' BackendService (Maybe Int32)
@@ -15993,6 +15958,7 @@ instance FromJSON BackendService where
15993 <*> (o .:? "name")
15958 <*> (o .:? "name")
15994 <*> (o .:? "creationTimestamp")
15959 <*> (o .:? "creationTimestamp")
15995 <*> (o .:? "id")
15960 <*> (o .:? "id")
15961+ <*> (o .:? "region")
15996 <*> (o .:? "timeoutSec")
15962 <*> (o .:? "timeoutSec")
15997 <*> (o .:? "description")
15963 <*> (o .:? "description")
15998 <*> (o .:? "portName")
15964 <*> (o .:? "portName")
@@ -16010,7 +15976,7 @@ instance ToJSON BackendService where
16010 ("selfLink" .=) <$> _bsSelfLink,
15976 ("selfLink" .=) <$> _bsSelfLink,
16011 ("name" .=) <$> _bsName,
15977 ("name" .=) <$> _bsName,
16012 ("creationTimestamp" .=) <$> _bsCreationTimestamp,
15978 ("creationTimestamp" .=) <$> _bsCreationTimestamp,
16013− ("id" .=) <$> _bsId,
15979+ ("id" .=) <$> _bsId, ("region" .=) <$> _bsRegion,
16014 ("timeoutSec" .=) <$> _bsTimeoutSec,
15980 ("timeoutSec" .=) <$> _bsTimeoutSec,
16015 ("description" .=) <$> _bsDescription,
15981 ("description" .=) <$> _bsDescription,
16016 ("portName" .=) <$> _bsPortName,
15982 ("portName" .=) <$> _bsPortName,
gogol-compute/gen/Network/Google/Compute/Types/Sum.hs+1−1
@@ -1547,7 +1547,7 @@ instance ToJSON BackendBalancingMode where
1547 toJSON = toJSONText
1547 toJSON = toJSONText
1548
1548
1549-- | The IP protocol to which this rule applies. Valid options are TCP, UDP,
1549-- | The IP protocol to which this rule applies. Valid options are TCP, UDP,
1550−-- ESP, AH or SCTP.
1550+-- ESP, AH, SCTP or ICMP.
1551data ForwardingRuleIPProtocol
1551data ForwardingRuleIPProtocol
1552 = AH
1552 = AH
1553 -- ^ @AH@
1553 -- ^ @AH@
gogol-compute/gen/Network/Google/Resource/Compute/Addresses/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ aalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119aalFilter :: Lens' AddressesAggregatedList (Maybe Text)
118aalFilter :: Lens' AddressesAggregatedList (Maybe Text)
120aalFilter
119aalFilter
121 = lens _aalFilter (\ s a -> s{_aalFilter = a})
120 = lens _aalFilter (\ s a -> s{_aalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Addresses/List.hs+9−10
@@ -111,17 +111,16 @@ alProject
111-- value is interpreted as a regular expression using RE2 syntax. The
111-- value is interpreted as a regular expression using RE2 syntax. The
112-- literal value must match the entire field. For example, to filter for
112-- literal value must match the entire field. For example, to filter for
113-- instances that do not have a name of example-instance, you would use
113-- instances that do not have a name of example-instance, you would use
114−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
114+-- filter=name ne example-instance. Compute Engine Beta API Only: When
115−-- use filtering in the Beta API, you can also filter on nested fields. For
115+-- filtering in the Beta API, you can also filter on nested fields. For
116-- example, you could filter on instances that have set the
116-- example, you could filter on instances that have set the
117−-- scheduling.automaticRestart field to true. In particular, use filtering
117+-- scheduling.automaticRestart field to true. Use filtering on nested
118−-- on nested fields to take advantage of instance labels to organize and
118+-- fields to take advantage of labels to organize and search for results
119−-- filter results based on label values. The Beta API also supports
119+-- based on label values. The Beta API also supports filtering on multiple
120−-- filtering on multiple expressions by providing each separate expression
120+-- expressions by providing each separate expression within parentheses.
121−-- within parentheses. For example, (scheduling.automaticRestart eq true)
121+-- For example, (scheduling.automaticRestart eq true) (zone eq
122−-- (zone eq us-central1-f). Multiple expressions are treated as AND
122+-- us-central1-f). Multiple expressions are treated as AND expressions,
123−-- expressions, meaning that resources must match all expressions to pass
123+-- meaning that resources must match all expressions to pass the filters.
124−-- the filters.
125alFilter :: Lens' AddressesList (Maybe Text)
124alFilter :: Lens' AddressesList (Maybe Text)
126alFilter = lens _alFilter (\ s a -> s{_alFilter = a})
125alFilter = lens _alFilter (\ s a -> s{_alFilter = a})
127
126
gogol-compute/gen/Network/Google/Resource/Compute/Autoscalers/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ autProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119autFilter :: Lens' AutoscalersAggregatedList (Maybe Text)
118autFilter :: Lens' AutoscalersAggregatedList (Maybe Text)
120autFilter
119autFilter
121 = lens _autFilter (\ s a -> s{_autFilter = a})
120 = lens _autFilter (\ s a -> s{_autFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Autoscalers/List.hs+9−10
@@ -115,17 +115,16 @@ aZone = lens _aZone (\ s a -> s{_aZone = a})
115-- value is interpreted as a regular expression using RE2 syntax. The
115-- value is interpreted as a regular expression using RE2 syntax. The
116-- literal value must match the entire field. For example, to filter for
116-- literal value must match the entire field. For example, to filter for
117-- instances that do not have a name of example-instance, you would use
117-- instances that do not have a name of example-instance, you would use
118−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
118+-- filter=name ne example-instance. Compute Engine Beta API Only: When
119−-- use filtering in the Beta API, you can also filter on nested fields. For
119+-- filtering in the Beta API, you can also filter on nested fields. For
120-- example, you could filter on instances that have set the
120-- example, you could filter on instances that have set the
121−-- scheduling.automaticRestart field to true. In particular, use filtering
121+-- scheduling.automaticRestart field to true. Use filtering on nested
122−-- on nested fields to take advantage of instance labels to organize and
122+-- fields to take advantage of labels to organize and search for results
123−-- filter results based on label values. The Beta API also supports
123+-- based on label values. The Beta API also supports filtering on multiple
124−-- filtering on multiple expressions by providing each separate expression
124+-- expressions by providing each separate expression within parentheses.
125−-- within parentheses. For example, (scheduling.automaticRestart eq true)
125+-- For example, (scheduling.automaticRestart eq true) (zone eq
126−-- (zone eq us-central1-f). Multiple expressions are treated as AND
126+-- us-central1-f). Multiple expressions are treated as AND expressions,
127−-- expressions, meaning that resources must match all expressions to pass
127+-- meaning that resources must match all expressions to pass the filters.
128−-- the filters.
129aFilter :: Lens' AutoscalersList (Maybe Text)
128aFilter :: Lens' AutoscalersList (Maybe Text)
130aFilter = lens _aFilter (\ s a -> s{_aFilter = a})
129aFilter = lens _aFilter (\ s a -> s{_aFilter = a})
131
130
gogol-compute/gen/Network/Google/Resource/Compute/BackendServices/List.hs+9−10
@@ -107,17 +107,16 @@ bslProject
107-- value is interpreted as a regular expression using RE2 syntax. The
107-- value is interpreted as a regular expression using RE2 syntax. The
108-- literal value must match the entire field. For example, to filter for
108-- literal value must match the entire field. For example, to filter for
109-- instances that do not have a name of example-instance, you would use
109-- instances that do not have a name of example-instance, you would use
110−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
110+-- filter=name ne example-instance. Compute Engine Beta API Only: When
111−-- use filtering in the Beta API, you can also filter on nested fields. For
111+-- filtering in the Beta API, you can also filter on nested fields. For
112-- example, you could filter on instances that have set the
112-- example, you could filter on instances that have set the
113−-- scheduling.automaticRestart field to true. In particular, use filtering
113+-- scheduling.automaticRestart field to true. Use filtering on nested
114−-- on nested fields to take advantage of instance labels to organize and
114+-- fields to take advantage of labels to organize and search for results
115−-- filter results based on label values. The Beta API also supports
115+-- based on label values. The Beta API also supports filtering on multiple
116−-- filtering on multiple expressions by providing each separate expression
116+-- expressions by providing each separate expression within parentheses.
117−-- within parentheses. For example, (scheduling.automaticRestart eq true)
117+-- For example, (scheduling.automaticRestart eq true) (zone eq
118−-- (zone eq us-central1-f). Multiple expressions are treated as AND
118+-- us-central1-f). Multiple expressions are treated as AND expressions,
119−-- expressions, meaning that resources must match all expressions to pass
119+-- meaning that resources must match all expressions to pass the filters.
120−-- the filters.
121bslFilter :: Lens' BackendServicesList (Maybe Text)
120bslFilter :: Lens' BackendServicesList (Maybe Text)
122bslFilter
121bslFilter
123 = lens _bslFilter (\ s a -> s{_bslFilter = a})
122 = lens _bslFilter (\ s a -> s{_bslFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/DiskTypes/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ dtalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119dtalFilter :: Lens' DiskTypesAggregatedList (Maybe Text)
118dtalFilter :: Lens' DiskTypesAggregatedList (Maybe Text)
120dtalFilter
119dtalFilter
121 = lens _dtalFilter (\ s a -> s{_dtalFilter = a})
120 = lens _dtalFilter (\ s a -> s{_dtalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/DiskTypes/List.hs+9−10
@@ -115,17 +115,16 @@ dtlZone = lens _dtlZone (\ s a -> s{_dtlZone = a})
115-- value is interpreted as a regular expression using RE2 syntax. The
115-- value is interpreted as a regular expression using RE2 syntax. The
116-- literal value must match the entire field. For example, to filter for
116-- literal value must match the entire field. For example, to filter for
117-- instances that do not have a name of example-instance, you would use
117-- instances that do not have a name of example-instance, you would use
118−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
118+-- filter=name ne example-instance. Compute Engine Beta API Only: When
119−-- use filtering in the Beta API, you can also filter on nested fields. For
119+-- filtering in the Beta API, you can also filter on nested fields. For
120-- example, you could filter on instances that have set the
120-- example, you could filter on instances that have set the
121−-- scheduling.automaticRestart field to true. In particular, use filtering
121+-- scheduling.automaticRestart field to true. Use filtering on nested
122−-- on nested fields to take advantage of instance labels to organize and
122+-- fields to take advantage of labels to organize and search for results
123−-- filter results based on label values. The Beta API also supports
123+-- based on label values. The Beta API also supports filtering on multiple
124−-- filtering on multiple expressions by providing each separate expression
124+-- expressions by providing each separate expression within parentheses.
125−-- within parentheses. For example, (scheduling.automaticRestart eq true)
125+-- For example, (scheduling.automaticRestart eq true) (zone eq
126−-- (zone eq us-central1-f). Multiple expressions are treated as AND
126+-- us-central1-f). Multiple expressions are treated as AND expressions,
127−-- expressions, meaning that resources must match all expressions to pass
127+-- meaning that resources must match all expressions to pass the filters.
128−-- the filters.
129dtlFilter :: Lens' DiskTypesList (Maybe Text)
128dtlFilter :: Lens' DiskTypesList (Maybe Text)
130dtlFilter
129dtlFilter
131 = lens _dtlFilter (\ s a -> s{_dtlFilter = a})
130 = lens _dtlFilter (\ s a -> s{_dtlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Disks/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ dalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119dalFilter :: Lens' DisksAggregatedList (Maybe Text)
118dalFilter :: Lens' DisksAggregatedList (Maybe Text)
120dalFilter
119dalFilter
121 = lens _dalFilter (\ s a -> s{_dalFilter = a})
120 = lens _dalFilter (\ s a -> s{_dalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Disks/Insert.hs+2−2
@@ -22,7 +22,7 @@
22--
22--
23-- Creates a persistent disk in the specified project using the data in the
23-- Creates a persistent disk in the specified project using the data in the
24-- request. You can create a disk with a sourceImage, a sourceSnapshot, or
24-- request. You can create a disk with a sourceImage, a sourceSnapshot, or
25−-- create an empty 200 GB data disk by omitting all properties. You can
25+-- create an empty 500 GB data disk by omitting all properties. You can
26-- also create a disk that is larger than the default size by specifying
26-- also create a disk that is larger than the default size by specifying
27-- the sizeGb property.
27-- the sizeGb property.
28--
28--
@@ -62,7 +62,7 @@ type DisksInsertResource =
62
62
63-- | Creates a persistent disk in the specified project using the data in the
63-- | Creates a persistent disk in the specified project using the data in the
64-- request. You can create a disk with a sourceImage, a sourceSnapshot, or
64-- request. You can create a disk with a sourceImage, a sourceSnapshot, or
65−-- create an empty 200 GB data disk by omitting all properties. You can
65+-- create an empty 500 GB data disk by omitting all properties. You can
66-- also create a disk that is larger than the default size by specifying
66-- also create a disk that is larger than the default size by specifying
67-- the sizeGb property.
67-- the sizeGb property.
68--
68--
gogol-compute/gen/Network/Google/Resource/Compute/Disks/List.hs+9−10
@@ -117,17 +117,16 @@ dlZone = lens _dlZone (\ s a -> s{_dlZone = a})
117-- value is interpreted as a regular expression using RE2 syntax. The
117-- value is interpreted as a regular expression using RE2 syntax. The
118-- literal value must match the entire field. For example, to filter for
118-- literal value must match the entire field. For example, to filter for
119-- instances that do not have a name of example-instance, you would use
119-- instances that do not have a name of example-instance, you would use
120−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
120+-- filter=name ne example-instance. Compute Engine Beta API Only: When
121−-- use filtering in the Beta API, you can also filter on nested fields. For
121+-- filtering in the Beta API, you can also filter on nested fields. For
122-- example, you could filter on instances that have set the
122-- example, you could filter on instances that have set the
123−-- scheduling.automaticRestart field to true. In particular, use filtering
123+-- scheduling.automaticRestart field to true. Use filtering on nested
124−-- on nested fields to take advantage of instance labels to organize and
124+-- fields to take advantage of labels to organize and search for results
125−-- filter results based on label values. The Beta API also supports
125+-- based on label values. The Beta API also supports filtering on multiple
126−-- filtering on multiple expressions by providing each separate expression
126+-- expressions by providing each separate expression within parentheses.
127−-- within parentheses. For example, (scheduling.automaticRestart eq true)
127+-- For example, (scheduling.automaticRestart eq true) (zone eq
128−-- (zone eq us-central1-f). Multiple expressions are treated as AND
128+-- us-central1-f). Multiple expressions are treated as AND expressions,
129−-- expressions, meaning that resources must match all expressions to pass
129+-- meaning that resources must match all expressions to pass the filters.
130−-- the filters.
131dlFilter :: Lens' DisksList (Maybe Text)
130dlFilter :: Lens' DisksList (Maybe Text)
132dlFilter = lens _dlFilter (\ s a -> s{_dlFilter = a})
131dlFilter = lens _dlFilter (\ s a -> s{_dlFilter = a})
133
132
gogol-compute/gen/Network/Google/Resource/Compute/Disks/Resize.hsnew file+125
@@ -0,0 +1,125 @@
1+{-# LANGUAGE DataKinds #-}
2+{-# LANGUAGE DeriveDataTypeable #-}
3+{-# LANGUAGE DeriveGeneric #-}
4+{-# LANGUAGE FlexibleInstances #-}
5+{-# LANGUAGE NoImplicitPrelude #-}
6+{-# LANGUAGE OverloadedStrings #-}
7+{-# LANGUAGE RecordWildCards #-}
8+{-# LANGUAGE TypeFamilies #-}
9+{-# LANGUAGE TypeOperators #-}
10+
11+{-# OPTIONS_GHC -fno-warn-duplicate-exports #-}
12+{-# OPTIONS_GHC -fno-warn-unused-binds #-}
13+{-# OPTIONS_GHC -fno-warn-unused-imports #-}
14+
15+-- |
16+-- Module : Network.Google.Resource.Compute.Disks.Resize
17+-- Copyright : (c) 2015-2016 Brendan Hay
18+-- License : Mozilla Public License, v. 2.0.
19+-- Maintainer : Brendan Hay <brendan.g.hay@gmail.com>
20+-- Stability : auto-generated
21+-- Portability : non-portable (GHC extensions)
22+--
23+-- Resizes the specified persistent disk.
24+--
25+-- /See:/ <https://developers.google.com/compute/docs/reference/latest/ Compute Engine API Reference> for @compute.disks.resize@.
26+module Network.Google.Resource.Compute.Disks.Resize
27+ (
28+ -- * REST Resource
29+ DisksResizeResource
30+
31+ -- * Creating a Request
32+ , disksResize
33+ , DisksResize
34+
35+ -- * Request Lenses
36+ , drProject
37+ , drDisk
38+ , drZone
39+ , drPayload
40+ ) where
41+
42+import Network.Google.Compute.Types
43+import Network.Google.Prelude
44+
45+-- | A resource alias for @compute.disks.resize@ method which the
46+-- 'DisksResize' request conforms to.
47+type DisksResizeResource =
48+ "compute" :>
49+ "v1" :>
50+ "projects" :>
51+ Capture "project" Text :>
52+ "zones" :>
53+ Capture "zone" Text :>
54+ "disks" :>
55+ Capture "disk" Text :>
56+ "resize" :>
57+ QueryParam "alt" AltJSON :>
58+ ReqBody '[JSON] DisksResizeRequest :>
59+ Post '[JSON] Operation
60+
61+-- | Resizes the specified persistent disk.
62+--
63+-- /See:/ 'disksResize' smart constructor.
64+data DisksResize = DisksResize'
65+ { _drProject :: !Text
66+ , _drDisk :: !Text
67+ , _drZone :: !Text
68+ , _drPayload :: !DisksResizeRequest
69+ } deriving (Eq,Show,Data,Typeable,Generic)
70+
71+-- | Creates a value of 'DisksResize' with the minimum fields required to make a request.
72+--
73+-- Use one of the following lenses to modify other fields as desired:
74+--
75+-- * 'drProject'
76+--
77+-- * 'drDisk'
78+--
79+-- * 'drZone'
80+--
81+-- * 'drPayload'
82+disksResize
83+ :: Text -- ^ 'drProject'
84+ -> Text -- ^ 'drDisk'
85+ -> Text -- ^ 'drZone'
86+ -> DisksResizeRequest -- ^ 'drPayload'
87+ -> DisksResize
88+disksResize pDrProject_ pDrDisk_ pDrZone_ pDrPayload_ =
89+ DisksResize'
90+ { _drProject = pDrProject_
91+ , _drDisk = pDrDisk_
92+ , _drZone = pDrZone_
93+ , _drPayload = pDrPayload_
94+ }
95+
96+-- | Project ID for this request.
97+drProject :: Lens' DisksResize Text
98+drProject
99+ = lens _drProject (\ s a -> s{_drProject = a})
100+
101+-- | The name of the persistent disk.
102+drDisk :: Lens' DisksResize Text
103+drDisk = lens _drDisk (\ s a -> s{_drDisk = a})
104+
105+-- | The name of the zone for this request.
106+drZone :: Lens' DisksResize Text
107+drZone = lens _drZone (\ s a -> s{_drZone = a})
108+
109+-- | Multipart request metadata.
110+drPayload :: Lens' DisksResize DisksResizeRequest
111+drPayload
112+ = lens _drPayload (\ s a -> s{_drPayload = a})
113+
114+instance GoogleRequest DisksResize where
115+ type Rs DisksResize = Operation
116+ type Scopes DisksResize =
117+ '["https://www.googleapis.com/auth/cloud-platform",
118+ "https://www.googleapis.com/auth/compute"]
119+ requestClient DisksResize'{..}
120+ = go _drProject _drZone _drDisk (Just AltJSON)
121+ _drPayload
122+ computeService
123+ where go
124+ = buildClient (Proxy :: Proxy DisksResizeResource)
125+ mempty
gogol-compute/gen/Network/Google/Resource/Compute/Firewalls/List.hs+9−10
@@ -104,17 +104,16 @@ flProject
104-- value is interpreted as a regular expression using RE2 syntax. The
104-- value is interpreted as a regular expression using RE2 syntax. The
105-- literal value must match the entire field. For example, to filter for
105-- literal value must match the entire field. For example, to filter for
106-- instances that do not have a name of example-instance, you would use
106-- instances that do not have a name of example-instance, you would use
107−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
107+-- filter=name ne example-instance. Compute Engine Beta API Only: When
108−-- use filtering in the Beta API, you can also filter on nested fields. For
108+-- filtering in the Beta API, you can also filter on nested fields. For
109-- example, you could filter on instances that have set the
109-- example, you could filter on instances that have set the
110−-- scheduling.automaticRestart field to true. In particular, use filtering
110+-- scheduling.automaticRestart field to true. Use filtering on nested
111−-- on nested fields to take advantage of instance labels to organize and
111+-- fields to take advantage of labels to organize and search for results
112−-- filter results based on label values. The Beta API also supports
112+-- based on label values. The Beta API also supports filtering on multiple
113−-- filtering on multiple expressions by providing each separate expression
113+-- expressions by providing each separate expression within parentheses.
114−-- within parentheses. For example, (scheduling.automaticRestart eq true)
114+-- For example, (scheduling.automaticRestart eq true) (zone eq
115−-- (zone eq us-central1-f). Multiple expressions are treated as AND
115+-- us-central1-f). Multiple expressions are treated as AND expressions,
116−-- expressions, meaning that resources must match all expressions to pass
116+-- meaning that resources must match all expressions to pass the filters.
117−-- the filters.
118flFilter :: Lens' FirewallsList (Maybe Text)
117flFilter :: Lens' FirewallsList (Maybe Text)
119flFilter = lens _flFilter (\ s a -> s{_flFilter = a})
118flFilter = lens _flFilter (\ s a -> s{_flFilter = a})
120
119
gogol-compute/gen/Network/Google/Resource/Compute/ForwardingRules/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ fralProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119fralFilter :: Lens' ForwardingRulesAggregatedList (Maybe Text)
118fralFilter :: Lens' ForwardingRulesAggregatedList (Maybe Text)
120fralFilter
119fralFilter
121 = lens _fralFilter (\ s a -> s{_fralFilter = a})
120 = lens _fralFilter (\ s a -> s{_fralFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/ForwardingRules/List.hs+9−10
@@ -114,17 +114,16 @@ frlProject
114-- value is interpreted as a regular expression using RE2 syntax. The
114-- value is interpreted as a regular expression using RE2 syntax. The
115-- literal value must match the entire field. For example, to filter for
115-- literal value must match the entire field. For example, to filter for
116-- instances that do not have a name of example-instance, you would use
116-- instances that do not have a name of example-instance, you would use
117−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
117+-- filter=name ne example-instance. Compute Engine Beta API Only: When
118−-- use filtering in the Beta API, you can also filter on nested fields. For
118+-- filtering in the Beta API, you can also filter on nested fields. For
119-- example, you could filter on instances that have set the
119-- example, you could filter on instances that have set the
120−-- scheduling.automaticRestart field to true. In particular, use filtering
120+-- scheduling.automaticRestart field to true. Use filtering on nested
121−-- on nested fields to take advantage of instance labels to organize and
121+-- fields to take advantage of labels to organize and search for results
122−-- filter results based on label values. The Beta API also supports
122+-- based on label values. The Beta API also supports filtering on multiple
123−-- filtering on multiple expressions by providing each separate expression
123+-- expressions by providing each separate expression within parentheses.
124−-- within parentheses. For example, (scheduling.automaticRestart eq true)
124+-- For example, (scheduling.automaticRestart eq true) (zone eq
125−-- (zone eq us-central1-f). Multiple expressions are treated as AND
125+-- us-central1-f). Multiple expressions are treated as AND expressions,
126−-- expressions, meaning that resources must match all expressions to pass
126+-- meaning that resources must match all expressions to pass the filters.
127−-- the filters.
128frlFilter :: Lens' ForwardingRulesList (Maybe Text)
127frlFilter :: Lens' ForwardingRulesList (Maybe Text)
129frlFilter
128frlFilter
130 = lens _frlFilter (\ s a -> s{_frlFilter = a})
129 = lens _frlFilter (\ s a -> s{_frlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/GlobalAddresses/List.hs+9−10
@@ -104,17 +104,16 @@ galProject
104-- value is interpreted as a regular expression using RE2 syntax. The
104-- value is interpreted as a regular expression using RE2 syntax. The
105-- literal value must match the entire field. For example, to filter for
105-- literal value must match the entire field. For example, to filter for
106-- instances that do not have a name of example-instance, you would use
106-- instances that do not have a name of example-instance, you would use
107−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
107+-- filter=name ne example-instance. Compute Engine Beta API Only: When
108−-- use filtering in the Beta API, you can also filter on nested fields. For
108+-- filtering in the Beta API, you can also filter on nested fields. For
109-- example, you could filter on instances that have set the
109-- example, you could filter on instances that have set the
110−-- scheduling.automaticRestart field to true. In particular, use filtering
110+-- scheduling.automaticRestart field to true. Use filtering on nested
111−-- on nested fields to take advantage of instance labels to organize and
111+-- fields to take advantage of labels to organize and search for results
112−-- filter results based on label values. The Beta API also supports
112+-- based on label values. The Beta API also supports filtering on multiple
113−-- filtering on multiple expressions by providing each separate expression
113+-- expressions by providing each separate expression within parentheses.
114−-- within parentheses. For example, (scheduling.automaticRestart eq true)
114+-- For example, (scheduling.automaticRestart eq true) (zone eq
115−-- (zone eq us-central1-f). Multiple expressions are treated as AND
115+-- us-central1-f). Multiple expressions are treated as AND expressions,
116−-- expressions, meaning that resources must match all expressions to pass
116+-- meaning that resources must match all expressions to pass the filters.
117−-- the filters.
118galFilter :: Lens' GlobalAddressesList (Maybe Text)
117galFilter :: Lens' GlobalAddressesList (Maybe Text)
119galFilter
118galFilter
120 = lens _galFilter (\ s a -> s{_galFilter = a})
119 = lens _galFilter (\ s a -> s{_galFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/GlobalForwardingRules/List.hs+9−10
@@ -107,17 +107,16 @@ gfrlProject
107-- value is interpreted as a regular expression using RE2 syntax. The
107-- value is interpreted as a regular expression using RE2 syntax. The
108-- literal value must match the entire field. For example, to filter for
108-- literal value must match the entire field. For example, to filter for
109-- instances that do not have a name of example-instance, you would use
109-- instances that do not have a name of example-instance, you would use
110−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
110+-- filter=name ne example-instance. Compute Engine Beta API Only: When
111−-- use filtering in the Beta API, you can also filter on nested fields. For
111+-- filtering in the Beta API, you can also filter on nested fields. For
112-- example, you could filter on instances that have set the
112-- example, you could filter on instances that have set the
113−-- scheduling.automaticRestart field to true. In particular, use filtering
113+-- scheduling.automaticRestart field to true. Use filtering on nested
114−-- on nested fields to take advantage of instance labels to organize and
114+-- fields to take advantage of labels to organize and search for results
115−-- filter results based on label values. The Beta API also supports
115+-- based on label values. The Beta API also supports filtering on multiple
116−-- filtering on multiple expressions by providing each separate expression
116+-- expressions by providing each separate expression within parentheses.
117−-- within parentheses. For example, (scheduling.automaticRestart eq true)
117+-- For example, (scheduling.automaticRestart eq true) (zone eq
118−-- (zone eq us-central1-f). Multiple expressions are treated as AND
118+-- us-central1-f). Multiple expressions are treated as AND expressions,
119−-- expressions, meaning that resources must match all expressions to pass
119+-- meaning that resources must match all expressions to pass the filters.
120−-- the filters.
121gfrlFilter :: Lens' GlobalForwardingRulesList (Maybe Text)
120gfrlFilter :: Lens' GlobalForwardingRulesList (Maybe Text)
122gfrlFilter
121gfrlFilter
123 = lens _gfrlFilter (\ s a -> s{_gfrlFilter = a})
122 = lens _gfrlFilter (\ s a -> s{_gfrlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/GlobalOperations/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ goalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119goalFilter :: Lens' GlobalOperationsAggregatedList (Maybe Text)
118goalFilter :: Lens' GlobalOperationsAggregatedList (Maybe Text)
120goalFilter
119goalFilter
121 = lens _goalFilter (\ s a -> s{_goalFilter = a})
120 = lens _goalFilter (\ s a -> s{_goalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/GlobalOperations/List.hs+9−10
@@ -106,17 +106,16 @@ golProject
106-- value is interpreted as a regular expression using RE2 syntax. The
106-- value is interpreted as a regular expression using RE2 syntax. The
107-- literal value must match the entire field. For example, to filter for
107-- literal value must match the entire field. For example, to filter for
108-- instances that do not have a name of example-instance, you would use
108-- instances that do not have a name of example-instance, you would use
109−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
109+-- filter=name ne example-instance. Compute Engine Beta API Only: When
110−-- use filtering in the Beta API, you can also filter on nested fields. For
110+-- filtering in the Beta API, you can also filter on nested fields. For
111-- example, you could filter on instances that have set the
111-- example, you could filter on instances that have set the
112−-- scheduling.automaticRestart field to true. In particular, use filtering
112+-- scheduling.automaticRestart field to true. Use filtering on nested
113−-- on nested fields to take advantage of instance labels to organize and
113+-- fields to take advantage of labels to organize and search for results
114−-- filter results based on label values. The Beta API also supports
114+-- based on label values. The Beta API also supports filtering on multiple
115−-- filtering on multiple expressions by providing each separate expression
115+-- expressions by providing each separate expression within parentheses.
116−-- within parentheses. For example, (scheduling.automaticRestart eq true)
116+-- For example, (scheduling.automaticRestart eq true) (zone eq
117−-- (zone eq us-central1-f). Multiple expressions are treated as AND
117+-- us-central1-f). Multiple expressions are treated as AND expressions,
118−-- expressions, meaning that resources must match all expressions to pass
118+-- meaning that resources must match all expressions to pass the filters.
119−-- the filters.
120golFilter :: Lens' GlobalOperationsList (Maybe Text)
119golFilter :: Lens' GlobalOperationsList (Maybe Text)
121golFilter
120golFilter
122 = lens _golFilter (\ s a -> s{_golFilter = a})
121 = lens _golFilter (\ s a -> s{_golFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/HTTPHealthChecks/List.hs+9−10
@@ -108,17 +108,16 @@ httphclProject
108-- value is interpreted as a regular expression using RE2 syntax. The
108-- value is interpreted as a regular expression using RE2 syntax. The
109-- literal value must match the entire field. For example, to filter for
109-- literal value must match the entire field. For example, to filter for
110-- instances that do not have a name of example-instance, you would use
110-- instances that do not have a name of example-instance, you would use
111−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
111+-- filter=name ne example-instance. Compute Engine Beta API Only: When
112−-- use filtering in the Beta API, you can also filter on nested fields. For
112+-- filtering in the Beta API, you can also filter on nested fields. For
113-- example, you could filter on instances that have set the
113-- example, you could filter on instances that have set the
114−-- scheduling.automaticRestart field to true. In particular, use filtering
114+-- scheduling.automaticRestart field to true. Use filtering on nested
115−-- on nested fields to take advantage of instance labels to organize and
115+-- fields to take advantage of labels to organize and search for results
116−-- filter results based on label values. The Beta API also supports
116+-- based on label values. The Beta API also supports filtering on multiple
117−-- filtering on multiple expressions by providing each separate expression
117+-- expressions by providing each separate expression within parentheses.
118−-- within parentheses. For example, (scheduling.automaticRestart eq true)
118+-- For example, (scheduling.automaticRestart eq true) (zone eq
119−-- (zone eq us-central1-f). Multiple expressions are treated as AND
119+-- us-central1-f). Multiple expressions are treated as AND expressions,
120−-- expressions, meaning that resources must match all expressions to pass
120+-- meaning that resources must match all expressions to pass the filters.
121−-- the filters.
122httphclFilter :: Lens' HTTPHealthChecksList (Maybe Text)
121httphclFilter :: Lens' HTTPHealthChecksList (Maybe Text)
123httphclFilter
122httphclFilter
124 = lens _httphclFilter
123 = lens _httphclFilter
gogol-compute/gen/Network/Google/Resource/Compute/HTTPSHealthChecks/List.hs+9−10
@@ -107,17 +107,16 @@ hhclProject
107-- value is interpreted as a regular expression using RE2 syntax. The
107-- value is interpreted as a regular expression using RE2 syntax. The
108-- literal value must match the entire field. For example, to filter for
108-- literal value must match the entire field. For example, to filter for
109-- instances that do not have a name of example-instance, you would use
109-- instances that do not have a name of example-instance, you would use
110−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
110+-- filter=name ne example-instance. Compute Engine Beta API Only: When
111−-- use filtering in the Beta API, you can also filter on nested fields. For
111+-- filtering in the Beta API, you can also filter on nested fields. For
112-- example, you could filter on instances that have set the
112-- example, you could filter on instances that have set the
113−-- scheduling.automaticRestart field to true. In particular, use filtering
113+-- scheduling.automaticRestart field to true. Use filtering on nested
114−-- on nested fields to take advantage of instance labels to organize and
114+-- fields to take advantage of labels to organize and search for results
115−-- filter results based on label values. The Beta API also supports
115+-- based on label values. The Beta API also supports filtering on multiple
116−-- filtering on multiple expressions by providing each separate expression
116+-- expressions by providing each separate expression within parentheses.
117−-- within parentheses. For example, (scheduling.automaticRestart eq true)
117+-- For example, (scheduling.automaticRestart eq true) (zone eq
118−-- (zone eq us-central1-f). Multiple expressions are treated as AND
118+-- us-central1-f). Multiple expressions are treated as AND expressions,
119−-- expressions, meaning that resources must match all expressions to pass
119+-- meaning that resources must match all expressions to pass the filters.
120−-- the filters.
121hhclFilter :: Lens' HTTPSHealthChecksList (Maybe Text)
120hhclFilter :: Lens' HTTPSHealthChecksList (Maybe Text)
122hhclFilter
121hhclFilter
123 = lens _hhclFilter (\ s a -> s{_hhclFilter = a})
122 = lens _hhclFilter (\ s a -> s{_hhclFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Images/GetFromFamily.hsnew file+105
@@ -0,0 +1,105 @@
1+{-# LANGUAGE DataKinds #-}
2+{-# LANGUAGE DeriveDataTypeable #-}
3+{-# LANGUAGE DeriveGeneric #-}
4+{-# LANGUAGE FlexibleInstances #-}
5+{-# LANGUAGE NoImplicitPrelude #-}
6+{-# LANGUAGE OverloadedStrings #-}
7+{-# LANGUAGE RecordWildCards #-}
8+{-# LANGUAGE TypeFamilies #-}
9+{-# LANGUAGE TypeOperators #-}
10+
11+{-# OPTIONS_GHC -fno-warn-duplicate-exports #-}
12+{-# OPTIONS_GHC -fno-warn-unused-binds #-}
13+{-# OPTIONS_GHC -fno-warn-unused-imports #-}
14+
15+-- |
16+-- Module : Network.Google.Resource.Compute.Images.GetFromFamily
17+-- Copyright : (c) 2015-2016 Brendan Hay
18+-- License : Mozilla Public License, v. 2.0.
19+-- Maintainer : Brendan Hay <brendan.g.hay@gmail.com>
20+-- Stability : auto-generated
21+-- Portability : non-portable (GHC extensions)
22+--
23+-- Returns the latest image that is part of an image family and is not
24+-- deprecated.
25+--
26+-- /See:/ <https://developers.google.com/compute/docs/reference/latest/ Compute Engine API Reference> for @compute.images.getFromFamily@.
27+module Network.Google.Resource.Compute.Images.GetFromFamily
28+ (
29+ -- * REST Resource
30+ ImagesGetFromFamilyResource
31+
32+ -- * Creating a Request
33+ , imagesGetFromFamily
34+ , ImagesGetFromFamily
35+
36+ -- * Request Lenses
37+ , igffProject
38+ , igffFamily
39+ ) where
40+
41+import Network.Google.Compute.Types
42+import Network.Google.Prelude
43+
44+-- | A resource alias for @compute.images.getFromFamily@ method which the
45+-- 'ImagesGetFromFamily' request conforms to.
46+type ImagesGetFromFamilyResource =
47+ "compute" :>
48+ "v1" :>
49+ "projects" :>
50+ Capture "project" Text :>
51+ "global" :>
52+ "images" :>
53+ "family" :>
54+ Capture "family" Text :>
55+ QueryParam "alt" AltJSON :> Get '[JSON] Image
56+
57+-- | Returns the latest image that is part of an image family and is not
58+-- deprecated.
59+--
60+-- /See:/ 'imagesGetFromFamily' smart constructor.
61+data ImagesGetFromFamily = ImagesGetFromFamily'
62+ { _igffProject :: !Text
63+ , _igffFamily :: !Text
64+ } deriving (Eq,Show,Data,Typeable,Generic)
65+
66+-- | Creates a value of 'ImagesGetFromFamily' with the minimum fields required to make a request.
67+--
68+-- Use one of the following lenses to modify other fields as desired:
69+--
70+-- * 'igffProject'
71+--
72+-- * 'igffFamily'
73+imagesGetFromFamily
74+ :: Text -- ^ 'igffProject'
75+ -> Text -- ^ 'igffFamily'
76+ -> ImagesGetFromFamily
77+imagesGetFromFamily pIgffProject_ pIgffFamily_ =
78+ ImagesGetFromFamily'
79+ { _igffProject = pIgffProject_
80+ , _igffFamily = pIgffFamily_
81+ }
82+
83+-- | Project ID for this request.
84+igffProject :: Lens' ImagesGetFromFamily Text
85+igffProject
86+ = lens _igffProject (\ s a -> s{_igffProject = a})
87+
88+-- | Name of the image resource to return.
89+igffFamily :: Lens' ImagesGetFromFamily Text
90+igffFamily
91+ = lens _igffFamily (\ s a -> s{_igffFamily = a})
92+
93+instance GoogleRequest ImagesGetFromFamily where
94+ type Rs ImagesGetFromFamily = Image
95+ type Scopes ImagesGetFromFamily =
96+ '["https://www.googleapis.com/auth/cloud-platform",
97+ "https://www.googleapis.com/auth/compute",
98+ "https://www.googleapis.com/auth/compute.readonly"]
99+ requestClient ImagesGetFromFamily'{..}
100+ = go _igffProject _igffFamily (Just AltJSON)
101+ computeService
102+ where go
103+ = buildClient
104+ (Proxy :: Proxy ImagesGetFromFamilyResource)
105+ mempty
gogol-compute/gen/Network/Google/Resource/Compute/Images/List.hs+9−10
@@ -116,17 +116,16 @@ illProject
116-- value is interpreted as a regular expression using RE2 syntax. The
116-- value is interpreted as a regular expression using RE2 syntax. The
117-- literal value must match the entire field. For example, to filter for
117-- literal value must match the entire field. For example, to filter for
118-- instances that do not have a name of example-instance, you would use
118-- instances that do not have a name of example-instance, you would use
119−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
119+-- filter=name ne example-instance. Compute Engine Beta API Only: When
120−-- use filtering in the Beta API, you can also filter on nested fields. For
120+-- filtering in the Beta API, you can also filter on nested fields. For
121-- example, you could filter on instances that have set the
121-- example, you could filter on instances that have set the
122−-- scheduling.automaticRestart field to true. In particular, use filtering
122+-- scheduling.automaticRestart field to true. Use filtering on nested
123−-- on nested fields to take advantage of instance labels to organize and
123+-- fields to take advantage of labels to organize and search for results
124−-- filter results based on label values. The Beta API also supports
124+-- based on label values. The Beta API also supports filtering on multiple
125−-- filtering on multiple expressions by providing each separate expression
125+-- expressions by providing each separate expression within parentheses.
126−-- within parentheses. For example, (scheduling.automaticRestart eq true)
126+-- For example, (scheduling.automaticRestart eq true) (zone eq
127−-- (zone eq us-central1-f). Multiple expressions are treated as AND
127+-- us-central1-f). Multiple expressions are treated as AND expressions,
128−-- expressions, meaning that resources must match all expressions to pass
128+-- meaning that resources must match all expressions to pass the filters.
129−-- the filters.
130illFilter :: Lens' ImagesList (Maybe Text)
129illFilter :: Lens' ImagesList (Maybe Text)
131illFilter
130illFilter
132 = lens _illFilter (\ s a -> s{_illFilter = a})
131 = lens _illFilter (\ s a -> s{_illFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/InstanceGroupManagers/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ igmalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119igmalFilter :: Lens' InstanceGroupManagersAggregatedList (Maybe Text)
118igmalFilter :: Lens' InstanceGroupManagersAggregatedList (Maybe Text)
120igmalFilter
119igmalFilter
121 = lens _igmalFilter (\ s a -> s{_igmalFilter = a})
120 = lens _igmalFilter (\ s a -> s{_igmalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/InstanceGroupManagers/List.hs+9−10
@@ -118,17 +118,16 @@ igmlZone = lens _igmlZone (\ s a -> s{_igmlZone = a})
118-- value is interpreted as a regular expression using RE2 syntax. The
118-- value is interpreted as a regular expression using RE2 syntax. The
119-- literal value must match the entire field. For example, to filter for
119-- literal value must match the entire field. For example, to filter for
120-- instances that do not have a name of example-instance, you would use
120-- instances that do not have a name of example-instance, you would use
121−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
121+-- filter=name ne example-instance. Compute Engine Beta API Only: When
122−-- use filtering in the Beta API, you can also filter on nested fields. For
122+-- filtering in the Beta API, you can also filter on nested fields. For
123-- example, you could filter on instances that have set the
123-- example, you could filter on instances that have set the
124−-- scheduling.automaticRestart field to true. In particular, use filtering
124+-- scheduling.automaticRestart field to true. Use filtering on nested
125−-- on nested fields to take advantage of instance labels to organize and
125+-- fields to take advantage of labels to organize and search for results
126−-- filter results based on label values. The Beta API also supports
126+-- based on label values. The Beta API also supports filtering on multiple
127−-- filtering on multiple expressions by providing each separate expression
127+-- expressions by providing each separate expression within parentheses.
128−-- within parentheses. For example, (scheduling.automaticRestart eq true)
128+-- For example, (scheduling.automaticRestart eq true) (zone eq
129−-- (zone eq us-central1-f). Multiple expressions are treated as AND
129+-- us-central1-f). Multiple expressions are treated as AND expressions,
130−-- expressions, meaning that resources must match all expressions to pass
130+-- meaning that resources must match all expressions to pass the filters.
131−-- the filters.
132igmlFilter :: Lens' InstanceGroupManagersList (Maybe Text)
131igmlFilter :: Lens' InstanceGroupManagersList (Maybe Text)
133igmlFilter
132igmlFilter
134 = lens _igmlFilter (\ s a -> s{_igmlFilter = a})
133 = lens _igmlFilter (\ s a -> s{_igmlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/InstanceGroups/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ igalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119igalFilter :: Lens' InstanceGroupsAggregatedList (Maybe Text)
118igalFilter :: Lens' InstanceGroupsAggregatedList (Maybe Text)
120igalFilter
119igalFilter
121 = lens _igalFilter (\ s a -> s{_igalFilter = a})
120 = lens _igalFilter (\ s a -> s{_igalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/InstanceGroups/List.hs+9−10
@@ -118,17 +118,16 @@ iglZone = lens _iglZone (\ s a -> s{_iglZone = a})
118-- value is interpreted as a regular expression using RE2 syntax. The
118-- value is interpreted as a regular expression using RE2 syntax. The
119-- literal value must match the entire field. For example, to filter for
119-- literal value must match the entire field. For example, to filter for
120-- instances that do not have a name of example-instance, you would use
120-- instances that do not have a name of example-instance, you would use
121−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
121+-- filter=name ne example-instance. Compute Engine Beta API Only: When
122−-- use filtering in the Beta API, you can also filter on nested fields. For
122+-- filtering in the Beta API, you can also filter on nested fields. For
123-- example, you could filter on instances that have set the
123-- example, you could filter on instances that have set the
124−-- scheduling.automaticRestart field to true. In particular, use filtering
124+-- scheduling.automaticRestart field to true. Use filtering on nested
125−-- on nested fields to take advantage of instance labels to organize and
125+-- fields to take advantage of labels to organize and search for results
126−-- filter results based on label values. The Beta API also supports
126+-- based on label values. The Beta API also supports filtering on multiple
127−-- filtering on multiple expressions by providing each separate expression
127+-- expressions by providing each separate expression within parentheses.
128−-- within parentheses. For example, (scheduling.automaticRestart eq true)
128+-- For example, (scheduling.automaticRestart eq true) (zone eq
129−-- (zone eq us-central1-f). Multiple expressions are treated as AND
129+-- us-central1-f). Multiple expressions are treated as AND expressions,
130−-- expressions, meaning that resources must match all expressions to pass
130+-- meaning that resources must match all expressions to pass the filters.
131−-- the filters.
132iglFilter :: Lens' InstanceGroupsList (Maybe Text)
131iglFilter :: Lens' InstanceGroupsList (Maybe Text)
133iglFilter
132iglFilter
134 = lens _iglFilter (\ s a -> s{_iglFilter = a})
133 = lens _iglFilter (\ s a -> s{_iglFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/InstanceGroups/ListInstances.hs+9−10
@@ -137,17 +137,16 @@ igliPayload
137-- value is interpreted as a regular expression using RE2 syntax. The
137-- value is interpreted as a regular expression using RE2 syntax. The
138-- literal value must match the entire field. For example, to filter for
138-- literal value must match the entire field. For example, to filter for
139-- instances that do not have a name of example-instance, you would use
139-- instances that do not have a name of example-instance, you would use
140−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
140+-- filter=name ne example-instance. Compute Engine Beta API Only: When
141−-- use filtering in the Beta API, you can also filter on nested fields. For
141+-- filtering in the Beta API, you can also filter on nested fields. For
142-- example, you could filter on instances that have set the
142-- example, you could filter on instances that have set the
143−-- scheduling.automaticRestart field to true. In particular, use filtering
143+-- scheduling.automaticRestart field to true. Use filtering on nested
144−-- on nested fields to take advantage of instance labels to organize and
144+-- fields to take advantage of labels to organize and search for results
145−-- filter results based on label values. The Beta API also supports
145+-- based on label values. The Beta API also supports filtering on multiple
146−-- filtering on multiple expressions by providing each separate expression
146+-- expressions by providing each separate expression within parentheses.
147−-- within parentheses. For example, (scheduling.automaticRestart eq true)
147+-- For example, (scheduling.automaticRestart eq true) (zone eq
148−-- (zone eq us-central1-f). Multiple expressions are treated as AND
148+-- us-central1-f). Multiple expressions are treated as AND expressions,
149−-- expressions, meaning that resources must match all expressions to pass
149+-- meaning that resources must match all expressions to pass the filters.
150−-- the filters.
151igliFilter :: Lens' InstanceGroupsListInstances' (Maybe Text)
150igliFilter :: Lens' InstanceGroupsListInstances' (Maybe Text)
152igliFilter
151igliFilter
153 = lens _igliFilter (\ s a -> s{_igliFilter = a})
152 = lens _igliFilter (\ s a -> s{_igliFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/InstanceTemplates/List.hs+9−10
@@ -107,17 +107,16 @@ itlProject
107-- value is interpreted as a regular expression using RE2 syntax. The
107-- value is interpreted as a regular expression using RE2 syntax. The
108-- literal value must match the entire field. For example, to filter for
108-- literal value must match the entire field. For example, to filter for
109-- instances that do not have a name of example-instance, you would use
109-- instances that do not have a name of example-instance, you would use
110−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
110+-- filter=name ne example-instance. Compute Engine Beta API Only: When
111−-- use filtering in the Beta API, you can also filter on nested fields. For
111+-- filtering in the Beta API, you can also filter on nested fields. For
112-- example, you could filter on instances that have set the
112-- example, you could filter on instances that have set the
113−-- scheduling.automaticRestart field to true. In particular, use filtering
113+-- scheduling.automaticRestart field to true. Use filtering on nested
114−-- on nested fields to take advantage of instance labels to organize and
114+-- fields to take advantage of labels to organize and search for results
115−-- filter results based on label values. The Beta API also supports
115+-- based on label values. The Beta API also supports filtering on multiple
116−-- filtering on multiple expressions by providing each separate expression
116+-- expressions by providing each separate expression within parentheses.
117−-- within parentheses. For example, (scheduling.automaticRestart eq true)
117+-- For example, (scheduling.automaticRestart eq true) (zone eq
118−-- (zone eq us-central1-f). Multiple expressions are treated as AND
118+-- us-central1-f). Multiple expressions are treated as AND expressions,
119−-- expressions, meaning that resources must match all expressions to pass
119+-- meaning that resources must match all expressions to pass the filters.
120−-- the filters.
121itlFilter :: Lens' InstanceTemplatesList (Maybe Text)
120itlFilter :: Lens' InstanceTemplatesList (Maybe Text)
122itlFilter
121itlFilter
123 = lens _itlFilter (\ s a -> s{_itlFilter = a})
122 = lens _itlFilter (\ s a -> s{_itlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Instances/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ ialProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119ialFilter :: Lens' InstancesAggregatedList (Maybe Text)
118ialFilter :: Lens' InstancesAggregatedList (Maybe Text)
120ialFilter
119ialFilter
121 = lens _ialFilter (\ s a -> s{_ialFilter = a})
120 = lens _ialFilter (\ s a -> s{_ialFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Instances/List.hs+9−10
@@ -115,17 +115,16 @@ ilZone = lens _ilZone (\ s a -> s{_ilZone = a})
115-- value is interpreted as a regular expression using RE2 syntax. The
115-- value is interpreted as a regular expression using RE2 syntax. The
116-- literal value must match the entire field. For example, to filter for
116-- literal value must match the entire field. For example, to filter for
117-- instances that do not have a name of example-instance, you would use
117-- instances that do not have a name of example-instance, you would use
118−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
118+-- filter=name ne example-instance. Compute Engine Beta API Only: When
119−-- use filtering in the Beta API, you can also filter on nested fields. For
119+-- filtering in the Beta API, you can also filter on nested fields. For
120-- example, you could filter on instances that have set the
120-- example, you could filter on instances that have set the
121−-- scheduling.automaticRestart field to true. In particular, use filtering
121+-- scheduling.automaticRestart field to true. Use filtering on nested
122−-- on nested fields to take advantage of instance labels to organize and
122+-- fields to take advantage of labels to organize and search for results
123−-- filter results based on label values. The Beta API also supports
123+-- based on label values. The Beta API also supports filtering on multiple
124−-- filtering on multiple expressions by providing each separate expression
124+-- expressions by providing each separate expression within parentheses.
125−-- within parentheses. For example, (scheduling.automaticRestart eq true)
125+-- For example, (scheduling.automaticRestart eq true) (zone eq
126−-- (zone eq us-central1-f). Multiple expressions are treated as AND
126+-- us-central1-f). Multiple expressions are treated as AND expressions,
127−-- expressions, meaning that resources must match all expressions to pass
127+-- meaning that resources must match all expressions to pass the filters.
128−-- the filters.
129ilFilter :: Lens' InstancesList (Maybe Text)
128ilFilter :: Lens' InstancesList (Maybe Text)
130ilFilter = lens _ilFilter (\ s a -> s{_ilFilter = a})
129ilFilter = lens _ilFilter (\ s a -> s{_ilFilter = a})
131
130
gogol-compute/gen/Network/Google/Resource/Compute/MachineTypes/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ mtalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119mtalFilter :: Lens' MachineTypesAggregatedList (Maybe Text)
118mtalFilter :: Lens' MachineTypesAggregatedList (Maybe Text)
120mtalFilter
119mtalFilter
121 = lens _mtalFilter (\ s a -> s{_mtalFilter = a})
120 = lens _mtalFilter (\ s a -> s{_mtalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/MachineTypes/List.hs+9−10
@@ -116,17 +116,16 @@ mtlZone = lens _mtlZone (\ s a -> s{_mtlZone = a})
116-- value is interpreted as a regular expression using RE2 syntax. The
116-- value is interpreted as a regular expression using RE2 syntax. The
117-- literal value must match the entire field. For example, to filter for
117-- literal value must match the entire field. For example, to filter for
118-- instances that do not have a name of example-instance, you would use
118-- instances that do not have a name of example-instance, you would use
119−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
119+-- filter=name ne example-instance. Compute Engine Beta API Only: When
120−-- use filtering in the Beta API, you can also filter on nested fields. For
120+-- filtering in the Beta API, you can also filter on nested fields. For
121-- example, you could filter on instances that have set the
121-- example, you could filter on instances that have set the
122−-- scheduling.automaticRestart field to true. In particular, use filtering
122+-- scheduling.automaticRestart field to true. Use filtering on nested
123−-- on nested fields to take advantage of instance labels to organize and
123+-- fields to take advantage of labels to organize and search for results
124−-- filter results based on label values. The Beta API also supports
124+-- based on label values. The Beta API also supports filtering on multiple
125−-- filtering on multiple expressions by providing each separate expression
125+-- expressions by providing each separate expression within parentheses.
126−-- within parentheses. For example, (scheduling.automaticRestart eq true)
126+-- For example, (scheduling.automaticRestart eq true) (zone eq
127−-- (zone eq us-central1-f). Multiple expressions are treated as AND
127+-- us-central1-f). Multiple expressions are treated as AND expressions,
128−-- expressions, meaning that resources must match all expressions to pass
128+-- meaning that resources must match all expressions to pass the filters.
129−-- the filters.
130mtlFilter :: Lens' MachineTypesList (Maybe Text)
129mtlFilter :: Lens' MachineTypesList (Maybe Text)
131mtlFilter
130mtlFilter
132 = lens _mtlFilter (\ s a -> s{_mtlFilter = a})
131 = lens _mtlFilter (\ s a -> s{_mtlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Networks/List.hs+9−10
@@ -104,17 +104,16 @@ nlProject
104-- value is interpreted as a regular expression using RE2 syntax. The
104-- value is interpreted as a regular expression using RE2 syntax. The
105-- literal value must match the entire field. For example, to filter for
105-- literal value must match the entire field. For example, to filter for
106-- instances that do not have a name of example-instance, you would use
106-- instances that do not have a name of example-instance, you would use
107−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
107+-- filter=name ne example-instance. Compute Engine Beta API Only: When
108−-- use filtering in the Beta API, you can also filter on nested fields. For
108+-- filtering in the Beta API, you can also filter on nested fields. For
109-- example, you could filter on instances that have set the
109-- example, you could filter on instances that have set the
110−-- scheduling.automaticRestart field to true. In particular, use filtering
110+-- scheduling.automaticRestart field to true. Use filtering on nested
111−-- on nested fields to take advantage of instance labels to organize and
111+-- fields to take advantage of labels to organize and search for results
112−-- filter results based on label values. The Beta API also supports
112+-- based on label values. The Beta API also supports filtering on multiple
113−-- filtering on multiple expressions by providing each separate expression
113+-- expressions by providing each separate expression within parentheses.
114−-- within parentheses. For example, (scheduling.automaticRestart eq true)
114+-- For example, (scheduling.automaticRestart eq true) (zone eq
115−-- (zone eq us-central1-f). Multiple expressions are treated as AND
115+-- us-central1-f). Multiple expressions are treated as AND expressions,
116−-- expressions, meaning that resources must match all expressions to pass
116+-- meaning that resources must match all expressions to pass the filters.
117−-- the filters.
118nlFilter :: Lens' NetworksList (Maybe Text)
117nlFilter :: Lens' NetworksList (Maybe Text)
119nlFilter = lens _nlFilter (\ s a -> s{_nlFilter = a})
118nlFilter = lens _nlFilter (\ s a -> s{_nlFilter = a})
120
119
gogol-compute/gen/Network/Google/Resource/Compute/RegionOperations/List.hs+9−10
@@ -113,17 +113,16 @@ rolProject
113-- value is interpreted as a regular expression using RE2 syntax. The
113-- value is interpreted as a regular expression using RE2 syntax. The
114-- literal value must match the entire field. For example, to filter for
114-- literal value must match the entire field. For example, to filter for
115-- instances that do not have a name of example-instance, you would use
115-- instances that do not have a name of example-instance, you would use
116−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
116+-- filter=name ne example-instance. Compute Engine Beta API Only: When
117−-- use filtering in the Beta API, you can also filter on nested fields. For
117+-- filtering in the Beta API, you can also filter on nested fields. For
118-- example, you could filter on instances that have set the
118-- example, you could filter on instances that have set the
119−-- scheduling.automaticRestart field to true. In particular, use filtering
119+-- scheduling.automaticRestart field to true. Use filtering on nested
120−-- on nested fields to take advantage of instance labels to organize and
120+-- fields to take advantage of labels to organize and search for results
121−-- filter results based on label values. The Beta API also supports
121+-- based on label values. The Beta API also supports filtering on multiple
122−-- filtering on multiple expressions by providing each separate expression
122+-- expressions by providing each separate expression within parentheses.
123−-- within parentheses. For example, (scheduling.automaticRestart eq true)
123+-- For example, (scheduling.automaticRestart eq true) (zone eq
124−-- (zone eq us-central1-f). Multiple expressions are treated as AND
124+-- us-central1-f). Multiple expressions are treated as AND expressions,
125−-- expressions, meaning that resources must match all expressions to pass
125+-- meaning that resources must match all expressions to pass the filters.
126−-- the filters.
127rolFilter :: Lens' RegionOperationsList (Maybe Text)
126rolFilter :: Lens' RegionOperationsList (Maybe Text)
128rolFilter
127rolFilter
129 = lens _rolFilter (\ s a -> s{_rolFilter = a})
128 = lens _rolFilter (\ s a -> s{_rolFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Regions/List.hs+9−10
@@ -104,17 +104,16 @@ rProject = lens _rProject (\ s a -> s{_rProject = a})
104-- value is interpreted as a regular expression using RE2 syntax. The
104-- value is interpreted as a regular expression using RE2 syntax. The
105-- literal value must match the entire field. For example, to filter for
105-- literal value must match the entire field. For example, to filter for
106-- instances that do not have a name of example-instance, you would use
106-- instances that do not have a name of example-instance, you would use
107−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
107+-- filter=name ne example-instance. Compute Engine Beta API Only: When
108−-- use filtering in the Beta API, you can also filter on nested fields. For
108+-- filtering in the Beta API, you can also filter on nested fields. For
109-- example, you could filter on instances that have set the
109-- example, you could filter on instances that have set the
110−-- scheduling.automaticRestart field to true. In particular, use filtering
110+-- scheduling.automaticRestart field to true. Use filtering on nested
111−-- on nested fields to take advantage of instance labels to organize and
111+-- fields to take advantage of labels to organize and search for results
112−-- filter results based on label values. The Beta API also supports
112+-- based on label values. The Beta API also supports filtering on multiple
113−-- filtering on multiple expressions by providing each separate expression
113+-- expressions by providing each separate expression within parentheses.
114−-- within parentheses. For example, (scheduling.automaticRestart eq true)
114+-- For example, (scheduling.automaticRestart eq true) (zone eq
115−-- (zone eq us-central1-f). Multiple expressions are treated as AND
115+-- us-central1-f). Multiple expressions are treated as AND expressions,
116−-- expressions, meaning that resources must match all expressions to pass
116+-- meaning that resources must match all expressions to pass the filters.
117−-- the filters.
118rFilter :: Lens' RegionsList (Maybe Text)
117rFilter :: Lens' RegionsList (Maybe Text)
119rFilter = lens _rFilter (\ s a -> s{_rFilter = a})
118rFilter = lens _rFilter (\ s a -> s{_rFilter = a})
120
119
gogol-compute/gen/Network/Google/Resource/Compute/Routes/List.hs+9−10
@@ -106,17 +106,16 @@ rlProject
106-- value is interpreted as a regular expression using RE2 syntax. The
106-- value is interpreted as a regular expression using RE2 syntax. The
107-- literal value must match the entire field. For example, to filter for
107-- literal value must match the entire field. For example, to filter for
108-- instances that do not have a name of example-instance, you would use
108-- instances that do not have a name of example-instance, you would use
109−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
109+-- filter=name ne example-instance. Compute Engine Beta API Only: When
110−-- use filtering in the Beta API, you can also filter on nested fields. For
110+-- filtering in the Beta API, you can also filter on nested fields. For
111-- example, you could filter on instances that have set the
111-- example, you could filter on instances that have set the
112−-- scheduling.automaticRestart field to true. In particular, use filtering
112+-- scheduling.automaticRestart field to true. Use filtering on nested
113−-- on nested fields to take advantage of instance labels to organize and
113+-- fields to take advantage of labels to organize and search for results
114−-- filter results based on label values. The Beta API also supports
114+-- based on label values. The Beta API also supports filtering on multiple
115−-- filtering on multiple expressions by providing each separate expression
115+-- expressions by providing each separate expression within parentheses.
116−-- within parentheses. For example, (scheduling.automaticRestart eq true)
116+-- For example, (scheduling.automaticRestart eq true) (zone eq
117−-- (zone eq us-central1-f). Multiple expressions are treated as AND
117+-- us-central1-f). Multiple expressions are treated as AND expressions,
118−-- expressions, meaning that resources must match all expressions to pass
118+-- meaning that resources must match all expressions to pass the filters.
119−-- the filters.
120rlFilter :: Lens' RoutesList (Maybe Text)
119rlFilter :: Lens' RoutesList (Maybe Text)
121rlFilter = lens _rlFilter (\ s a -> s{_rlFilter = a})
120rlFilter = lens _rlFilter (\ s a -> s{_rlFilter = a})
122
121
gogol-compute/gen/Network/Google/Resource/Compute/SSLCertificates/List.hs+9−10
@@ -107,17 +107,16 @@ sclProject
107-- value is interpreted as a regular expression using RE2 syntax. The
107-- value is interpreted as a regular expression using RE2 syntax. The
108-- literal value must match the entire field. For example, to filter for
108-- literal value must match the entire field. For example, to filter for
109-- instances that do not have a name of example-instance, you would use
109-- instances that do not have a name of example-instance, you would use
110−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
110+-- filter=name ne example-instance. Compute Engine Beta API Only: When
111−-- use filtering in the Beta API, you can also filter on nested fields. For
111+-- filtering in the Beta API, you can also filter on nested fields. For
112-- example, you could filter on instances that have set the
112-- example, you could filter on instances that have set the
113−-- scheduling.automaticRestart field to true. In particular, use filtering
113+-- scheduling.automaticRestart field to true. Use filtering on nested
114−-- on nested fields to take advantage of instance labels to organize and
114+-- fields to take advantage of labels to organize and search for results
115−-- filter results based on label values. The Beta API also supports
115+-- based on label values. The Beta API also supports filtering on multiple
116−-- filtering on multiple expressions by providing each separate expression
116+-- expressions by providing each separate expression within parentheses.
117−-- within parentheses. For example, (scheduling.automaticRestart eq true)
117+-- For example, (scheduling.automaticRestart eq true) (zone eq
118−-- (zone eq us-central1-f). Multiple expressions are treated as AND
118+-- us-central1-f). Multiple expressions are treated as AND expressions,
119−-- expressions, meaning that resources must match all expressions to pass
119+-- meaning that resources must match all expressions to pass the filters.
120−-- the filters.
121sclFilter :: Lens' SSLCertificatesList (Maybe Text)
120sclFilter :: Lens' SSLCertificatesList (Maybe Text)
122sclFilter
121sclFilter
123 = lens _sclFilter (\ s a -> s{_sclFilter = a})
122 = lens _sclFilter (\ s a -> s{_sclFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Snapshots/List.hs+9−10
@@ -105,17 +105,16 @@ sProject = lens _sProject (\ s a -> s{_sProject = a})
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119sFilter :: Lens' SnapshotsList (Maybe Text)
118sFilter :: Lens' SnapshotsList (Maybe Text)
120sFilter = lens _sFilter (\ s a -> s{_sFilter = a})
119sFilter = lens _sFilter (\ s a -> s{_sFilter = a})
121
120
gogol-compute/gen/Network/Google/Resource/Compute/Subnetworks/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ salProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119salFilter :: Lens' SubnetworksAggregatedList (Maybe Text)
118salFilter :: Lens' SubnetworksAggregatedList (Maybe Text)
120salFilter
119salFilter
121 = lens _salFilter (\ s a -> s{_salFilter = a})
120 = lens _salFilter (\ s a -> s{_salFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Subnetworks/Get.hs+4−4
@@ -20,8 +20,8 @@
20-- Stability : auto-generated
20-- Stability : auto-generated
21-- Portability : non-portable (GHC extensions)
21-- Portability : non-portable (GHC extensions)
22--
22--
23−-- Returns the specified subnetwork. Get a list of available subnetworks by
23+-- Returns the specified subnetwork. Get a list of available subnetworks
24−-- making a list() request.
24+-- list() request.
25--
25--
26-- /See:/ <https://developers.google.com/compute/docs/reference/latest/ Compute Engine API Reference> for @compute.subnetworks.get@.
26-- /See:/ <https://developers.google.com/compute/docs/reference/latest/ Compute Engine API Reference> for @compute.subnetworks.get@.
27module Network.Google.Resource.Compute.Subnetworks.Get
27module Network.Google.Resource.Compute.Subnetworks.Get
@@ -55,8 +55,8 @@ type SubnetworksGetResource =
55 Capture "subnetwork" Text :>
55 Capture "subnetwork" Text :>
56 QueryParam "alt" AltJSON :> Get '[JSON] Subnetwork
56 QueryParam "alt" AltJSON :> Get '[JSON] Subnetwork
57
57
58−-- | Returns the specified subnetwork. Get a list of available subnetworks by
58+-- | Returns the specified subnetwork. Get a list of available subnetworks
59−-- making a list() request.
59+-- list() request.
60--
60--
61-- /See:/ 'subnetworksGet' smart constructor.
61-- /See:/ 'subnetworksGet' smart constructor.
62data SubnetworksGet = SubnetworksGet'
62data SubnetworksGet = SubnetworksGet'
gogol-compute/gen/Network/Google/Resource/Compute/Subnetworks/List.hs+9−10
@@ -112,17 +112,16 @@ slProject
112-- value is interpreted as a regular expression using RE2 syntax. The
112-- value is interpreted as a regular expression using RE2 syntax. The
113-- literal value must match the entire field. For example, to filter for
113-- literal value must match the entire field. For example, to filter for
114-- instances that do not have a name of example-instance, you would use
114-- instances that do not have a name of example-instance, you would use
115−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
115+-- filter=name ne example-instance. Compute Engine Beta API Only: When
116−-- use filtering in the Beta API, you can also filter on nested fields. For
116+-- filtering in the Beta API, you can also filter on nested fields. For
117-- example, you could filter on instances that have set the
117-- example, you could filter on instances that have set the
118−-- scheduling.automaticRestart field to true. In particular, use filtering
118+-- scheduling.automaticRestart field to true. Use filtering on nested
119−-- on nested fields to take advantage of instance labels to organize and
119+-- fields to take advantage of labels to organize and search for results
120−-- filter results based on label values. The Beta API also supports
120+-- based on label values. The Beta API also supports filtering on multiple
121−-- filtering on multiple expressions by providing each separate expression
121+-- expressions by providing each separate expression within parentheses.
122−-- within parentheses. For example, (scheduling.automaticRestart eq true)
122+-- For example, (scheduling.automaticRestart eq true) (zone eq
123−-- (zone eq us-central1-f). Multiple expressions are treated as AND
123+-- us-central1-f). Multiple expressions are treated as AND expressions,
124−-- expressions, meaning that resources must match all expressions to pass
124+-- meaning that resources must match all expressions to pass the filters.
125−-- the filters.
126slFilter :: Lens' SubnetworksList (Maybe Text)
125slFilter :: Lens' SubnetworksList (Maybe Text)
127slFilter = lens _slFilter (\ s a -> s{_slFilter = a})
126slFilter = lens _slFilter (\ s a -> s{_slFilter = a})
128
127
gogol-compute/gen/Network/Google/Resource/Compute/TargetHTTPProxies/List.hs+9−10
@@ -108,17 +108,16 @@ thttpplProject
108-- value is interpreted as a regular expression using RE2 syntax. The
108-- value is interpreted as a regular expression using RE2 syntax. The
109-- literal value must match the entire field. For example, to filter for
109-- literal value must match the entire field. For example, to filter for
110-- instances that do not have a name of example-instance, you would use
110-- instances that do not have a name of example-instance, you would use
111−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
111+-- filter=name ne example-instance. Compute Engine Beta API Only: When
112−-- use filtering in the Beta API, you can also filter on nested fields. For
112+-- filtering in the Beta API, you can also filter on nested fields. For
113-- example, you could filter on instances that have set the
113-- example, you could filter on instances that have set the
114−-- scheduling.automaticRestart field to true. In particular, use filtering
114+-- scheduling.automaticRestart field to true. Use filtering on nested
115−-- on nested fields to take advantage of instance labels to organize and
115+-- fields to take advantage of labels to organize and search for results
116−-- filter results based on label values. The Beta API also supports
116+-- based on label values. The Beta API also supports filtering on multiple
117−-- filtering on multiple expressions by providing each separate expression
117+-- expressions by providing each separate expression within parentheses.
118−-- within parentheses. For example, (scheduling.automaticRestart eq true)
118+-- For example, (scheduling.automaticRestart eq true) (zone eq
119−-- (zone eq us-central1-f). Multiple expressions are treated as AND
119+-- us-central1-f). Multiple expressions are treated as AND expressions,
120−-- expressions, meaning that resources must match all expressions to pass
120+-- meaning that resources must match all expressions to pass the filters.
121−-- the filters.
122thttpplFilter :: Lens' TargetHTTPProxiesList (Maybe Text)
121thttpplFilter :: Lens' TargetHTTPProxiesList (Maybe Text)
123thttpplFilter
122thttpplFilter
124 = lens _thttpplFilter
123 = lens _thttpplFilter
gogol-compute/gen/Network/Google/Resource/Compute/TargetHTTPSProxies/List.hs+9−10
@@ -107,17 +107,16 @@ thplProject
107-- value is interpreted as a regular expression using RE2 syntax. The
107-- value is interpreted as a regular expression using RE2 syntax. The
108-- literal value must match the entire field. For example, to filter for
108-- literal value must match the entire field. For example, to filter for
109-- instances that do not have a name of example-instance, you would use
109-- instances that do not have a name of example-instance, you would use
110−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
110+-- filter=name ne example-instance. Compute Engine Beta API Only: When
111−-- use filtering in the Beta API, you can also filter on nested fields. For
111+-- filtering in the Beta API, you can also filter on nested fields. For
112-- example, you could filter on instances that have set the
112-- example, you could filter on instances that have set the
113−-- scheduling.automaticRestart field to true. In particular, use filtering
113+-- scheduling.automaticRestart field to true. Use filtering on nested
114−-- on nested fields to take advantage of instance labels to organize and
114+-- fields to take advantage of labels to organize and search for results
115−-- filter results based on label values. The Beta API also supports
115+-- based on label values. The Beta API also supports filtering on multiple
116−-- filtering on multiple expressions by providing each separate expression
116+-- expressions by providing each separate expression within parentheses.
117−-- within parentheses. For example, (scheduling.automaticRestart eq true)
117+-- For example, (scheduling.automaticRestart eq true) (zone eq
118−-- (zone eq us-central1-f). Multiple expressions are treated as AND
118+-- us-central1-f). Multiple expressions are treated as AND expressions,
119−-- expressions, meaning that resources must match all expressions to pass
119+-- meaning that resources must match all expressions to pass the filters.
120−-- the filters.
121thplFilter :: Lens' TargetHTTPSProxiesList (Maybe Text)
120thplFilter :: Lens' TargetHTTPSProxiesList (Maybe Text)
122thplFilter
121thplFilter
123 = lens _thplFilter (\ s a -> s{_thplFilter = a})
122 = lens _thplFilter (\ s a -> s{_thplFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/TargetInstances/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ tialProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119tialFilter :: Lens' TargetInstancesAggregatedList (Maybe Text)
118tialFilter :: Lens' TargetInstancesAggregatedList (Maybe Text)
120tialFilter
119tialFilter
121 = lens _tialFilter (\ s a -> s{_tialFilter = a})
120 = lens _tialFilter (\ s a -> s{_tialFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/TargetInstances/List.hs+9−10
@@ -118,17 +118,16 @@ tilZone = lens _tilZone (\ s a -> s{_tilZone = a})
118-- value is interpreted as a regular expression using RE2 syntax. The
118-- value is interpreted as a regular expression using RE2 syntax. The
119-- literal value must match the entire field. For example, to filter for
119-- literal value must match the entire field. For example, to filter for
120-- instances that do not have a name of example-instance, you would use
120-- instances that do not have a name of example-instance, you would use
121−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
121+-- filter=name ne example-instance. Compute Engine Beta API Only: When
122−-- use filtering in the Beta API, you can also filter on nested fields. For
122+-- filtering in the Beta API, you can also filter on nested fields. For
123-- example, you could filter on instances that have set the
123-- example, you could filter on instances that have set the
124−-- scheduling.automaticRestart field to true. In particular, use filtering
124+-- scheduling.automaticRestart field to true. Use filtering on nested
125−-- on nested fields to take advantage of instance labels to organize and
125+-- fields to take advantage of labels to organize and search for results
126−-- filter results based on label values. The Beta API also supports
126+-- based on label values. The Beta API also supports filtering on multiple
127−-- filtering on multiple expressions by providing each separate expression
127+-- expressions by providing each separate expression within parentheses.
128−-- within parentheses. For example, (scheduling.automaticRestart eq true)
128+-- For example, (scheduling.automaticRestart eq true) (zone eq
129−-- (zone eq us-central1-f). Multiple expressions are treated as AND
129+-- us-central1-f). Multiple expressions are treated as AND expressions,
130−-- expressions, meaning that resources must match all expressions to pass
130+-- meaning that resources must match all expressions to pass the filters.
131−-- the filters.
132tilFilter :: Lens' TargetInstancesList (Maybe Text)
131tilFilter :: Lens' TargetInstancesList (Maybe Text)
133tilFilter
132tilFilter
134 = lens _tilFilter (\ s a -> s{_tilFilter = a})
133 = lens _tilFilter (\ s a -> s{_tilFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/TargetPools/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ tpalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119tpalFilter :: Lens' TargetPoolsAggregatedList (Maybe Text)
118tpalFilter :: Lens' TargetPoolsAggregatedList (Maybe Text)
120tpalFilter
119tpalFilter
121 = lens _tpalFilter (\ s a -> s{_tpalFilter = a})
120 = lens _tpalFilter (\ s a -> s{_tpalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/TargetPools/List.hs+9−10
@@ -114,17 +114,16 @@ tplProject
114-- value is interpreted as a regular expression using RE2 syntax. The
114-- value is interpreted as a regular expression using RE2 syntax. The
115-- literal value must match the entire field. For example, to filter for
115-- literal value must match the entire field. For example, to filter for
116-- instances that do not have a name of example-instance, you would use
116-- instances that do not have a name of example-instance, you would use
117−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
117+-- filter=name ne example-instance. Compute Engine Beta API Only: When
118−-- use filtering in the Beta API, you can also filter on nested fields. For
118+-- filtering in the Beta API, you can also filter on nested fields. For
119-- example, you could filter on instances that have set the
119-- example, you could filter on instances that have set the
120−-- scheduling.automaticRestart field to true. In particular, use filtering
120+-- scheduling.automaticRestart field to true. Use filtering on nested
121−-- on nested fields to take advantage of instance labels to organize and
121+-- fields to take advantage of labels to organize and search for results
122−-- filter results based on label values. The Beta API also supports
122+-- based on label values. The Beta API also supports filtering on multiple
123−-- filtering on multiple expressions by providing each separate expression
123+-- expressions by providing each separate expression within parentheses.
124−-- within parentheses. For example, (scheduling.automaticRestart eq true)
124+-- For example, (scheduling.automaticRestart eq true) (zone eq
125−-- (zone eq us-central1-f). Multiple expressions are treated as AND
125+-- us-central1-f). Multiple expressions are treated as AND expressions,
126−-- expressions, meaning that resources must match all expressions to pass
126+-- meaning that resources must match all expressions to pass the filters.
127−-- the filters.
128tplFilter :: Lens' TargetPoolsList (Maybe Text)
127tplFilter :: Lens' TargetPoolsList (Maybe Text)
129tplFilter
128tplFilter
130 = lens _tplFilter (\ s a -> s{_tplFilter = a})
129 = lens _tplFilter (\ s a -> s{_tplFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/TargetVPNGateways/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ tvgalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119tvgalFilter :: Lens' TargetVPNGatewaysAggregatedList (Maybe Text)
118tvgalFilter :: Lens' TargetVPNGatewaysAggregatedList (Maybe Text)
120tvgalFilter
119tvgalFilter
121 = lens _tvgalFilter (\ s a -> s{_tvgalFilter = a})
120 = lens _tvgalFilter (\ s a -> s{_tvgalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/TargetVPNGateways/List.hs+9−10
@@ -114,17 +114,16 @@ tvglProject
114-- value is interpreted as a regular expression using RE2 syntax. The
114-- value is interpreted as a regular expression using RE2 syntax. The
115-- literal value must match the entire field. For example, to filter for
115-- literal value must match the entire field. For example, to filter for
116-- instances that do not have a name of example-instance, you would use
116-- instances that do not have a name of example-instance, you would use
117−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
117+-- filter=name ne example-instance. Compute Engine Beta API Only: When
118−-- use filtering in the Beta API, you can also filter on nested fields. For
118+-- filtering in the Beta API, you can also filter on nested fields. For
119-- example, you could filter on instances that have set the
119-- example, you could filter on instances that have set the
120−-- scheduling.automaticRestart field to true. In particular, use filtering
120+-- scheduling.automaticRestart field to true. Use filtering on nested
121−-- on nested fields to take advantage of instance labels to organize and
121+-- fields to take advantage of labels to organize and search for results
122−-- filter results based on label values. The Beta API also supports
122+-- based on label values. The Beta API also supports filtering on multiple
123−-- filtering on multiple expressions by providing each separate expression
123+-- expressions by providing each separate expression within parentheses.
124−-- within parentheses. For example, (scheduling.automaticRestart eq true)
124+-- For example, (scheduling.automaticRestart eq true) (zone eq
125−-- (zone eq us-central1-f). Multiple expressions are treated as AND
125+-- us-central1-f). Multiple expressions are treated as AND expressions,
126−-- expressions, meaning that resources must match all expressions to pass
126+-- meaning that resources must match all expressions to pass the filters.
127−-- the filters.
128tvglFilter :: Lens' TargetVPNGatewaysList (Maybe Text)
127tvglFilter :: Lens' TargetVPNGatewaysList (Maybe Text)
129tvglFilter
128tvglFilter
130 = lens _tvglFilter (\ s a -> s{_tvglFilter = a})
129 = lens _tvglFilter (\ s a -> s{_tvglFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/URLMaps/List.hs+9−10
@@ -106,17 +106,16 @@ umlProject
106-- value is interpreted as a regular expression using RE2 syntax. The
106-- value is interpreted as a regular expression using RE2 syntax. The
107-- literal value must match the entire field. For example, to filter for
107-- literal value must match the entire field. For example, to filter for
108-- instances that do not have a name of example-instance, you would use
108-- instances that do not have a name of example-instance, you would use
109−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
109+-- filter=name ne example-instance. Compute Engine Beta API Only: When
110−-- use filtering in the Beta API, you can also filter on nested fields. For
110+-- filtering in the Beta API, you can also filter on nested fields. For
111-- example, you could filter on instances that have set the
111-- example, you could filter on instances that have set the
112−-- scheduling.automaticRestart field to true. In particular, use filtering
112+-- scheduling.automaticRestart field to true. Use filtering on nested
113−-- on nested fields to take advantage of instance labels to organize and
113+-- fields to take advantage of labels to organize and search for results
114−-- filter results based on label values. The Beta API also supports
114+-- based on label values. The Beta API also supports filtering on multiple
115−-- filtering on multiple expressions by providing each separate expression
115+-- expressions by providing each separate expression within parentheses.
116−-- within parentheses. For example, (scheduling.automaticRestart eq true)
116+-- For example, (scheduling.automaticRestart eq true) (zone eq
117−-- (zone eq us-central1-f). Multiple expressions are treated as AND
117+-- us-central1-f). Multiple expressions are treated as AND expressions,
118−-- expressions, meaning that resources must match all expressions to pass
118+-- meaning that resources must match all expressions to pass the filters.
119−-- the filters.
120umlFilter :: Lens' URLMapsList (Maybe Text)
119umlFilter :: Lens' URLMapsList (Maybe Text)
121umlFilter
120umlFilter
122 = lens _umlFilter (\ s a -> s{_umlFilter = a})
121 = lens _umlFilter (\ s a -> s{_umlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/VPNTunnels/AggregatedList.hs+9−10
@@ -105,17 +105,16 @@ vtalProject
105-- value is interpreted as a regular expression using RE2 syntax. The
105-- value is interpreted as a regular expression using RE2 syntax. The
106-- literal value must match the entire field. For example, to filter for
106-- literal value must match the entire field. For example, to filter for
107-- instances that do not have a name of example-instance, you would use
107-- instances that do not have a name of example-instance, you would use
108−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109−-- use filtering in the Beta API, you can also filter on nested fields. For
109+-- filtering in the Beta API, you can also filter on nested fields. For
110-- example, you could filter on instances that have set the
110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112−-- on nested fields to take advantage of instance labels to organize and
112+-- fields to take advantage of labels to organize and search for results
113−-- filter results based on label values. The Beta API also supports
113+-- based on label values. The Beta API also supports filtering on multiple
114−-- filtering on multiple expressions by providing each separate expression
114+-- expressions by providing each separate expression within parentheses.
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117−-- expressions, meaning that resources must match all expressions to pass
117+-- meaning that resources must match all expressions to pass the filters.
118−-- the filters.
119vtalFilter :: Lens' VPNTunnelsAggregatedList (Maybe Text)
118vtalFilter :: Lens' VPNTunnelsAggregatedList (Maybe Text)
120vtalFilter
119vtalFilter
121 = lens _vtalFilter (\ s a -> s{_vtalFilter = a})
120 = lens _vtalFilter (\ s a -> s{_vtalFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/VPNTunnels/List.hs+9−10
@@ -113,17 +113,16 @@ vtlProject
113-- value is interpreted as a regular expression using RE2 syntax. The
113-- value is interpreted as a regular expression using RE2 syntax. The
114-- literal value must match the entire field. For example, to filter for
114-- literal value must match the entire field. For example, to filter for
115-- instances that do not have a name of example-instance, you would use
115-- instances that do not have a name of example-instance, you would use
116−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
116+-- filter=name ne example-instance. Compute Engine Beta API Only: When
117−-- use filtering in the Beta API, you can also filter on nested fields. For
117+-- filtering in the Beta API, you can also filter on nested fields. For
118-- example, you could filter on instances that have set the
118-- example, you could filter on instances that have set the
119−-- scheduling.automaticRestart field to true. In particular, use filtering
119+-- scheduling.automaticRestart field to true. Use filtering on nested
120−-- on nested fields to take advantage of instance labels to organize and
120+-- fields to take advantage of labels to organize and search for results
121−-- filter results based on label values. The Beta API also supports
121+-- based on label values. The Beta API also supports filtering on multiple
122−-- filtering on multiple expressions by providing each separate expression
122+-- expressions by providing each separate expression within parentheses.
123−-- within parentheses. For example, (scheduling.automaticRestart eq true)
123+-- For example, (scheduling.automaticRestart eq true) (zone eq
124−-- (zone eq us-central1-f). Multiple expressions are treated as AND
124+-- us-central1-f). Multiple expressions are treated as AND expressions,
125−-- expressions, meaning that resources must match all expressions to pass
125+-- meaning that resources must match all expressions to pass the filters.
126−-- the filters.
127vtlFilter :: Lens' VPNTunnelsList (Maybe Text)
126vtlFilter :: Lens' VPNTunnelsList (Maybe Text)
128vtlFilter
127vtlFilter
129 = lens _vtlFilter (\ s a -> s{_vtlFilter = a})
128 = lens _vtlFilter (\ s a -> s{_vtlFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/ZoneOperations/List.hs+9−10
@@ -117,17 +117,16 @@ zolZone = lens _zolZone (\ s a -> s{_zolZone = a})
117-- value is interpreted as a regular expression using RE2 syntax. The
117-- value is interpreted as a regular expression using RE2 syntax. The
118-- literal value must match the entire field. For example, to filter for
118-- literal value must match the entire field. For example, to filter for
119-- instances that do not have a name of example-instance, you would use
119-- instances that do not have a name of example-instance, you would use
120−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
120+-- filter=name ne example-instance. Compute Engine Beta API Only: When
121−-- use filtering in the Beta API, you can also filter on nested fields. For
121+-- filtering in the Beta API, you can also filter on nested fields. For
122-- example, you could filter on instances that have set the
122-- example, you could filter on instances that have set the
123−-- scheduling.automaticRestart field to true. In particular, use filtering
123+-- scheduling.automaticRestart field to true. Use filtering on nested
124−-- on nested fields to take advantage of instance labels to organize and
124+-- fields to take advantage of labels to organize and search for results
125−-- filter results based on label values. The Beta API also supports
125+-- based on label values. The Beta API also supports filtering on multiple
126−-- filtering on multiple expressions by providing each separate expression
126+-- expressions by providing each separate expression within parentheses.
127−-- within parentheses. For example, (scheduling.automaticRestart eq true)
127+-- For example, (scheduling.automaticRestart eq true) (zone eq
128−-- (zone eq us-central1-f). Multiple expressions are treated as AND
128+-- us-central1-f). Multiple expressions are treated as AND expressions,
129−-- expressions, meaning that resources must match all expressions to pass
129+-- meaning that resources must match all expressions to pass the filters.
130−-- the filters.
131zolFilter :: Lens' ZoneOperationsList (Maybe Text)
130zolFilter :: Lens' ZoneOperationsList (Maybe Text)
132zolFilter
131zolFilter
133 = lens _zolFilter (\ s a -> s{_zolFilter = a})
132 = lens _zolFilter (\ s a -> s{_zolFilter = a})
gogol-compute/gen/Network/Google/Resource/Compute/Zones/List.hs+9−10
@@ -103,17 +103,16 @@ zlProject
103-- value is interpreted as a regular expression using RE2 syntax. The
103-- value is interpreted as a regular expression using RE2 syntax. The
104-- literal value must match the entire field. For example, to filter for
104-- literal value must match the entire field. For example, to filter for
105-- instances that do not have a name of example-instance, you would use
105-- instances that do not have a name of example-instance, you would use
106−-- filter=name ne example-instance. Compute Engine Beta API Only: If you
106+-- filter=name ne example-instance. Compute Engine Beta API Only: When
107−-- use filtering in the Beta API, you can also filter on nested fields. For
107+-- filtering in the Beta API, you can also filter on nested fields. For
108-- example, you could filter on instances that have set the
108-- example, you could filter on instances that have set the
109−-- scheduling.automaticRestart field to true. In particular, use filtering
109+-- scheduling.automaticRestart field to true. Use filtering on nested
110−-- on nested fields to take advantage of instance labels to organize and
110+-- fields to take advantage of labels to organize and search for results
111−-- filter results based on label values. The Beta API also supports
111+-- based on label values. The Beta API also supports filtering on multiple
112−-- filtering on multiple expressions by providing each separate expression
112+-- expressions by providing each separate expression within parentheses.
113−-- within parentheses. For example, (scheduling.automaticRestart eq true)
113+-- For example, (scheduling.automaticRestart eq true) (zone eq
114−-- (zone eq us-central1-f). Multiple expressions are treated as AND
114+-- us-central1-f). Multiple expressions are treated as AND expressions,
115−-- expressions, meaning that resources must match all expressions to pass
115+-- meaning that resources must match all expressions to pass the filters.
116−-- the filters.
117zlFilter :: Lens' ZonesList (Maybe Text)
116zlFilter :: Lens' ZonesList (Maybe Text)
118zlFilter = lens _zlFilter (\ s a -> s{_zlFilter = a})
117zlFilter = lens _zlFilter (\ s a -> s{_zlFilter = a})
119
118
gogol-compute/gogol-compute.cabal+3−1
@@ -14,7 +14,7 @@ cabal-version: >= 1.10
14extra-source-files: README.md
14extra-source-files: README.md
15
15
16description:
16description:
17− API for the Google Compute Engine service.
17+ Creates and runs virtual machines on Google Cloud Platform.
18 .
18 .
19 /Warning:/ This is an experimental prototype/preview release which is still
19 /Warning:/ This is an experimental prototype/preview release which is still
20 under exploratory development and not intended for public use, caveat emptor!
20 under exploratory development and not intended for public use, caveat emptor!
@@ -63,6 +63,7 @@ library
63 , Network.Google.Resource.Compute.Disks.Get
63 , Network.Google.Resource.Compute.Disks.Get
64 , Network.Google.Resource.Compute.Disks.Insert
64 , Network.Google.Resource.Compute.Disks.Insert
65 , Network.Google.Resource.Compute.Disks.List
65 , Network.Google.Resource.Compute.Disks.List
66+ , Network.Google.Resource.Compute.Disks.Resize
66 , Network.Google.Resource.Compute.Firewalls.Delete
67 , Network.Google.Resource.Compute.Firewalls.Delete
67 , Network.Google.Resource.Compute.Firewalls.Get
68 , Network.Google.Resource.Compute.Firewalls.Get
68 , Network.Google.Resource.Compute.Firewalls.Insert
69 , Network.Google.Resource.Compute.Firewalls.Insert
@@ -103,6 +104,7 @@ library
103 , Network.Google.Resource.Compute.Images.Delete
104 , Network.Google.Resource.Compute.Images.Delete
104 , Network.Google.Resource.Compute.Images.Deprecate
105 , Network.Google.Resource.Compute.Images.Deprecate
105 , Network.Google.Resource.Compute.Images.Get
106 , Network.Google.Resource.Compute.Images.Get
107+ , Network.Google.Resource.Compute.Images.GetFromFamily
106 , Network.Google.Resource.Compute.Images.Insert
108 , Network.Google.Resource.Compute.Images.Insert
107 , Network.Google.Resource.Compute.Images.List
109 , Network.Google.Resource.Compute.Images.List
108 , Network.Google.Resource.Compute.InstanceGroupManagers.AbandonInstances
110 , Network.Google.Resource.Compute.InstanceGroupManagers.AbandonInstances