-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] dbt init overwrite just appends to profile #4375
Comments
@leahwicz This isn't something I've managed to reproduce locally. I imagine the fix for it is super straightforward, though |
@jtcohen6 yes I was able to do it again so that's why I filed it. I would rate this low on priorities but I would assume its an easy fix as well |
@leahwicz I also wasn't able to reproduce the issue where two profile entries were created, but there definitely is a bug where the user isn't asked for permission to overwrite an existing profile entry. The above PR addresses that. |
@leahwicz I was not able to replicate the original described behavior either. I tested this on 1.0.0 and 1.0.1 with the same results. Can you both provide the versions you were working with so I can be sure I'm comparing apples to apples? |
@NiallRees Never mind my previous comment, that bug is confirmed as is it's fix (thanks again). @leahwicz Let's close this ticket as addressing the issue Niall found and we can open a new one for the double-entry if you can show me how to reproduce it. |
Is there an existing issue for this?
Current Behavior
If you have a profile setup and then you try to setup a new one, it will ask if you want to overwrite existing entry. It just adds another entry and does not overwrite it.
dbt init
again and when it asks you to overwrite the connection choose yes.There are now 2 entries in profile.yml for it
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
No response
Environment
What database are you using dbt with?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: