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
{{ message }}
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.
As I understand correctly it is required for the dbx tool. Is it possible to add support of environment variables to dbx or to pass HOST and TOKEN as an arguments?
I think it is important by two reasons:
If dbx can read environment than we can remove this step and it also means that we remove one more place when we are working with sensitive data. As I know databricks-cli works correctly with the environment.
Keep sensitive data in the custom local file could lead us to security issue. Yes, it should be cleaned up after our workflow run, but looks scary anyway. GitHub recommends pass secrets through Settings or Environment file.
The text was updated successfully, but these errors were encountered:
In the
onpush
workflow we have the following step:As I understand correctly it is required for the
dbx
tool. Is it possible to add support of environment variables todbx
or to pass HOST and TOKEN as an arguments?I think it is important by two reasons:
dbx
can read environment than we can remove this step and it also means that we remove one more place when we are working with sensitive data. As I knowdatabricks-cli
works correctly with the environment.Settings
or Environment file.The text was updated successfully, but these errors were encountered: