fix(cpa): generate .env when using the --example flag #12572
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
jacobsfletch changed the title 
denolfe reviewed May 27, 2025
Member
denolfe left a comment
denolfe left a comment There was a problem hiding this comment.
Looking good, just a few notes.
denolfe approved these changes May 30, 2025
Contributor
| 🚀 This is included in version v3.41.0 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
When cloning a new project from the examples dir via create-payload-app, the corresponding
.envfile is not being generated. This is because the--exampleflag does not prompt for database credentials, which ultimately skips this step.For example:
The result will include the provided
.env.example, but lacks a.env.We were previously writing to the
.env.examplefile, which is unexpected. We should only be writing to the.envfile itself. To do this, we only write the.env.exampleto memory as needed, instead of the file system.This PR also simplifies the logic needed to set default vars, and improves the testing coverage overall.