Minor fix to Databricks Apps deployment script #32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…AULT Databricks CLI profile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When deploying the app to Databricks Apps using the deploy.sh script, it mostly uses the Databricks SDK but for the file upload part it relies on the Databricks CLI. When calling the Databricks CLI to upload files, it was missing the profile argument. Therefore, for anyone trying to deploy the app to a different profile than the DEFAULT one, it would fail.
This change adds a minor fix by checking if the profile has been set on the deployment script. If so, it appends the profile argument to make sure it uploads the source code to the correct Databricks workspace.