Skip to content

databricks lakeview create does not support parameter parent_path anymore #5983

Description

@marcin-sg

Describe the issue

databricks lakeview create used to support parameter --parent-path (location where specific dashboard will be saved). New version (Databricks CLI v0.286.1) does not support it directly, but rest API still exposes this parameter.

As a work around you can provide the --json parameter with parent_path argument.

databricks lakeview create --json "$(jq -n \
            --arg name "${dashboard_name}" \
            --arg wh "${warehouse_id}" \
            --arg parent "${path}" \
            --arg dash "$(cat ${dashboard_dir}/${dashboard_name}.lvdash.json | jq -c)" \
            '{display_name: $name, warehouse_id: $wh, parent_path: $parent, serialized_dashboard: $dash}')"

Steps to reproduce the behavior

databricks lakeview create "${dashboard_name}" \
        --warehouse-id ${warehouse_id} \
        --serialized-dashboard "$(cat ${dashboard_dir}/${dashboard_name}.lvdash.json | jq -c)" \
        --parent-path ${path}

Expected Behavior

Either support that parameter or explain why it should not be used anymore.

Actual Behavior

Running command with --parent-path throws Error: unknown flag: --parent-path. The work around works as expected (the way the parameter used to work)

OS and CLI version

Databricks CLI v0.286.1

Is this a regression?

It is regresion.... But I cannot recovered with which version it used to work.

Debug Logs

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLICLI related issues

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions