git.iko.soy/gogol
on develop help sign in
Regenerating gogol-deploymentmanager from latest service definition
commitc22ab4c07eb3ac2cd2f827732547c9fe1e2dd34e authorBrendan Hay <brendan.g.hay@gmail.com> dateTue 10 May 2016, 16:12 (10 years ago) parent1ecc1e7
9 files changed+63−55
compare with develop
unifiedsplit
gogol-deploymentmanager/gen/Network/Google/DeploymentManager.hs+3−2 gogol-deploymentmanager/gen/Network/Google/DeploymentManager/Types.hs+1 gogol-deploymentmanager/gen/Network/Google/DeploymentManager/Types/Product.hs+12−1 gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Deployments/List.hs+9−10 gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Manifests/List.hs+9−10 gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Operations/List.hs+9−10 gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Resources/List.hs+9−10 gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Types/List.hs+9−10 gogol-deploymentmanager/gogol-deploymentmanager.cabal+2−2
gogol-deploymentmanager/gen/Network/Google/DeploymentManager.hs+3−2
@@ -13,8 +13,8 @@
1313-- Stability : auto-generated
1414-- Portability : non-portable (GHC extensions)
1515--
16−-- The Deployment Manager API allows users to declaratively configure,
17−-- deploy and run complex solutions on the Google Cloud Platform.
16+-- Declares, configures, and deploys complex solutions on Google Cloud
17+-- Platform.
1818--
1919-- /See:/ <https://cloud.google.com/deployment-manager/ Google Cloud Deployment Manager API Reference>
2020module Network.Google.DeploymentManager
@@ -309,6 +309,7 @@ module Network.Google.DeploymentManager
309309 , dInsertTime
310310 , dOperation
311311 , dFingerprint
312+ , dSelfLink
312313 , dName
313314 , dManifest
314315 , dId
gogol-deploymentmanager/gen/Network/Google/DeploymentManager/Types.hs+1
@@ -254,6 +254,7 @@ module Network.Google.DeploymentManager.Types
254254 , dInsertTime
255255 , dOperation
256256 , dFingerprint
257+ , dSelfLink
257258 , dName
258259 , dManifest
259260 , dId
gogol-deploymentmanager/gen/Network/Google/DeploymentManager/Types/Product.hs+12−1
@@ -404,7 +404,7 @@ oStartTime
404404 = lens _oStartTime (\ s a -> s{_oStartTime = a})
405405
406406-- | [Output Only] Type of the resource. Always compute#operation for
407−-- operation resources.
407+-- Operation resources.
408408oKind :: Lens' Operation Text
409409oKind = lens _oKind (\ s a -> s{_oKind = a})
410410
@@ -1915,6 +1915,7 @@ data Deployment = Deployment'
19151915 { _dInsertTime :: !(Maybe Text)
19161916 , _dOperation :: !(Maybe Operation)
19171917 , _dFingerprint :: !(Maybe (Textual Word8))
1918+ , _dSelfLink :: !(Maybe Text)
19181919 , _dName :: !(Maybe Text)
19191920 , _dManifest :: !(Maybe Text)
19201921 , _dId :: !(Maybe (Textual Word64))
@@ -1934,6 +1935,8 @@ data Deployment = Deployment'
19341935--
19351936-- * 'dFingerprint'
19361937--
1938+-- * 'dSelfLink'
1939+--
19371940-- * 'dName'
19381941--
19391942-- * 'dManifest'
@@ -1954,6 +1957,7 @@ deployment =
19541957 { _dInsertTime = Nothing
19551958 , _dOperation = Nothing
19561959 , _dFingerprint = Nothing
1960+ , _dSelfLink = Nothing
19571961 , _dName = Nothing
19581962 , _dManifest = Nothing
19591963 , _dId = Nothing
@@ -1988,6 +1992,11 @@ dFingerprint
19881992 = lens _dFingerprint (\ s a -> s{_dFingerprint = a})
19891993 . mapping _Coerce
19901994
1995+-- | [Output Only] Self link for the deployment.
1996+dSelfLink :: Lens' Deployment (Maybe Text)
1997+dSelfLink
1998+ = lens _dSelfLink (\ s a -> s{_dSelfLink = a})
1999+
19912000-- | Name of the resource; provided by the client when the resource is
19922001-- created. The name must be 1-63 characters long, and comply with RFC1035.
19932002-- Specifically, the name must be 1-63 characters long and match the
@@ -2042,6 +2051,7 @@ instance FromJSON Deployment where
20422051 Deployment' <$>
20432052 (o .:? "insertTime") <*> (o .:? "operation") <*>
20442053 (o .:? "fingerprint")
2054+ <*> (o .:? "selfLink")
20452055 <*> (o .:? "name")
20462056 <*> (o .:? "manifest")
20472057 <*> (o .:? "id")
@@ -2057,6 +2067,7 @@ instance ToJSON Deployment where
20572067 [("insertTime" .=) <$> _dInsertTime,
20582068 ("operation" .=) <$> _dOperation,
20592069 ("fingerprint" .=) <$> _dFingerprint,
2070+ ("selfLink" .=) <$> _dSelfLink,
20602071 ("name" .=) <$> _dName,
20612072 ("manifest" .=) <$> _dManifest, ("id" .=) <$> _dId,
20622073 ("labels" .=) <$> _dLabels,
gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Deployments/List.hs+9−10
@@ -105,17 +105,16 @@ dlProject
105105-- value is interpreted as a regular expression using RE2 syntax. The
106106-- literal value must match the entire field. For example, to filter for
107107-- 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
109−-- use filtering in the Beta API, you can also filter on nested fields. For
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109+-- filtering in the Beta API, you can also filter on nested fields. For
110110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
112−-- on nested fields to take advantage of instance labels to organize and
113−-- filter results based on label values. The Beta API also supports
114−-- filtering on multiple expressions by providing each separate expression
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
117−-- expressions, meaning that resources must match all expressions to pass
118−-- the filters.
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112+-- fields to take advantage of labels to organize and search for results
113+-- based on label values. The Beta API also supports filtering on multiple
114+-- expressions by providing each separate expression within parentheses.
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117+-- meaning that resources must match all expressions to pass the filters.
119118dlFilter :: Lens' DeploymentsList (Maybe Text)
120119dlFilter = lens _dlFilter (\ s a -> s{_dlFilter = a})
121120
gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Manifests/List.hs+9−10
@@ -113,17 +113,16 @@ mlProject
113113-- value is interpreted as a regular expression using RE2 syntax. The
114114-- literal value must match the entire field. For example, to filter for
115115-- 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
117−-- use filtering in the Beta API, you can also filter on nested fields. For
116+-- filter=name ne example-instance. Compute Engine Beta API Only: When
117+-- filtering in the Beta API, you can also filter on nested fields. For
118118-- example, you could filter on instances that have set the
119−-- scheduling.automaticRestart field to true. In particular, use filtering
120−-- on nested fields to take advantage of instance labels to organize and
121−-- filter results based on label values. The Beta API also supports
122−-- filtering on multiple expressions by providing each separate expression
123−-- within parentheses. For example, (scheduling.automaticRestart eq true)
124−-- (zone eq us-central1-f). Multiple expressions are treated as AND
125−-- expressions, meaning that resources must match all expressions to pass
126−-- the filters.
119+-- scheduling.automaticRestart field to true. Use filtering on nested
120+-- fields to take advantage of labels to organize and search for results
121+-- based on label values. The Beta API also supports filtering on multiple
122+-- expressions by providing each separate expression within parentheses.
123+-- For example, (scheduling.automaticRestart eq true) (zone eq
124+-- us-central1-f). Multiple expressions are treated as AND expressions,
125+-- meaning that resources must match all expressions to pass the filters.
127126mlFilter :: Lens' ManifestsList (Maybe Text)
128127mlFilter = lens _mlFilter (\ s a -> s{_mlFilter = a})
129128
gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Operations/List.hs+9−10
@@ -105,17 +105,16 @@ olProject
105105-- value is interpreted as a regular expression using RE2 syntax. The
106106-- literal value must match the entire field. For example, to filter for
107107-- 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
109−-- use filtering in the Beta API, you can also filter on nested fields. For
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109+-- filtering in the Beta API, you can also filter on nested fields. For
110110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
112−-- on nested fields to take advantage of instance labels to organize and
113−-- filter results based on label values. The Beta API also supports
114−-- filtering on multiple expressions by providing each separate expression
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
117−-- expressions, meaning that resources must match all expressions to pass
118−-- the filters.
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112+-- fields to take advantage of labels to organize and search for results
113+-- based on label values. The Beta API also supports filtering on multiple
114+-- expressions by providing each separate expression within parentheses.
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117+-- meaning that resources must match all expressions to pass the filters.
119118olFilter :: Lens' OperationsList (Maybe Text)
120119olFilter = lens _olFilter (\ s a -> s{_olFilter = a})
121120
gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Resources/List.hs+9−10
@@ -113,17 +113,16 @@ rlProject
113113-- value is interpreted as a regular expression using RE2 syntax. The
114114-- literal value must match the entire field. For example, to filter for
115115-- 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
117−-- use filtering in the Beta API, you can also filter on nested fields. For
116+-- filter=name ne example-instance. Compute Engine Beta API Only: When
117+-- filtering in the Beta API, you can also filter on nested fields. For
118118-- example, you could filter on instances that have set the
119−-- scheduling.automaticRestart field to true. In particular, use filtering
120−-- on nested fields to take advantage of instance labels to organize and
121−-- filter results based on label values. The Beta API also supports
122−-- filtering on multiple expressions by providing each separate expression
123−-- within parentheses. For example, (scheduling.automaticRestart eq true)
124−-- (zone eq us-central1-f). Multiple expressions are treated as AND
125−-- expressions, meaning that resources must match all expressions to pass
126−-- the filters.
119+-- scheduling.automaticRestart field to true. Use filtering on nested
120+-- fields to take advantage of labels to organize and search for results
121+-- based on label values. The Beta API also supports filtering on multiple
122+-- expressions by providing each separate expression within parentheses.
123+-- For example, (scheduling.automaticRestart eq true) (zone eq
124+-- us-central1-f). Multiple expressions are treated as AND expressions,
125+-- meaning that resources must match all expressions to pass the filters.
127126rlFilter :: Lens' ResourcesList (Maybe Text)
128127rlFilter = lens _rlFilter (\ s a -> s{_rlFilter = a})
129128
gogol-deploymentmanager/gen/Network/Google/Resource/DeploymentManager/Types/List.hs+9−10
@@ -105,17 +105,16 @@ tlProject
105105-- value is interpreted as a regular expression using RE2 syntax. The
106106-- literal value must match the entire field. For example, to filter for
107107-- 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
109−-- use filtering in the Beta API, you can also filter on nested fields. For
108+-- filter=name ne example-instance. Compute Engine Beta API Only: When
109+-- filtering in the Beta API, you can also filter on nested fields. For
110110-- example, you could filter on instances that have set the
111−-- scheduling.automaticRestart field to true. In particular, use filtering
112−-- on nested fields to take advantage of instance labels to organize and
113−-- filter results based on label values. The Beta API also supports
114−-- filtering on multiple expressions by providing each separate expression
115−-- within parentheses. For example, (scheduling.automaticRestart eq true)
116−-- (zone eq us-central1-f). Multiple expressions are treated as AND
117−-- expressions, meaning that resources must match all expressions to pass
118−-- the filters.
111+-- scheduling.automaticRestart field to true. Use filtering on nested
112+-- fields to take advantage of labels to organize and search for results
113+-- based on label values. The Beta API also supports filtering on multiple
114+-- expressions by providing each separate expression within parentheses.
115+-- For example, (scheduling.automaticRestart eq true) (zone eq
116+-- us-central1-f). Multiple expressions are treated as AND expressions,
117+-- meaning that resources must match all expressions to pass the filters.
119118tlFilter :: Lens' TypesList (Maybe Text)
120119tlFilter = lens _tlFilter (\ s a -> s{_tlFilter = a})
121120
gogol-deploymentmanager/gogol-deploymentmanager.cabal+2−2
@@ -14,8 +14,8 @@ cabal-version: >= 1.10
1414extra-source-files: README.md
1515
1616description:
17− The Deployment Manager API allows users to declaratively configure,
18− deploy and run complex solutions on the Google Cloud Platform.
17+ Declares, configures, and deploys complex solutions on Google Cloud
18+ Platform.
1919 .
2020 /Warning:/ This is an experimental prototype/preview release which is still
2121 under exploratory development and not intended for public use, caveat emptor!