Set KAMAL_DESTINATION for envify command #666
Closed
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.
Since destinations usually map to an environment such as a Rails environment it'd be helpful to load the current destination so that you can more easily use a destination template file. I made the assumption that we load the clear variables from Kamal but right now envify just loads the template and writes the output destination file, no clear/secret loading from Kamal.
For example:
.env.template.erb
.env.staging.erb and .env.production.erb
Which would generate something like this when running
kamal envify -d staging
:#352 is related from the perspective of having a template for your destination files.