-
Notifications
You must be signed in to change notification settings - Fork 324
Open
Description
Hi!
My dev database includes a schema (google_vacuum_mgmt) generated by my cloud provider (GCP) for which I have no control over.
This prevents any migration using the command atlas schema apply with the error:
Error: sql/sqlimport: taking database snapshot before computing module state: sql/migrate: connected database is not clean: found schema "google_vacuum_mgmt"
I've tried the argument --exclude google_vacuum_mgmt*, and it works in other commands like schema_inspect but not for the snapshot phase of schema apply.
Shouldn't exclude also scope the snapshot phase?
Thank you!
Metadata
Metadata
Assignees
Labels
No labels