Use env in migrations?

[djMax]

is it possible to use environment information (not NODE_ENV, the db-migrate env) in migration scripts? I'm wondering if I can model "seeding" as a migration that only runs in a particular env.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/37996228-use-env-in-migrations?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F73887&utm_medium=issues&utm_source=github).

[wzrdtales]

@djMax Well, every migration gives you full access to the node js api, due to being javascript itself.

Just access process.env and control this yourself.

[wzrdtales]

And if you ment the db-migrate env, from reading your question again, I just noticed you probably ment this (NODE_ENV is actually also not the same as process.env), you can access this though.

if you ment this information, that is not yet passed though. But you could access it over the internals: internals.currentEnv || internals.argv.env

[wzrdtales]

But we could very easily add this to the base driver.

[djMax]

Yes, I meant the db-migrate env. Would be nice to have access to that and the corresponding config in the migrations (perhaps in setup or in the driver/db arg of the up/down methods.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.