supabase
Pulling unneeded docker images
I'm writing a slim github action that just dumps the supabase types to check if it's up to date with the PR. Because of this, I don't need to run the majority of the supabase services. To accomplish this I'm running this line with the -x line to exclude them from starting up:
supabase start -x gotrue,realtime,storage,api,imgproxy,kong,mailpit,postgrest,studio,edge-runtime,logflare,vector,supavisor
but then the output is showing that it is still pulling down the following docker images that I'd expect it to skip:
Status: Downloaded newer image for public.ecr.aws/supabase/gotrue:v2.170.0
Status: Downloaded newer image for public.ecr.aws/supabase/storage-api:v1.19.3
Status: Downloaded newer image for public.ecr.aws/supabase/realtime:v2.34.40
Describe the solution you'd like It'd be great if it also skipped downloading these images to save time, but I'm wondering if I'm missing something that would make these still required to download during the start step? I don't have any experiencing writing in go, but I think it may have to do with this function and needs to also check against the excluded services list instead of only checking against the config
+1 came seeking the same - this is basically the discussion in https://github.com/supabase/cli/issues/2407 - there the solution is to use your supabase/config.toml but as pointed out eloquently in #2407 this makes it hard to use the same config.toml for both local dev and CI.
It would be very handy to have more flexible ways to exclude which images are going to be downloaded when running supabase start. I didn't see a way to use an alternative config file as a flag for the CLI, for instance, which would make it trivial for a CI script to be configured differently - a bit janky, but effective and easily visible.
Would be more handy to have this be a CLI flag for the purpose of scripting in CI (assuming that at this point you can't make the breaking change to suddenly not download all of the "excluded" images).
