Skip to content

Parameterization for Calling Fabric Items Too Limited (e.g. now way to pass custom command line arguments when running SJDs) #22

@nikita-makarov

Description

@nikita-makarov

data = {"executionData": {"parameters": job_params}} if job_params else {}

In current implementation, when calling a Fabric item, it's always nested in "parameters", which severely limits the amount of customization on the API call to run a Fabric item. For example, if we wanted to run an SJD with custom command line args, we would not be able to do that as that requires different syntax inside executionData, as shown here. Same for notebooks,we don't have the ability to set other configs like environments or default lakehouses.

Maybe allow for users to pass their own custom executionData json object instead of just parameters?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions