Ability to export database connections without including datasets

What is the problem or goal the end user is trying to solve or accomplish?

Users want to export only database connection objects from Preset/Superset via the CLI or UI, without exporting the datasets associated with those databases. This is often needed when managing connections independently of the datasets, such as for migration, testing, or version control.

How are they solving it currently?

Currently, when a database connection is exported (either via CLI or UI), Superset automatically includes all related datasets.

• Users must manually delete the datasets folder/files from the exported package if they only want the database connection.

• This workaround is repetitive and error-prone, especially when handling multiple exports or scripting automated processes.

What is the recommended solution by the Customer?

ntroduce an option/flag (e.g., --exclude-datasets or similar) in the CLI and a corresponding toggle in the UI to allow exporting only the database connection object, without automatically bundling datasets. This would provide users with more granular control over what gets exported.