`plan --select-model` picks up unrelated Python Models

[hustic]

I am playing around with the --select-model option in plan.

I have made changes to two SQL Models and running sqlmesh plan env picks them up no problem:

New environment `env` will be created from `prod`
Summary of differences against `env`:
Models:
├── Directly Modified:
│   ├── shared_views__env.sims_checkin
│   └── business_central__env.kits
└── Indirectly Modified:
    └── shared_views__env.bc_kits

However, when I use the --select-model option like so: sqlmesh plan env --select-model business_central.kits, SQLMesh lists some un-related Python models as Modified.

New environment `env` will be created from `prod`
Summary of differences against `env`:
Models:
├── Directly Modified:
│   ├── business_central_raw__env.sales_line
│   ├── business_central_raw__env.kit_collections
│   ├── business_central__env.kits
│   ├── business_central_raw__env.kits
│   ├── business_central_raw__env.item_list
│   ├── business_central_raw__env.subscriptions
│   ├── business_central_raw__env.app_sample
│   └── business_central_raw__env.project_subscription
└── Indirectly Modified:
    ├── business_central__env.sales_line
    ├── business_central__env.item_list
    ├── shared_views__env.bc_kits
    ├── business_central__env.subscriptions
    ├── business_central__env.kit_collections
    ├── shared_views__env.bc_projects
    ├── business_central__env.project_subscription
    └── business_central__env.app_sample

The Python models are the ones from the business_central_raw schema. Am I doing something wrong?

[izeigerman]

Hey @hustic!

For those Python models that get picked up, what diff gets printed?

What's SQLMesh version?

Can you please come up with a minimal reproducible example?

[tobymao]

closing this for now as there isn't enough information to reproduce or fix this issue