[google-appengine] Re: [app-engine] multiple app.yaml files

[Jason Yoon]

"The app.yaml file must be located in your application's root directory. 
You may check this detail and general app.yaml-related information on the 
"Configuring your App with app.yaml" documentation page 
.
 
This means that the ./config/dev/ directory, where app.yaml is saved, must 
be regarded as the root directory: you should copy all your app's other 
directories and files accordingly, to dev, from your home directory, or 
where stored initially. Once this file copy succeeds, and your app 
directories are placed under the root "dev" directory, the "gcloud app 
deploy ./config/dev/app.yaml" command should succeed, as expected."

Or alternatively you could have multiple "app.yaml" files in the root 
directory, and just change the name of each file as well as provide the 
service flag. For example, app.yaml can be the default service, dev.yaml 
can be the dev service, and stage.yaml can be the stage service (the name 
of the file doesn't have to be "app"). Then you can just do `gcloud app 
deploy app.yaml` or `gcloud app deploy dev.yaml`, etc.

The parameters of `gcloud app deploy` is actually an array of 
"deployables", meaning you can update multiple services at the same time. 
So if you wanted to update all environments, you can do `gcloud app deploy 
dev.yaml stage.yaml app.yaml` if you wanted.



On Tuesday, April 10, 2018 at 11:45:37 AM UTC-4, Raunak Gupta wrote:
>
> I've multiple services running for the same app under the name "dev",  
> "stage" and "default" (which is prod). 
>
> The deployment is done using the standard `gcloud app deploy app.yaml`.
>
> It is frustrating having to update app.yaml with service name before each 
> deployment. I tried overcoming this by creating multiple app.yaml file for 
> each environment. As an example, for dev, the `app.yaml` file would be 
> stored under ./config/dev/app.yaml'. But now when I deploy using `gcloud 
> app deploy ./config/dev/app.yaml`, gcloud only uploads what is in the 
> /config/dev directory (and nothing from home directory). 
>
> Is there a way to change this behaviour, or an alternative way to manage 
> multiple environments better?
>
> Thanks! 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d66fd7f3-f183-4359-9303-688fcf4ad2d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine Migration from V1 to V2

['Kenworth (Google Cloud Platform)' via Google App Engine]

I can see that you also posted this on StackOverflow 

 which 
we also monitor, and already getting responses from the community. I 
encourage everyone experiencing the same issue to continue discussions on 
StackOverflow 

 
since this forum is not meant for specific 1-on-1 technical issues, but for 
general discussion of the platform and its services.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/21b2d3e2-7dde-49b2-9771-a71a6d0cc348%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: [app-engine] multiple app.yaml files

['George (Cloud Platform Support)' via Google App Engine]

The app.yaml file must be located in your application's root directory. You 
may check this detail and general app.yaml-related information on the 
"Configuring your App with app.yaml" documentation page 
.
 
This means that the ./config/dev/ directory, where app.yaml is saved, must 
be regarded as the root directory: you should copy all your app's other 
directories and files accordingly, to dev, from your home directory, or 
where stored initially. Once this file copy succeeds, and your app 
directories are placed under the root "dev" directory, the "gcloud app 
deploy ./config/dev/app.yaml" command should succeed, as expected. 

Depending what your services entail, you might use the "service: 
service_name" settings in app.yaml. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/22beaa20-398d-4879-b1bc-84704a10922b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] [app-engine] multiple app.yaml files

[Raunak Gupta]

I've multiple services running for the same app under the name "dev",  
"stage" and "default" (which is prod). 

The deployment is done using the standard `gcloud app deploy app.yaml`.

It is frustrating having to update app.yaml with service name before each 
deployment. I tried overcoming this by creating multiple app.yaml file for 
each environment. As an example, for dev, the `app.yaml` file would be 
stored under ./config/dev/app.yaml'. But now when I deploy using `gcloud 
app deploy ./config/dev/app.yaml`, gcloud only uploads what is in the 
/config/dev directory (and nothing from home directory). 

Is there a way to change this behaviour, or an alternative way to manage 
multiple environments better?

Thanks! 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/fbcb4e68-c0bf-49a6-995a-69645d1ea649%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google App Engine Migration from V1 to V2

[Arun Prasath]

*I have migrated my Google App Engine end point. There is one jar and war 
file available in my V1 libs folder. But after I migrated, there is war 
file only available in my v2 libs folder. Without jar file I cannot proceed 
my work. Is anything I missed in the migration process ? Help from anyone 
is appreciated.*

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ea72ea79-c454-4bfa-8e86-a449bb6e9c4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.