Because dbt-superset-lineage (0.2.1) depends on sqlfluff (>=0.8.2,<0.9.0) and no versions of dbt-superset-lineage match >0.2.1,<0.3.0, dbt-superset-lineage (>=0.2.1,<0.3.0) requires sqlfluff (>=0.8.2,<0.9.0). So, because seed depends on both dbt-superset-lineage (^0.2.1) and sqlfluff (^1.4.1), version solving failed.

Problems:

1. We wanted to pull dashboards by name and not simply by published status
2. When pushing, we wanted to specify the database by name.
3. When pushing, we wanted to specify the schema name in case of inter-schema table name overlap.

Solutions:

1. Added: --superset-dashboard-name as a option for pulling. It can be daisy chained by using --superset-dashboard-name 'Name One' --superset-dashboard-name 'Name 2'.
2. Added: --superset-db-name to push command
3. Added: --superset-schema-name to push command

Updated the docs to reflect these changes.

In preparation for a second command and to allow for easier orientation between the two, each Typer command should be put to a separate .py file.

Note that this is to be merged to #1.

Hi, is this repo still actively maintained. I have been testing this on a Docker deployment of Superset and unable to disable CSRF tokens. there are a number of threads on this which seem to indicate this is a common issue. Is there a way to ensure this library works for POST commands with SS or any specific steps to disable CSRF.

Created based on internal script.

Changes

• add new dependencies through Poetry that amended poetry.lock and pyproject.toml
• add new command into __init__.py
• add source code to push_descriptions.py
• release as v0.2.0

Tests

• installed via Poetry
• ran on Superset staging with the same result as from internal script

Next steps

• release (tag on Github and publish on PyPI)
• add docs as v0.2.1

As generating docs through dbt docs generate often takes a while, it is less economical to use catalog.json than manifest.json that gets created with every compile (dbt compile or as a part of dbt run or dbt docs generate). This could be done because we don't need information about the current state of database, only what's documented in dbt, because we can only create refs to these tables anyway.

Tested by running the code – resulted in the same output as the code on main.

Why

Asking users for superset_domain did not allow for using HTTP protocol because HTTPS protocol was then hard-coded into the full URL address for API calls. That, however, disallowed for easy run on local (using HTTP).

Changes

• amend in URL for API calls and dashboard links
• rename everywhere
• bump version to 0.1.1

Notes

• #2 to be merged before merging to main

• Refactor the way URL params are being passed to requests in Dashboard listing in pull_dashboards.py, as the previous version has been susceptible to encoding issues.

Signed-off-by: mrshu [email protected]

Hey guys, I adapted the pull_dashboards.py file to use it as, when trying to run the code out of the box, I was not getting the dashboards' table names.

Out of my interpretation GET /dashboard/id doesn't return "table_name" anymore and it was replaced by a similar command I found (GET /dashboard/id/datasets).

Let me know how this sounds to you, I am happy to contribute with my minor edits. Best, Agus