Closed tubiskasarus closed 7 months ago
Apologies for submitting the pull request using my test account. I have now transferred the ownership of the forked repository to my main account. I wanted to clarify this to avoid any suspicion. 🙏
@tubiskasaroos can you please rebase your branch? Looks it contains some irrelevant changes
@kravets-levko, I’m a bit apprehensive because this is my first time contributing on GitHub. I’ve pushed a change from a forked repository to the original one, and I attempted to rebase and address the previous issue related to signing off. However, I lack confidence in whether my actions were correct. Would it be possible to receive some assistance, or should I create a separate fork and submit another pull request?
@tubiskasaroos sorry if my message feels rude - there was no such intention at all. Of course I can help you.
Go to your fork, select main
branch in dropdown. Under that dropdown there's a message "This branch is 2 commits behind databricks/databricks-sql-go:main", and next to it is a "Sync fork" button. Click it and select "Update branch".
Next, go to terminal/command line on your computer, and run these commands:
git checkut main
git pull
git checkout patch-1
git pull
git merge main
git push
There should be no conflicts, but in a case of any - resolve them.
I'll keep an eye on this PR. Please feel free to ping me if any questions.
Much better now 🙂 Thank you!
All good. Thank you so much for your help!
AzureTenantId was hardcoded as a constant which was linked to ".staging.azuredatabricks.net". Therefore, if the host URL was for example from ".azuredatabricks.net", it failed to detect ClientId. I replaced the const value with a map to find the AzureTenantId based on the DSN host.