[ISSUE] Misleading and wrong type hinting for boolean parameters in jobs.list and jobs.list_runs

[dreilstad]

Description
The expected type for the parameters expand_tasks, completed_only, and active_only in the functions list() and list_runs() in the JobsAPI class is boolean. This is misleading and wrong in terms of what the Databricks API expects.

When supplying a True boolean value for any of these parameters, they are not applied correctly and does not return the expected values.

The reason for this is because the Databricks API expects a lowercase string: "true" or "false"
Either the conversion from boolean to lowercase string has to be implemented in the functions (list() and list_runs()) or change the type hinting of these parameters to be correct.

I do not know if this is an issue for other API endpoints.

Reproduction
The following code shows an example with the expand_tasks parameter.
The only difference between the two examples is value supplied to the parameter True and "true".

Code where list_runs does NOT return tasks:

host ="..."
token = "..."

w = WorkspaceClient(host=host, token=token)

for job in w.jobs.list():
    for run in w.jobs.list_runs(job_id=job.job_id, expand_tasks=True):
        assert "tasks" in run.as_dict(), "Did not find 'tasks' in returned job run dict"

Code where list_runs does return tasks:

host ="..."
token = "..."

w = WorkspaceClient(host=host, token=token)

for job in w.jobs.list():
    for run in w.jobs.list_runs(job_id=job.job_id, expand_tasks="true"):
        assert "tasks" in run.as_dict(), "Did not find 'tasks' in returned job run dict"

Expected behavior
I expect no missing values returned from functions when supplied with the correct parameters and that the parameters are actually applied.

Is it a regression?
I have not tested multiple versions. Only the latest.

Other Information

• OS: macOS

[dreilstad]

I realized after some investigation that my issue was the same as Issue #142 and that a fix had been implemented. I mistakenly assumed that I had the latest version of the SDK installed. Updating the version to the latest version (0.20.0) fixed the issue.