Upgrading version 0.15.1 → 0.16.0 cause "Runtime Error: Could not find profile named 'elementary" #1702
Comments
|
I have the exact same issue after upgrading from 0.15.1 to 0.16.1. Note that I also upgraded dbt from 1.7.x (dbt-core was 1.7.10 and dbt-bigquery was 1.7.6) to 1.8 at the same time. |
|
Another tip, in case it helps. I'm fixing the following: and
I don't know if it makes a difference but mentioning it just in case: I'm using pyenv virtualenv in ubuntu to handle my virtual environments, hopefully that's not the issue here. |
|
Hey,
@geo909 from the logs you provided, i assume that in your can you try setting the keyfile path to the absolute path of the file and see if this helps, something like |
|
@ofek1weiss Still doesn't work: ferryhopper:
target: dev_user
outputs:
dev_user:
dataset: user_{{ env_var('DBT_USER') }}_dbt
job_execution_timeout_seconds: 600
job_retries: 1
keyfile: "/home/tzanakis/git/bi/dbt/service-account-dbt.json"
location: EU
method: service-account
priority: interactive
project: bigquery-xxxxxx
threads: 2
type: bigqueryOutput: Tried this one too, just in case: Note that, if I change the virtual environment to switch back to 0.15.1 and change absolutely nothing else, both the above commands run without errors. |
|
@ofek1weiss run command: |
|
@geo909 did you try both at the same time? (setting both the keyfile and the command flags to absolute paths)? or was it one at a time? the reason i am asking is that in the logs for the second command, you can see the log |
Oops.. Apologies, that was my mistake. I was trying the full path in the wrong profile. So, the following combination finally worked!
Played around with different expressions just in case, but relative paths expressed in different ways do not work, as expected probably. For example, the following:
|
|
@geo909 Firstly, that is great to hear :)
|
|
No, the last combination does not work. To recap: Works
Output: Does NOT work
Output: Let me know if you need to me to try anything else! |
|
ohhhhhhh, you use elementary |
Ough.. I had tried with 0.16.1 earlier (see here) with the error again but I must have switched to 0.16.0 when playing around with the versions. Apologies again! But we're getting there. Indeed now 0.16.1 works with the following combination:
But if I switch the keyfile parameter in profiles.yml to simply Note that dbt runs fine with |
|
@ofek1weiss I cloned elementary's repo and played around, the issue is with this commit. If you comment-out the line Edit: Tried with the latest version of elementary, and it's the same if I comment out this line, this is what brakes it for me. |
|
@geo909 i see, thanks for the deep dive 🙏 |
Great, good to know! Do you have an estimate about how long this could take, by any chance? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Yesterday I upgrading elementary-data[bigquery] from 0.15.1 to 0.16.0, but Upgrading caused a Runtime Error.
I include below the contents of the files and logs that are considered necessary for troubleshooting.
To Reproduce
Steps to reproduce the behavior:
pyproject.toml
profiles.yml
packages.yml
dbt_project.yml
edr report --env prod --project-name {project_id} --days-back=30Expected behavior
A report of the dbt project will be generated.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: