Cloud Run does not load .env variables about cloud-run-samples

[grayside]

Hi @Pierre-Alexandre35, thank you for the detailed bug report. Unfortunately, this issue tracker has limited visibility and scope - basically, it's just for reporting issues with the samples contained here and is only watched by the folks who work on these samples.

In the future, you're likely to get a faster response on StackOverflow's "google-cloud-run" tag.

It looks like your .env file may not be inside the the application code running on Cloud Run. A likely reason for this is the following combination of behaviors:

• The .env file is configured in your .gitignore
• The application does not have a .gcloudignore

When these two problems happen at the same time, gcloud commands to build your application into a container do not upload any of the files covered in your .gitignore. Many dotenv implementations silently fallback to default values if the .env file is missing.

If this is your problem, creating an empty .gcloudignore file will fix it. Here's a sample gcloudignore file from the helloworld-shell sample in this repo:

cloud-run-samples/helloworld-shell/.gcloudignore

Lines 1 to 12 in 836133e

	# The .gcloudignore file excludes file from upload to Cloud Build.
	# If this file is deleted, gcloud will default to .gitignore.
	#
	# https://cloud.google.com/cloud-build/docs/speeding-up-builds#gcloudignore
	# https://cloud.google.com/sdk/gcloud/reference/topic/gcloudignore
	# Exclude locally vendored dependencies.
	vendor/
	# Exclude git history and configuration.
	.git/
	.gitignore

If this does not help, please comment back here with a link to your StackOverflow question!