Support databricks policy id for setup_stitch and launch_job commands#44
Merged
pragyan-amp merged 2 commits intoamperity:mainfrom Nov 27, 2025
Merged
Conversation
Contributor
|
Hi @avivshafir Thanks a lot for raising the PR. can you take some time to add tests for following:
Will get it merged once these are validated.. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This pull request introduces support for passing an optional cluster policy ID (
policy_id) when launching Databricks jobs, and Stitch setup command.For example:
Previously the passed command arguments were being ignored (auto confirm didn't work)
Related issue: #43