Describe the issue
According to Azure and AWS documentations --embed-credentials parameter should be
"Flag to indicate if the publisher's credentials should be embedded in the published dashboard."
However, the credentials are embedded even if the flag is not given.
Links:
https://learn.microsoft.com/en-gb/azure/databricks/dev-tools/cli/reference/lakeview-commands#databricks-lakeview-publish
https://docs.databricks.com/aws/en/dev-tools/cli/reference/lakeview-commands#databricks-lakeview-publish
Steps to reproduce the behavior
- Run
databricks lakeview publish REDACTED --warehouse-id REDACTED
- Get response
{
"display_name":"REDACTED",
"embed_credentials":true,
"revision_create_time":"2025-11-25T16:42:42.420Z",
"warehouse_id":"REDACTED"
}
Expected Behavior
Getting response
{
"display_name":"REDACTED",
"embed_credentials":false,
"revision_create_time":"2025-11-25T16:42:42.420Z",
"warehouse_id":"REDACTED"
}
Actual Behavior
The credentials are embedded, even if they should not be.
OS and CLI version
OS: Ubuntu 24.04.3
CLI version: 0.278.0
Is this a regression?
Not tested on previous versions
Debug Logs
None
Describe the issue
According to Azure and AWS documentations
--embed-credentialsparameter should be"Flag to indicate if the publisher's credentials should be embedded in the published dashboard."
However, the credentials are embedded even if the flag is not given.
Links:
https://learn.microsoft.com/en-gb/azure/databricks/dev-tools/cli/reference/lakeview-commands#databricks-lakeview-publish
https://docs.databricks.com/aws/en/dev-tools/cli/reference/lakeview-commands#databricks-lakeview-publish
Steps to reproduce the behavior
databricks lakeview publish REDACTED --warehouse-id REDACTEDExpected Behavior
Getting response
Actual Behavior
The credentials are embedded, even if they should not be.
OS and CLI version
OS: Ubuntu 24.04.3
CLI version: 0.278.0
Is this a regression?
Not tested on previous versions
Debug Logs
None