Atlas just ignores Pro resources silently when not logged in. #3607
Description
How to reproduce
- Install atlas and don't log-in.
- Prepare the environment with a schema file with tables but also add a trigger (resource which is locked behind Pro).
- Realise that it will migrate properly the tables but will ignore completely the trigger without warning.
- Login and set-up the trial.
- Run the exact same command.
- Realise that now it works (not the point).
What is wrong
- It silently ignores Pro entities in the migration check diff when not logged in
- It should at least warn somehow that "Hey, this is a Pro feature".