Running appengineDeploy Creates .gcloudignore File by Default
See original GitHub issueI’ve noticed starting recently that running ./gradlew appengineDeploy
on a Gradle project creates the .gcloudignore
file within the staging directory. I was wondering if this kinda behaviour was added recently? I had to run gcloud config set gcloudignore/enabled false
before deploying since otherwise the .gcloudignore
file seems to prevent files for deploying correctly. 🤔
Any help or thoughts on this will be greatly appreciated. 😄
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (7 by maintainers)
Top Results From Across the Web
gcloud topic gcloudignore | Google Cloud CLI Documentation
application-default ... Gcloud commands may generate a .gcloudignore file; see the individual command help page for details. The following gcloud commands ...
Read more >Deploying to Google Cloud Platform (GCP) - Quarkus
This will create a default service for your App Engine application. ... upload all your project files (the list can be reduced via...
Read more >gcloud app deploy : This deployment has too many files
Maybe your need ignore some files in file .gcloudignore ... When you create an app, App Engine creates a default bucket.
Read more >Google Cloud - Jmix Documentation
Inside the project, you need to create an Application that will run the deployed JAR file and Database that will be used by...
Read more >GCP App Engine - Deploy and Split traffic (Part 2) - YouTube
For some reason, App Engine is trying to run the application using Python 2. What file would you check and possibly modify to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@SudharakaP the internal bug is marked fixed; the default
.gcloudignore
will no longer have thebuild/
entry. The next Cloud SDK may contain this fix (although I can’t guarantee 100%). And of course, you cannot expect that your users are always using the latest Cloud SDK.After further investigation, we have found that this change was introduced in version 292.0.0. As a workaround, while it is being fixed, you could revert/pin to 291.0.0 via gcloud components update --version=291.0.0 .