Skip to content

Minor fix to Databricks Apps deployment script#32

Closed
FNeiva wants to merge 1 commit into
databrickslabs:mainfrom
FNeiva:deploy-script-fix
Closed

Minor fix to Databricks Apps deployment script#32
FNeiva wants to merge 1 commit into
databrickslabs:mainfrom
FNeiva:deploy-script-fix

Conversation

@FNeiva

@FNeiva FNeiva commented Sep 10, 2025

Copy link
Copy Markdown

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.

MrBlack1995 added a commit to MrBlack1995/kasal that referenced this pull request Jun 3, 2026
When deploying to a non-DEFAULT Databricks CLI profile, the import-dir
commands were missing the --profile flag, causing uploads to go to the
wrong workspace.

Cherry-picked from PR databrickslabs#32 by Felipe Cruz Neiva Campos, adapted to
current hybrid upload strategy.

Co-authored-by: Isaac
MrBlack1995 added a commit to MrBlack1995/kasal that referenced this pull request Jun 3, 2026
When deploying to a non-DEFAULT Databricks CLI profile, the import-dir
commands were missing the --profile flag, causing uploads to go to the
wrong workspace.

Cherry-picked from PR databrickslabs#32 by Felipe Cruz Neiva Campos, adapted to
current hybrid upload strategy.

Co-authored-by: Felipe Neiva <felipe.pqi@gmail.com>
Co-authored-by: Isaac
MrBlack1995 added a commit to MrBlack1995/kasal that referenced this pull request Jun 3, 2026
When deploying to a non-DEFAULT Databricks CLI profile, the import-dir
commands were missing the --profile flag, causing uploads to go to the
wrong workspace.

Cherry-picked from PR databrickslabs#32 by Felipe Cruz Neiva Campos, adapted to
current hybrid upload strategy.

Co-authored-by: FNeiva <2091157+FNeiva@users.noreply.github.com>
Co-authored-by: Isaac
MrBlack1995 pushed a commit to MrBlack1995/kasal that referenced this pull request Jun 3, 2026
When deploying to a non-DEFAULT Databricks CLI profile, the import-dir
commands were missing the --profile flag, causing uploads to go to the
wrong workspace.

Cherry-picked from PR databrickslabs#32 by Felipe Cruz Neiva Campos, adapted to
current hybrid upload strategy.

Co-authored-by: FNeiva <2091157+FNeiva@users.noreply.github.com>
Co-authored-by: Isaac
@MrBlack1995

Copy link
Copy Markdown
Contributor

Hi @FNeiva — thanks for this fix! We've integrated your change into PR #51 (our feature/flow branch) which consolidates multiple pending PRs into a single release batch.

Your commit authorship is preserved so you show as a contributor on #51.

Could you close this PR when you get a chance? No need to merge to main separately — it'll go in with #51.

Thanks!

@FNeiva

FNeiva commented Jun 3, 2026

Copy link
Copy Markdown
Author

@MrBlack1995 Absolutely, closing it now!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants