-
Notifications
You must be signed in to change notification settings - Fork 60
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
Show an error when using a cluster override with 'mode: production' #1994
Conversation
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
Test Details: go/deco-tests/12274679661 |
Bundles: * Allow overriding compute for non-development mode targets ([#1899](#1899)). * Avoid panic if Config.Workspace.CurrentUser.User is not set ([#1993](#1993)). * Show an error when using a cluster override with 'mode: production' ([#1994](#1994)). Internal: API Changes: * Added `databricks account federation-policy` command group. * Added `databricks account service-principal-federation-policy` command group. * Added `databricks aibi-dashboard-embedding-access-policy delete` command. * Added `databricks aibi-dashboard-embedding-approved-domains delete` command. OpenAPI commit a6a317df8327c9b1e5cb59a03a42ffa2aabeef6d (2024-12-16) Dependency updates: * Upgrade TF provider to 1.62.0 ([#2030](#2030)). * Upgrade Go SDK to 0.54.0 ([#2029](#2029)). * Bump TF codegen dependencies to latest ([#1961](#1961)). * Bump golang.org/x/term from 0.26.0 to 0.27.0 ([#1983](#1983)). * Bump golang.org/x/sync from 0.9.0 to 0.10.0 ([#1984](#1984)). * Bump github.com/databricks/databricks-sdk-go from 0.52.0 to 0.53.0 ([#1985](#1985)). * Bump golang.org/x/crypto from 0.24.0 to 0.31.0 ([#2006](#2006)). * Bump golang.org/x/crypto from 0.30.0 to 0.31.0 in /bundle/internal/tf/codegen ([#2005](#2005)).
Bundles: * Allow overriding compute for non-development mode targets ([#1899](#1899)). * Show an error when using a cluster override with 'mode: production' ([#1994](#1994)). API Changes: * Added `databricks account federation-policy` command group. * Added `databricks account service-principal-federation-policy` command group. * Added `databricks aibi-dashboard-embedding-access-policy delete` command. * Added `databricks aibi-dashboard-embedding-approved-domains delete` command. OpenAPI commit a6a317df8327c9b1e5cb59a03a42ffa2aabeef6d (2024-12-16) Dependency updates: * Upgrade TF provider to 1.62.0 ([#2030](#2030)). * Upgrade Go SDK to 0.54.0 ([#2029](#2029)). * Bump TF codegen dependencies to latest ([#1961](#1961)). * Bump golang.org/x/term from 0.26.0 to 0.27.0 ([#1983](#1983)). * Bump golang.org/x/sync from 0.9.0 to 0.10.0 ([#1984](#1984)). * Bump github.com/databricks/databricks-sdk-go from 0.52.0 to 0.53.0 ([#1985](#1985)). * Bump golang.org/x/crypto from 0.24.0 to 0.31.0 ([#2006](#2006)). * Bump golang.org/x/crypto from 0.30.0 to 0.31.0 in /bundle/internal/tf/codegen ([#2005](#2005)).
@NodeJSmith Thanks for reporting and I can see how it can be confusing. Before this pair of changes, the cluster override required the development mode. Now it can always be used, except when using the production mode. It's better to always use job clusters in production because they're always fresh and as such cannot be tainted (in terms of cluster settings, libraries, etc). |
Changes
We should show a warning when using a cluster override with 'mode: production'. Right now, we inadvertently show an error for this state. This is a followup based on #1899 (comment).