Transition of list airflowctl config command

[yunchipang]

partially closes: #45664
parent issue: #45661

implements list config command by adding a list method to ConfigOperations.

[yunchipang]

@bugraoz93 referencing our discussion in #49601, could you please take a look if this implementation of airflowctl's list config command is on the right track?

[bugraoz93]

Thanks for the update! Direction is good. The only thing is there is no direct list command. We either need to utilise get and loop through the entire configuration or implement a simple list on the API side and keep these newly added pieces
See endpoints: https://github.com/apache/airflow/blob/main/airflow-core%2Fsrc%2Fairflow%2Fapi_fastapi%2Fcore_api%2Froutes%2Fpublic%2Fconfig.py

[yunchipang]

@bugraoz93 Thanks for the review!

Just wanted to clarify—I was using the endpoint below to get all configs while implementing the list command, and it seemed to be working as expected:

airflow/airflow-core/src/airflow/api_fastapi/core_api/routes/public/config.py

Lines 97 to 98 in 3936683

	@config_router.get(
	"",

This is the what the current list command gets me.

root@24ae150ff6a0:/opt/airflow# airflowctl config list
Please enter password for encrypted keyring:
Config(
    sections=[
        ConfigSection(
            name='atlas',
            options=[
                ConfigOption(key='sasl_enabled', value='False'),
                ConfigOption(key='host', value=''),
                ConfigOption(key='port', value='21000'),
                ConfigOption(key='username', value=''),
                ConfigOption(key='password', value='')
            ]
        ),
        ConfigSection(
            name='hive',
            options=[ConfigOption(key='default_hive_mapred_queue', value='')]
        ),
        ...

If the goal is to format it more like this:

[core]
dags_folder = /opt/airflow/dags
base_log_folder = /opt/airflow/logs
...

Would it be correct to assume this is just a matter of formatting? Or am I missing something deeper in the implementation? Happy to adjust if needed—just want to make sure I fully understand your feedback. Appreciate your insights!

[bugraoz93]

Exactly, this is the case. In this one, directly calling the API endpoint is returning what we want, so only implementing the operations is enough in this case.
Format is okay for now, we are just using rich.print() for all generated ones, and we will do a bulk update later for formatting with one line below.

airflow/airflow-ctl/src/airflowctl/ctl/cli_config.py

Line 439 in 3936683

rich.print(operation_method_object(method_params))

We only need to add and update a small part in the unit test for operations. Direction is good. Thanks for the update!

[bugraoz93]

Looks great! Thanks!