You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, when I create a preview environment, all of the tables show in the sidebar and there are no subheadings or anything.
Instead, I want the preview environment to match what's in production when it comes to tables configuration (by default).
There should still be a way to override this in the CLI (e.g. imagine I listed out exactly which tables to include/not include in my production instance, then I added a new table and wanted it to appear in the preview environment).
It could be something like lightdash preview --table-configuration=none Other potential options for table-configuration could be =tags, =list, or =prod then you could have like --table-configuration-tags=lightdash, etc.
But, for now, the default is just lightdash preview --table-configuration=prod and there's an option to turn this off (using --table-configuration=none)
The text was updated successfully, but these errors were encountered:
Description
Right now, when I create a preview environment, all of the tables show in the sidebar and there are no subheadings or anything.
Instead, I want the preview environment to match what's in production when it comes to tables configuration (by default).
There should still be a way to override this in the CLI (e.g. imagine I listed out exactly which tables to include/not include in my production instance, then I added a new table and wanted it to appear in the preview environment).
It could be something like
lightdash preview --table-configuration=none
Other potential options fortable-configuration
could be=tags
,=list
, or=prod
then you could have like--table-configuration-tags=lightdash
, etc.But, for now, the default is just
lightdash preview --table-configuration=prod
and there's an option to turn this off (using--table-configuration=none
)The text was updated successfully, but these errors were encountered: