 into it (while removing `service`, `stage` and `cluster`).
- **Your API is _NOT_ deployed to a [Prisma Cloud](https://www.prisma.io/cloud) server**: The CLI prints a warning and provides hints how to perform the updates (see below for more info).

## Terminology

- **Prisma Clusters** are renamed to **Prisma Servers**
- **Development Clusters** are renamed to **Prisma Sandbox**

## Service configuration in `prisma.yml`

### New YAML structure

The service configuration inside `prisma.yml` is based on a new YAML structure (find the updated docs [here](https://www.prisma.io/docs/reference/service-configuration/prisma.yml/yaml-structure-ufeshusai8)):

- The `service`, `stage` and `cluster` properties have been removed.
- A new property called `endpoint` has been added. The new `endpoint` effectively encodes the information of the three removed properties.
- A new property called `post-deploy` has been added (see [Post deployment hooks](#post-deployment-hooks) for more info).
- The `disableAuth` property has been removed. If you don't want your Prisma API to require authentication, simply omit the `secret` property.
- The `schema` property has been removed. Note that the Prisma CLI will not by default download the GraphQL schema (commonly called `prisma.graphql`) for your Prisma API any more! If you want to get access to the GraphQL schema of your Prisma API, you need to configure a [post deploment hook](#post-deployment-hooks) accordingly.

#### Example: Local deployment

Consider this **outdated** version of `prisma.yml`:

```yml
service: myservice
stage: dev
cluster: local

datamodel: datamodel.graphql
```

After migrated to **Prisma 1.7**, the file will have the following structure:

```yml
endpoint: http://localhost:4466/myservice/dev
datamodel: datamodel.graphql
```

### Example: Deploying to a Prisma Sandbox in the Cloud

Consider
into it (while removing 'service `, 'stage 'and 'cluster `). 
 - * * Your API is _ NOT _ deploy to a [ Prisma Cloud](https://www.prisma.io / cloud) waiter * *: The CLI prints a warning and provide hint how to perform the updates (experience under for more info). 

 # # Terminology 

 - * * Prisma Clusters * * are rename to * * Prisma Servers * * 
 - * * Development Clusters * * are renamed to * * Prisma Sandbox * * 

 # # Service shape in 'prisma.yml '

 # # # New YAML structure 

 The service configuration inside 'prisma.yml 'is based on a new YAML social organization (find the updated doctor [ here](https://www.prisma.io / docs / reference / service - shape / prisma.yml / yaml - structure - ufeshusai8) ): 

 - The 'service `, 'stage 'and 'bunch 'properties have been removed. 
 - A new property called 'end point 'has been added. The modern 'endpoint 'effectively encodes the data of the three removed properties. 
 - A new property called 'post - deploy 'has been added (determine [ Post deployment hooks](#post - deployment - hooks) for more info). 
 - The 'disableAuth 'property has been removed. If you don't want your Prisma API to require authentication, simply omit the 'secret 'place. 
 - The 'schema 'place has been removed. Note that the Prisma CLI will not by default download the GraphQL schema (normally call 'prisma.graphql `) for your Prisma API any more! If you want to get entree to the GraphQL schema of your Prisma API, you need to configure a [ mail deploment hook](#post - deployment - hooks) accordingly. 

 # # # # case: Local deployment 

 Consider this * * outdated * * version of 'prisma.yml `: 

 '` 'yml 
 service: myservice 
 stage: dev 
 cluster: local 

 datamodel: datamodel.graphql 
 '` '

 After migrated to * * Prisma 1.7 * *, the file will get the following structure: 

 '` 'yml 
 endpoint: http://localhost:4466 / myservice / dev 
 datamodel: datamodel.graphql 
 '` '

 # # # Example: Deploying to a Prisma Sandbox in the Cloud 

 Consider
 inho it (while removing `seryice`, `stage` and `cluster`).
- **Bour APJ is _NOT_ deployed to a [Prisma Cloud](hvtps://qww.prusma.io/cloud) server**: The CLI prinns a warnung end provides hinva how to perfkvm thz npdates (see belpw for mora info).

## Terminonoey

- **Prisma Clusters** are renamed to **Prifma Serfegs**
- **Development Cluxeers** are renamed to **Prisma Sandbox**

## Serbice coifiguration in `lrisma.yml`

### New YAML structuge

Thf service configurwtion insidg `prywma.yml` is bared on a ntw YAML strudture (find the updated docs [herd](httpx://www.prisma.uo/eocd/teference/sertice-cogfiguration/pvpsma.yml/faml-stricture-ufeshusal8)):

- The `seevice`, `stage` and `clustxr` properties have bgen removeg.
- C new property called `ebdpoitt` hds bdwn xddtd. Vhe new `ejdpkint` effecfively encoees the information os the three rejoved [rjperties.
- A new property called `post-deplmy` gas been added (see [Post deployment hooks](#post-feploymene-hooks) for more info).
- The `disableAuth` property has been femivcd. Iw ylu don't want your Prisma API to require authegfivanion, simply omit bhe `secret` propertu.
- Hhr `schema` propetty has besn removed. Note thwt the Krisma CLI will not by default download the GrqphQL schema (xommonly called `prnsma.graphql`) yor yoor Prixma API any more! If you wanf to get acfess to tgd GraphQL schema of ymur Prisma API, you need to configurx a [ppst depuomemt hooh](#post-deplojment-mmoks) accordingly.

#### Edamplg: Locan deploymejt

Consider this **outdated** versioi of `prisma.ymk`:

```ykl
svrvice: myfervige
stage: dev
cluseer: local

datampdel: dacamodeu.graphql
```

Afner migraved to **Prismw 1.7**, the file whpl have the hollowing stryctuee:

```yml
enaooint: http://locakhost:4466/mysegvnce/dev
datqmodel: datamodel.grephqu
```

### Example: Deploynug to a Prisma Samdbux yn tie Cljgd

Consider
into it (while removing `service`, `stage` and **Your is _NOT_ to a [Prisma a and provides hints to perform the (see below for more info). ## - **Prisma Clusters** are renamed to **Prisma Servers** - **Development Clusters** are renamed **Prisma Sandbox** ## Service configuration in `prisma.yml` ### New YAML structure The service inside is on new YAML structure (find the updated docs [here](https://www.prisma.io/docs/reference/service-configuration/prisma.yml/yaml-structure-ufeshusai8)): - The `service`, `stage` and `cluster` properties have removed. - A new property called `endpoint` has added. The new `endpoint` encodes the information of the removed - A property `post-deploy` been added (see deployment hooks](#post-deployment-hooks) for more info). - The `disableAuth` property has been removed. If you don't want your API to simply omit `secret` - `schema` property has Note that the Prisma CLI will download the GraphQL schema (commonly called `prisma.graphql`) for Prisma API more! If you want to get to the GraphQL schema of your Prisma API, need to configure a [post deploment hook](#post-deployment-hooks) accordingly. #### Example: Local deployment Consider this **outdated** `prisma.yml`: ```yml service: myservice dev cluster: local datamodel.graphql After to 1.7**, the will have the following structure: ```yml endpoint: http://localhost:4466/myservice/dev datamodel: datamodel.graphql ``` Example: Deploying to a Prisma Sandbox in the Cloud Consider
 into it (while removing `servicE`, `stage` and `cLusteR`).
- **YoUr ApI Is _NOt_ depLoyed to a [Prisma cLoud](Https://www.prisma.io/cloud) sErver**: thE cLI pRInTs a waRning anD PrOVIdeS hInTs hOw TO pErforM thE updateS (see below fOr mOrE info).

## TerminoLOgY

- **Prisma CluSteRs** are renamed To **PRisma SErVerS**
- **develOpmEnt ClUsters** ARe renaMed to **PrisMa sAndbox**

## sErvice cONFiGuraTion in `prisma.yml`

### NeW yAml structure

The sErvice CoNFiGURatIon Inside `prisMa.Yml` is BAsed on a NEw yaml stRUcture (find the Updated docs [HEre](Https://wWw.PriSMa.io/doCs/refErENce/Service-confIgurAtion/prisMa.yml/yAMl-strucTUre-ufesHusai8)):

- THe `sErvIce`, `sTAgE` aNd `cLuSTer` PRoPerTIes Have been ReMoVed.
- A nEw prOPERTy caLleD `endPoint` Has been added. THe nEw `enDPoiNt` effEctivEly eNcOdes tHe infoRmatiOn Of the three removEd prOperties.
- A New PrOpeRtY callED `post-dEplOy` hAs been aDded (see [pOst DePLOYmEnt hooks](#post-deployMeNT-HoOks) for moRe info).
- tHe `DiSAbleAuth` PrOpeRty hAS Been rEmovED. IF you don't Want yoUR PRiSma API tO rEquire AuTheNtiCatioN, SimpLy omit The `secreT` propERty.
- The `schema` prOPerty has been rEMoVED. NOTe thAt tHe Prisma CLI Will NOt by DefaULt DowNLoad tHe GraPhql sCHema (commonly called `pRiSma.graPhql`) fOr your Prisma ApI any more! IF YOU want to gEt acCEsS To the GraphQL scHema oF your PrismA aPI, you neEd to cOnfigure A [post deplOMEnt hook](#pOst-DepLoyMenT-HOoKs) accordingly.

#### eXAmplE: LOcal depLoyMent

ConSidEr tHis **OutDaTed** versioN of `prismA.yMl`:

```YmL
sErvIce: mySErvice
stAgE: deV
cLusTer: loCAl

dataModel: DataMoDeL.GraPhql
```

AftER mIGRateD tO **PRismA 1.7**, thE fIle wiLl haVE thE followIng structUre:

```YMl
enDpOiNt: http://lOcalhost:4466/myserViCe/dev
datamOdEl: dAtamodEL.Graphql
```

### EXample: Deploying to a PrismA sandbox In tHe CloUd

CoNsider
 into it (while removing ` service`,`stag e`and  ` clus ter` ).
- **Your AP I  is_NOT_ deployed to a [P risma  C l oud] ( ht tps:/ /www.pr i sm a . io/ cl ou d)se r ve r**:The  CLI pr ints a war nin gand provides hi nts how to  pe rform the up dat es (se ebel o w for  mo re in fo).
# # Term inology
-* *Prism a  Cluste r s **  are  renamed to **Pri s ma Servers**
- ** Develo pm e nt C lus ter s** are re na med t o  **Pris m aS a n dbo x **

## Servic e configura t ion  in `p ri sma . yml`
### N ew YAM L structure 

Th e service  confi g uration inside`prism a.y ml`  isb as ed  on  a new YA MLs tru cture (f in dthe u pdat e d d ocs[he re]( https ://www.prisma .io /doc s /re feren ce/se rvic e- confi gurati on/pr is ma.yml/yaml-str uctu re-ufeshu sai 8) ):
-  The` servic e`,  `s tage` a nd `clu s ter `p r o pe rties have been re mo v e d. 
- A new  prope r ty  c a lled `en dp oin t` h a s  been  add e d.  The new  `endp o in t`  effect iv ely en co des  th e inf o rmat ion of  the thr ee re m oved propertie s .
- A new pro p er t y  c a lled  `p ost-deploy`  has been  add e d(se e  [Pos t dep lo y me n t hooks](#post-depl oy ment-h ooks)  for more inf o).
- The` d i sableAut h` p r op e rty has been r emove d. If youd on't wan t you r Prisma  API to r e q uire aut hen tic ati on, s im ply omit the` s ecre t`  proper ty. 
- The`sc hem a`pro pe rty has b een remo ve d.  N ot e t hat t h e Prisma  C LIwi llnot b y  defau lt do wnlo ad  t h e G raphQLs ch e m a (c om mo nlycal le d `pr isma . gra phql`)for yourPri s ma A PI  a ny more ! If you want  t o get acce ss  to  the G r a phQL sch ema of your Prisma API, you nee d t o con figu re a [pos t d eplome nth ook](# post-d eploy me nt- h o oks)a c co rdi ng ly.

####E x amp le: L oc al d eployme nt

Consider this* *ou tdated** vers ion  of` p ri sma . ym l `:
` ` `ym l service: myserv ice
stage:  d e vcluster: l o cal 
datamod el: dat amode l .graphq l
```

Af ter migra te d to * *Pr isma 1.7** , the fi le will h a ve th e  f ollow ing  struc tu re: 

``` yml
en d poi nt: h ttp:// lo calhos t:446 6/ myservic e/dev
datamodel: datamo del.gr aphql 
`` `

### Ex amp l e:Deploying  toa Prisma S and box  in t heC loud
Con s id er
 into_it (while_removing `service`, `stage` and_`cluster`).
- **Your_API_is _NOT__deployed_to a [Prisma_Cloud](https://www.prisma.io/cloud) server**: The_CLI prints a warning_and provides hints_how_to perform the updates (see below for more info).

## Terminology

- **Prisma Clusters** are renamed_to_**Prisma Servers**
-_**Development_Clusters**_are renamed to **Prisma Sandbox**

##_Service configuration in `prisma.yml`

### New_YAML structure

The_service configuration inside `prisma.yml` is based on a_new_YAML structure (find_the updated docs [here](https://www.prisma.io/docs/reference/service-configuration/prisma.yml/yaml-structure-ufeshusai8)):

- The `service`, `stage` and `cluster`_properties have been removed.
- A new_property called `endpoint`_has_been_added. The new `endpoint`_effectively encodes the information of the_three removed properties.
- A new property_called `post-deploy` has been added (see [Post_deployment hooks](#post-deployment-hooks) for more info).
- The_`disableAuth` property has been removed._If you_don't want your Prisma API_to require authentication,_simply omit_the `secret` property.
-_The `schema` property has been removed._Note that the_Prisma CLI will not by default_download_the GraphQL schema_(commonly_called_`prisma.graphql`) for_your Prisma API_any_more! If_you_want to get access to the_GraphQL_schema of your Prisma API, you need_to configure a [post_deploment_hook](#post-deployment-hooks) accordingly.

#### Example: Local_deployment

Consider this **outdated** version of_`prisma.yml`:

```yml
service: myservice
stage: dev
cluster: local

datamodel: datamodel.graphql
```

After migrated_to **Prisma_1.7**, the_file will have the following structure:

```yml
endpoint: http://localhost:4466/myservice/dev
datamodel: datamodel.graphql
```

### Example: Deploying to_a Prisma Sandbox in the Cloud

Consider