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
When using the CLI to interact with Databricks Asset Bundles, it needs to fetch and install some Terraform libraries. This causes problems when installing the CLI in a Docker image and then using that CLI in an airgapped environment.
This is a re-raising of the issue brought up in #1238 (comment) since it's been a while since that was posted and I still have no idea when a solution will be available.
Steps to reproduce the behavior
Install CLI
block access to hasicorp.com
try to run databricks bundle ...
Expected Behavior
I would expect to be able to install all transitive dependencies when running the installer, and not have them dynamically installed later.
Actual Behavior
I have to manually install and configure terraform, or use a standalone Docker image, which does not really fit with my workflow here.
OS and CLI version
NA
Is this a regression?
No
Debug Logs
NA
The text was updated successfully, but these errors were encountered:
Describe the issue
When using the CLI to interact with Databricks Asset Bundles, it needs to fetch and install some Terraform libraries. This causes problems when installing the CLI in a Docker image and then using that CLI in an airgapped environment.
This is a re-raising of the issue brought up in #1238 (comment) since it's been a while since that was posted and I still have no idea when a solution will be available.
Steps to reproduce the behavior
databricks bundle ...
Expected Behavior
I would expect to be able to install all transitive dependencies when running the installer, and not have them dynamically installed later.
Actual Behavior
I have to manually install and configure terraform, or use a standalone Docker image, which does not really fit with my workflow here.
OS and CLI version
NA
Is this a regression?
No
Debug Logs
NA
The text was updated successfully, but these errors were encountered: