Nóta
Aðgangur að þessari síðu krefst heimildar. Þú getur prófað aðskrá þig inn eða breyta skráasöfnum.
Aðgangur að þessari síðu krefst heimildar. Þú getur prófað að breyta skráasöfnum.
Note
This information applies to Databricks CLI versions 0.205 and above. The Databricks CLI is in Public Preview.
Databricks CLI use is subject to the Databricks License and Databricks Privacy Notice, including any Usage Data provisions.
The account settings command group within the Databricks CLI contains commands to manage settings at the account level. These settings control default configurations for new workspaces, including compliance security profile, legacy features, and enhanced security monitoring. See Manage your Azure Databricks account.
databricks account settings csp-enablement-account get
Get the compliance security profile setting for new workspaces.
databricks account settings csp-enablement-account get [flags]
Options
--etag string
Etag used for versioning.
Examples
The following example gets the compliance security profile setting:
databricks account settings csp-enablement-account get
The following example gets the compliance security profile setting with etag:
databricks account settings csp-enablement-account get --etag "etag-value"
databricks account settings csp-enablement-account update
Update the value of the compliance security profile setting for new workspaces. The compliance security profile settings at the account level control whether to enable it for new workspaces. By default, this account-level setting is disabled for new workspaces. After workspace creation, account admins can enable the compliance security profile individually for each workspace.
databricks account settings csp-enablement-account update [flags]
Options
--json JSON
The inline JSON string or the @path to the JSON file with the request body
Examples
The following example updates the compliance security profile setting using JSON:
databricks account settings csp-enablement-account update --json '{"setting_value": {"compliance_security_profile_workspace": {"enabled": true}}}'
The following example updates the compliance security profile setting using a JSON file:
databricks account settings csp-enablement-account update --json @csp-setting.json
databricks account settings disable-legacy-features delete
Delete the disable legacy features setting.
databricks account settings disable-legacy-features delete [flags]
Options
--etag string
Etag used for versioning.
Examples
The following example deletes the disable legacy features setting:
databricks account settings disable-legacy-features delete
The following example deletes the disable legacy features setting with etag:
databricks account settings disable-legacy-features delete --etag "etag-value"
databricks account settings disable-legacy-features get
Get the value of the disable legacy features setting. For newly created workspaces, this setting disables the use of DBFS root and mounts, Hive Metastore provisioning, no-isolation clusters, and Databricks Runtime versions prior to 13.3LTS.
databricks account settings disable-legacy-features get [flags]
Options
--etag string
Etag used for versioning.
Examples
The following example gets the disable legacy features setting:
databricks account settings disable-legacy-features get
The following example gets the disable legacy features setting with etag:
databricks account settings disable-legacy-features get --etag "etag-value"
databricks account settings disable-legacy-features update
Update the value of the disable legacy features setting.
databricks account settings disable-legacy-features update [flags]
Options
--json JSON
The inline JSON string or the @path to the JSON file with the request body
Examples
The following example updates the disable legacy features setting using JSON:
databricks account settings disable-legacy-features update --json '{"setting_value": {"disable_legacy_features": {"enabled": true}}}'
The following example updates the disable legacy features setting using a JSON file:
databricks account settings disable-legacy-features update --json @disable-legacy-features.json
databricks account settings esm-enablement-account get
Get the enhanced security monitoring setting for new workspaces. The enhanced security monitoring setting at the account level controls whether to enable the feature on new workspaces. By default, this account-level setting is disabled for new workspaces. After workspace creation, account admins can enable enhanced security monitoring individually for each workspace.
databricks account settings esm-enablement-account get [flags]
Options
--etag string
Etag used for versioning.
Examples
The following example gets the enhanced security monitoring setting:
databricks account settings esm-enablement-account get
The following example gets the enhanced security monitoring setting with etag:
databricks account settings esm-enablement-account get --etag "etag-value"
databricks account settings esm-enablement-account update
Update the value of the enhanced security monitoring setting for new workspaces.
databricks account settings esm-enablement-account update [flags]
Options
--json JSON
The inline JSON string or the @path to the JSON file with the request body
Examples
The following example updates the enhanced security monitoring setting using JSON:
databricks account settings esm-enablement-account update --json '{"setting_value": {"esm_enablement_account": {"enabled": true}}}'
The following example updates the enhanced security monitoring setting using a JSON file:
databricks account settings esm-enablement-account update --json @esm-setting.json
Global flags
--debug
Whether to enable debug logging.
-h or --help
Display help for the Databricks CLI or the related command group or the related command.
--log-file string
A string representing the file to write output logs to. If this flag is not specified then the default is to write output logs to stderr.
--log-format format
The log format type, text or json. The default value is text.
--log-level string
A string representing the log format level. If not specified then the log format level is disabled.
-o, --output type
The command output type, text or json. The default value is text.
-p, --profile string
The name of the profile in the ~/.databrickscfg file to use to run the command. If this flag is not specified then if it exists, the profile named DEFAULT is used.
--progress-format format
The format to display progress logs: default, append, inplace, or json
-t, --target string
If applicable, the bundle target to use