imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Wed May 15 09:19:06 UTC 2024

Browse source
This commit is contained in:
Automated 2024-05-15 09:19:06 +00:00
parent e8259d86b1
commit 3b84182be4
193 changed files with 10091 additions and 581 deletions
Download patch file Download diff file Expand all files Collapse all files

11
gcloud/app/deploy
View file

@ -15,17 +15,16 @@ DESCRIPTION
uploaded. A DEPLOYABLE can be a service's .yaml file or a configuration's
.yaml file (for more information about configuration files specific to your
App Engine environment, refer to
https://cloud.google.com/appengine/docs/standard/python/configuration-files
or
https://cloud.google.com/appengine/docs/flexible/python/configuration-files).
Note, for Java8 Standard apps or Java11/17 Standard apps using bundled
https://cloud.google.com/appengine/docs/standard/configuration-files or
https://cloud.google.com/appengine/docs/flexible/configuration-files).
Note, for Java 8 Standard apps or Java 11/17/21 Standard apps using bundled
services, you must add the path to the appengine-web.xml file inside the
WEB-INF directory. gcloud app deploy skips files specified in the
.gcloudignore file (see gcloud topic gcloudignore for more information).
For Java11 Standard, you can either use the yaml file, a Maven pom.xml, or
For Java 11 Standard, you can either use the yaml file, a Maven pom.xml, or
a Gradle build.gradle. Alternatively, if the application is a single
self-contained jar, you can give the path to the jar and a simple service
configuration will be generated. You can deploy Java11 Maven source
configuration will be generated. You can deploy Java 11 Maven source
projects by specifying the location of your project's pom.xml file, and it
will be built and deployed using App Engine Buildpacks.