AltimateAI / AltimateAI/vscode-dbt-power-user

Bigquery Cost Estimation wouldn't use new profile target

Aperta
#1,588 1 commento 0 reazioni 1 assegnatario Rivendicata da @ralphstodomingo Vedi su GitHub
bug
Lingua principale
JavaScript
Stelle
585
Fork
121
Merge medio
5g 39m
PR unite (30g)
4

Descrizione

### Expected behavior

bigquery cost estimation should use the default profile target we set on profiles.yml even after we change it

### Actual behavior

I tried bigquery cost estimation using my dev profile target, and when i change my default target to prod (or vice versa),
bigquery cost estimation will still calculate using my dev target.

this also happens to compile dbt preview and execute dbt sql feature

### Steps To Reproduce

use bigquery cost estimation feature / compile dbt sql / execute dbt sql,
change default profile target
use the feature again

### Log output/Screenshots

_No response_

### Operating System

Ubuntu 22.04.5 LTS

### dbt version

1.8.6

### dbt Adapter

dbt-bigquery

### dbt Power User version

0.39.20

### Are you willing to submit PR?

- [ ] Yes I am willing to submit a PR!

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.