Always clear the cache after db-import

[dalin-]

Otherwise you'll get random hard-to-debug errors.

[dalin-]

Or maybe, even better yet, maybe we should always run fire cim to get local config installed.

[dalin-]

Actually we need to do both.

fire import-db
fire cim

Results in no config to import because there's old data stored in Redis.

So we need to both drush cr && drush cim -y after a DB import.

[rigoucr]

Hi @dalin- @Yuvania the Idea/goal behind the db-import command is to import the DB as close as posible to the state that it has over the the selected env, this in case we need to run some debugging over DB data without the influence of any local config change , so , IMporting data Right after importing DB is not a option.

I think this change goes more into the the command src/Robo/Plugin/Commands/DrushDeployCommand.php and add just a drush cr at the very beggining of the command exec, thx

[dalin-]

@rigoucr
I could be convinced not to do a cim after import. But I really suggest doing cr. I've often see people run into strange issues because they don't know how Redis works and don't realize that this step is required.