gogol-firebase-rules-0.3.0: Google Firebase Rules SDK.

Copyright(c) 2015-2016 Brendan Hay
LicenseMozilla Public License, v. 2.0.
MaintainerBrendan Hay <brendan.g.hay@gmail.com>
Stabilityauto-generated
Portabilitynon-portable (GHC extensions)
Safe HaskellNone
LanguageHaskell2010

Network.Google.Resource.FirebaseRules.Projects.Releases.Update

Contents

Description

Update a `Release`. Only updates to the `ruleset_name` field will be honored. `Release` rename is not supported. To create a `Release` use the CreateRelease method instead.

See: Firebase Rules API Reference for firebaserules.projects.releases.update.

Synopsis

REST Resource

type ProjectsReleasesUpdateResource = "v1" :> (Capture "name" Text :> (QueryParam "$.xgafv" Xgafv :> (QueryParam "upload_protocol" Text :> (QueryParam "pp" Bool :> (QueryParam "access_token" Text :> (QueryParam "uploadType" Text :> (QueryParam "bearer_token" Text :> (QueryParam "callback" Text :> (QueryParam "alt" AltJSON :> (ReqBody '[JSON] Release :> Put '[JSON] Release)))))))))) #

A resource alias for firebaserules.projects.releases.update method which the ProjectsReleasesUpdate request conforms to.

Creating a Request

projectsReleasesUpdate #

Creates a value of ProjectsReleasesUpdate with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

data ProjectsReleasesUpdate #

Update a `Release`. Only updates to the `ruleset_name` field will be honored. `Release` rename is not supported. To create a `Release` use the CreateRelease method instead.

See: projectsReleasesUpdate smart constructor.

Instances

Eq ProjectsReleasesUpdate # 
Data ProjectsReleasesUpdate # 

Methods

gfoldl :: (forall d b. Data d => c (d -> b) -> d -> c b) -> (forall g. g -> c g) -> ProjectsReleasesUpdate -> c ProjectsReleasesUpdate #

gunfold :: (forall b r. Data b => c (b -> r) -> c r) -> (forall r. r -> c r) -> Constr -> c ProjectsReleasesUpdate #

toConstr :: ProjectsReleasesUpdate -> Constr #

dataTypeOf :: ProjectsReleasesUpdate -> DataType #

dataCast1 :: Typeable (* -> *) t => (forall d. Data d => c (t d)) -> Maybe (c ProjectsReleasesUpdate) #

dataCast2 :: Typeable (* -> * -> *) t => (forall d e. (Data d, Data e) => c (t d e)) -> Maybe (c ProjectsReleasesUpdate) #

gmapT :: (forall b. Data b => b -> b) -> ProjectsReleasesUpdate -> ProjectsReleasesUpdate #

gmapQl :: (r -> r' -> r) -> r -> (forall d. Data d => d -> r') -> ProjectsReleasesUpdate -> r #

gmapQr :: (r' -> r -> r) -> r -> (forall d. Data d => d -> r') -> ProjectsReleasesUpdate -> r #

gmapQ :: (forall d. Data d => d -> u) -> ProjectsReleasesUpdate -> [u] #

gmapQi :: Int -> (forall d. Data d => d -> u) -> ProjectsReleasesUpdate -> u #

gmapM :: Monad m => (forall d. Data d => d -> m d) -> ProjectsReleasesUpdate -> m ProjectsReleasesUpdate #

gmapMp :: MonadPlus m => (forall d. Data d => d -> m d) -> ProjectsReleasesUpdate -> m ProjectsReleasesUpdate #

gmapMo :: MonadPlus m => (forall d. Data d => d -> m d) -> ProjectsReleasesUpdate -> m ProjectsReleasesUpdate #

Show ProjectsReleasesUpdate # 
Generic ProjectsReleasesUpdate # 
GoogleRequest ProjectsReleasesUpdate # 
type Rep ProjectsReleasesUpdate # 
type Scopes ProjectsReleasesUpdate # 
type Scopes ProjectsReleasesUpdate = (:) Symbol "https://www.googleapis.com/auth/cloud-platform" ((:) Symbol "https://www.googleapis.com/auth/firebase" ([] Symbol))
type Rs ProjectsReleasesUpdate # 

Request Lenses

pruUploadProtocol :: Lens' ProjectsReleasesUpdate (Maybe Text) #

Upload protocol for media (e.g. "raw", "multipart").

pruPp :: Lens' ProjectsReleasesUpdate Bool #

Pretty-print response.

pruUploadType :: Lens' ProjectsReleasesUpdate (Maybe Text) #

Legacy upload protocol for media (e.g. "media", "multipart").

pruPayload :: Lens' ProjectsReleasesUpdate Release #

Multipart request metadata.

pruName :: Lens' ProjectsReleasesUpdate Text #

Resource name for the `Release`. `Release` names may be structured `app1/prod/v2` or flat `app1_prod_v2` which affords developers a great deal of flexibility in mapping the name to the style that best fits their existing development practices. For example, a name could refer to an environment, an app, a version, or some combination of three. In the table below, for the project name `projects/foo`, the following relative release paths show how flat and structured names might be chosen to match a desired development / deployment strategy. Use Case | Flat Name | Structured Name -------------|---------------------|---------------- Environments | releases/qa | releases/qa Apps | releases/app1_qa | releases/app1/qa Versions | releases/app1_v2_qa | releases/app1/v2/qa The delimiter between the release name path elements can be almost anything and it should work equally well with the release name list filter, but in many ways the structured paths provide a clearer picture of the relationship between `Release` instances. Format: `projects/{project_id}/releases/{release_id}`