-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#186 Deploy pipeline fails with "staging: no such target. Available t… #187
Conversation
…vailable targets: Setting the catalog name in databricks.yml Updated bundle and pipeline yml files to use the catalog variable in databricks.yml
@ThomasHenckel thanks so much for creating this PR! I ran the tests and they seem to be failing, would you mind taking a look and resolving where you can? Happy to help re-run on future commits |
...{.input_root_dir}}/{{template `project_name_alphanumeric_underscore` .}}/databricks.yml.tmpl
Outdated
Show resolved
Hide resolved
…eric_underscore` .}}/databricks.yml.tmpl Co-authored-by: Arpit Jasapara <[email protected]>
Unfortunately I have not setup local to run the large unit tests, when I look at the error it is failing at |
@ThomasHenckel I fixed the tests in another PR, though it seems the changes weren't being picked up here. Fixed and merged the PR, thanks for making the contribution! |
## Changes databricks/mlops-stacks#187 broke mlops-stacks deployments for non-UC projects. Snoozing the test until upstream is fixed. ## Tests The test is skipped on my local machine. CI run will verify it's also skipped on Github Actions runners.
## Changes This test was broken due to upstream change: databricks/mlops-stacks#187 Fixed in upstream change: databricks/mlops-stacks#188 ## Tests Test passes now
…argets:
Setting the catalog name in databricks.yml
Updated bundle and pipeline yml files to use the catalog variable in databricks.yml