airflowctl: action_on_existence flag returns empty success & errors in `variables import`

[jx2lee]

Apache Airflow version

3.0.1

If "Other Airflow 2 version" selected, which one?

No response

What happened?

related: #50908
details: #50908 (comment)
cc. @bugraoz93 (comment)

What you think should happen instead?

With --action_on_existence fail, request should return 200 OK with right results.errors / results.success. But, empty

How to reproduce

When importing variables with --action_on_existence flag set to fail, overwrite, or skip,
the API responds 200 OK, but both results.success and results.errors are empty.
This makes it impossible to determine whether the existing variables were handled as expected.

Operating System

osx

Versions of Apache Airflow Providers

No response

Deployment

Other

Deployment details

No response

Anything else?

Reproduction Steps

1. Pre-condition: Two variables already exist in Airflow

[
  {"key": "foo", "value": "1"},
  {"key": "bar", "value": "2"}
]

2. Prepare import file (vars.json) containing the same keys:

[
  {"key": "foo", "value": "99"},
  {"key": "bar", "value": "88"}
]

3. Run CLI:

uv run airflowctl variables import vars.json --action_on_existence fail

You'll found empty success/errors.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[bugraoz93]

I think testing with Postman and seeing if it is working for all bulk operations should be enough. Thanks for creating it! I assigned to you

[jx2lee]

@bugraoz93 I found potential problem!

Airflow REST API documentation indicates that bulk variables endpoint returns a BulkResponse. However, bulk method in VariableOperation within airflowctl currently returns BulkActionResponse. This discrepancy could lead to inconsistencies in handling API responses.

REST API response bulk variables.

BulkResponse response scheme

This diff might also exist in PoolOperation's bulk method.
Should we consider updating these methods to return BulkResponse to align with the API spec? If you can provide guidance or direction, I'd be happy to create a PR to address this.

[jx2lee]

If we'll update methods to return BulkResponse, how about implementing it as follows?

screencast.2025-06-07.21-53-43.mp4