You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is a "classic" bug, or a improvement request. The fact is that databricks-cli fails to recover the token from the configuration file when used inside a Gitlab pipeline. Anything works until you try to use the token.
BTW, the solution is don't initialize the databricks-cli, just pass TOKEN and WORKSPACE URL as env VARS.
Steps to reproduce the behavior
Of course, you need a Gitlab pipeline.
obtain a person token from databricks
In the Gitlab's repo settings -> CI/CD -> variables -> add a new VAR "TF_VAR_personal_token" to hold your PERSONAL TOKEN and set it Masked & Expanded. ( actuall, any var name is fine, but DATABRICKS_TOKEN )
Use a YAML file like that where the databricks cli is initialized by writing the configuration file:
Describe the issue
I don't know if this is a "classic" bug, or a improvement request. The fact is that databricks-cli fails to recover the token from the configuration file when used inside a Gitlab pipeline. Anything works until you try to use the token.
BTW, the solution is don't initialize the databricks-cli, just pass TOKEN and WORKSPACE URL as env VARS.
Steps to reproduce the behavior
Of course, you need a Gitlab pipeline.
Expected Behavior
The Gitlab pipeline ends reporting the current user info
Actual Behavior
Anything is perfect until
databricks current-user me
is executed. You will get this message:OS and CLI version
Linux, Databricks CLI V0.213.0
Debug Logs
The text was updated successfully, but these errors were encountered: