question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Disable `refresh dbt` button for certain setups

See original GitHub issue

Description

If you’re:

  • connected to a warehouse
  • not connected to a hosted dbt project (i.e. local dbt project)
  • Then, disable the refresh dbt button

The “disabled” state should be greyed out text, with text on hover that says:

You’re still connected to a local dbt project. To keep your Lightdash project in sync, you need to update your dbt connection. Find out how to do that here.

What problem does this solve?

People are clicking on refresh dbt and it’s giving them an error

Having the button disabled instead of disappeared means that we have another entrypoint for getting people to update their connection information (instead of just relying on the intro tour in Intercom).

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
ZeRegocommented, Oct 12, 2022

ok, I think I understand now. This is supposed to affect only those who created the project from the CLI, on cloud, right ?

correct 👍

I’m happy as long as it doesn’t change our local environment (so we need to ensure it is only happening on cloud)

Agree, dev env and users using the DBT_PROJECT_DIR env var should still be able to use the “local dbt server” option and have “refresh dbt” button.

1reaction
ZeRegocommented, Oct 11, 2022

Technical note:

  1. We should add a DbtProjectType.NONE or similar
  2. Support that type in the form (UI) and a callout saying they will have to sync their explores via the command lightdash deploy
  3. Use that type when creating projects from the CLI ( also previews )
  4. Hide refresh dbt button when type is DbtProjectType.NONE
Read more comments on GitHub >

github_iconTop Results From Across the Web

How to prevent (accidental) full refreshes for a model
To fully refresh this model, one would simply run the command dbt run --full-refresh --vars 'allow_full_refresh: True' . This is only an example ......
Read more >
dbt Data Freshness | Integrations - Mode Support
The integration allows Mode users to present information about when source data was last refreshed for a report, by mapping the tables used...
Read more >
Understanding dbt Incremental Strategies part 2/2 - Medium
I suggest to always configure your incremental model in the config() block of your file. It allows you to set specific parameters per...
Read more >
Transformations for dbt Core - Scheduled in Code | Setup Guide
In the pop-up window, select SSH, then copy the repository URL that appears in the text box below (be sure to remove the...
Read more >
dbt Release v0.21.0. Extract, Learn, Teach is a series…
Move that Config block where it belongs. The dbt Labs team has been working hard at bridging the configurations and properties in projects....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found