To answer Brian's questions:
1) The gcloud app deploy documentation
<https://cloud.google.com/sdk/gcloud/reference/app/deploy> mentions
DEPLOYABLES as such:
A DEPLOYABLE can be a service's .yaml file or a configuration's
.yaml file.
It might help to update the documentation to be more specific about what is
meant by 'configuration's .yaml file', but this does mean any .yaml file
listed in the 'Configuration files' section of the documentation
<https://cloud.google.com/appengine/docs/python/configuration-files> such
as 'queues.yaml, dispatch.yaml, dos.yaml, cron.yaml and index.yaml'.
2) The dispatch rules are applied project level, so the --version flag is
ignored. This is the same behavior as the standalone SDK.
3) The --version= flag specifies the version for this deployment. If you
are targeting different versions for different services, you'll need to use
separate commands.
4) This part of the docs is now incorrect, and should be edited. Following
the link to 'app.yaml
<https://cloud.google.com/appengine/docs/python/config/appref>' shows that
the 'version: ' field is not present, and if you test 'gcloud app deploy
app.yaml' with either 'version: ' or 'project: ' present, you'll get an
error.
For Attila:
1) I've tested parallel deployments for the same version by backgrounding
them in a terminal and it appears to work, however I can't guarantee there
won't be any issues as its not supported. Eg.
$ gcloud app deploy -q -v myversion app.yaml & \
gcloud app deploy -q -v myversion module1.yaml & \
gcloud app deploy -q -v myversion module2.yaml
The '-q' flag is necessary to avoid the prompt. Otherwise, there's no
builtin solution, and you might consider filing a feature request
<https://code.google.com/p/google-cloud-sdk/issues/list>.
2) Routing with dispatch.yaml is and has always been covered by the
documentation, specifically 'How requests are routed
<https://cloud.google.com/appengine/docs/python/how-requests-are-routed>'
and the 'dispatch.yaml
<https://cloud.google.com/appengine/docs/python/config/dispatchref>'
reference. Using dispatch.yaml does not remove subdomain routing, but you
can use it to route by domain. The exception is on the development server,
where there exists no subdomain to route on (you could add one in
/etc/hosts, but this would be another feature request to support it).
* Note:* Dispatch rules apply to the URLs in a cron file
<https://cloud.google.com/appengine/docs/python/config/cron>.
Note that dispatch rules also apply to URLs that are used in cron
configuration
<https://cloud.google.com/appengine/docs/python/config/cronref> or in task
queue configuration
<https://cloud.google.com/appengine/docs/python/config/queueref>.
The server does not support dispatch.yaml file rules that include
hostnames (for example, url: "customer1.myapp.com/*").
On Saturday, January 7, 2017 at 2:54:10 AM UTC-5, Attila-Mihaly Balazs
wrote:
>
> Great discussion, definitely something I'll keep my eye on since
> dev_appserver doesn't seem to be maintained any-more (for example the
> version check doesn't show that "1.9.49" is available).
>
> Couple of follow-up questions:
>
> - is there a built-in solution for deploying multiple modules in parallel?
> (we have 8 modules and it would be nice to speed up deployment)
> - could we get a clear documentation on how routing is affected by
> dispatch.yml? in particular:
> - does having dispatch.yml mean that individual services can no longer
> be accesses via the "servicename-dot-appname.appspot.com" syntax?
> - does the answer to the above change depending on if the dispatch.yml
> ends in a "*/*" url or not?
> - do requests from PUSH taskqueues go trough the dispatcher? do requests
> from cron?
>
> Thank you,
> Attila
>
--
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 [email protected].
To post to this group, send email to [email protected].
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/d943d05e-6a7b-412b-8920-4e083ca3fb80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
