Whitelist of production database(s)

[f3l1x]

I have an idea about whitelisted database which will prevent of calling migration:reset command. Just for security reasons. What do you think?

[JanTvrdik]

Whitelist of production database

I assume you mean whitelist of dev databases, otherwise it would useless.

---

The problem is that local database often has the same name as production database. Maybe would could create e.g. table migrations_dev on localhost and allow resetting database only when the table exists?

[f3l1x]

Something like that, I have not figured this out, just posting an idea. :-)

[Mikulas]

Yep, this is needed. This could probably best be implemented as a check against an environment variable. It probably should be an opt-in featured. The env name could be defined in the configuration.

Also it should be noted this is mostly preventing an user error and not adding very much “security”. With this in mind, the reset command could also ask for a nonce such as current datetime string.

[mabar]

I would like to add new configuration option to extension. Something like registerResetCommand. Simple, two lines of code solution.

[f3l1x]

Closing it, don't need it anymore.

[dakur]

@f3l1x Why have you closed this? There is similar issue #84 and it is not still resolved as there is still simple way to destroy whole production database in a moment. You don't want to allow such thing without any confirmation. Can we please reopen it and agree on some resolution?

[jkuchar]

Isn't it possible to just deregister the command from DI services?

[dakur]

Yes, use:

services:
	migrations.resetCommand: false

[jkuchar]

To be precise, we use a environment based config, that is loaded only in production environment, where it deregisters that command: