Remove all sensitive export functionality from airflowctl

[henry3260]

closes: #59841

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[henry3260]

I will fix the CI test failure in test_variable_command.py.

[jscheffl]

No need to backport in my view.

[potiuk]

Also - it needs a newsfragment describing change in behaviour.

[potiuk]

You need to remove "export" command from the generation script :).

[henry3260]

You need to remove "export" command from the generation script :).

Applied!

[amoghrajesh]

Looks good.

[jscheffl]

Thanks for the rework and discussions. Looks good to me now!

[bugraoz93]

Sorry for joining late, and I may have missed something. The issue was stating connections and variables export, but why pool export also deleted that I didn't understand. I think we should add this back since pools don't store anything sensitive

[henry3260]

Sorry for joining late, and I may have missed something. The issue was stating connections and variables export, but why pool export also deleted that I didn't understand. I think we should add this back since pools don't store anything sensitive

Yes, your are right. Sorry about that 😵‍💫 .

#59850 (comment)

Should I open an another pr to add it back?

[jason810496]

Should I open an another pr to add it back?

Yes, let’s open another PR to add it back. Thanks!