Add seed envs #636
Open
Add seed envs #636
Conversation
This file contains 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
marccampbell
force-pushed
the
seed-envs
branch
from
60d4e80
to
b45cdb4
Compare
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.
Fixes #632
This change allows seed data to be created for a single environment, multiple environments, or all environments.
This adds a new, optional "env" key to the database spec.
Seed data in a table now has an "envs" key which is a string array of matching envs.
If the target database is not in the envs, it will not apply seed data.
This is added because often seed / fixture data is needed in dev environments that doesn't match what's in production
(Note: this does change the
seedDatakey from a map into an array. This is alpha in 0.13 (unreleased) so no migrations or compatibility concerns exist yet.