-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.env file not created when using --dont-exe-cf
, creates confusing ux and errors later
#199
Comments
This was referenced Dec 23, 2020
Open
Open
Open
Open
Open
Open
This was referenced Sep 5, 2021
Open
Open
Open
Open
Open
Open
This was referenced Jan 12, 2022
[Snyk] Security upgrade serverless-google-cloudfunctions from 1.2.0 to 2.4.1
romathur/serverless#101
Open
[Snyk] Security upgrade serverless-google-cloudfunctions from 1.2.0 to 2.4.1
romathur/serverless#102
Open
Open
Open
Open
This was referenced Jan 12, 2022
Open
This was referenced Feb 9, 2022
Open
Open
Open
[Snyk] Security upgrade serverless-google-cloudfunctions from 1.2.0 to 2.4.1
romathur/serverless#105
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This was a confusing user experience raised by @zoonywhoop.
If you create a new project, using our own suggested best practices of
--dont-exe-cf
with a Power User for deploys, and using an Admin via the UI to create the resources, an env file doesn't not get initialized in the bucket.This ends up being very confusing because now all deploys fail for the stage because an env file does not exist. And to make matters even worse env set also fails because it can't pull the env file to begin with. 😦
The text was updated successfully, but these errors were encountered: