evgenii-prusov opened a new pull request, #53726:
URL: https://github.com/apache/airflow/pull/53726
# Feature Proposal: Add YAML Support to Airflow Variables Import Command
## Problem Statement
Apache Airflow currently has an inconsistency in its CLI commands for
importing variables and connections:
- **`airflow connections import`**: Supports multiple file formats (JSON,
YAML, ENV) using a flexible secret parser
- **`airflow variables import`**: Only supports JSON format with hardcoded
`json.load()` and `json.dump()`
This inconsistency damages user experience and limits flexibility when
managing Airflow variables, especially for teams that prefer YAML for
configuration management.
This change brings the `airflow variables import` command to feature parity
with `airflow connections import` by adding support for YAML and ENV file
formats.
Key changes:
- Replace hardcoded `json.load()` with flexible `load_variables()` function
- Add format detection based on file extension (.json, .yaml, .yml, .env)
- Handle ENV files differently from JSON/YAML (single values vs. preserving
data types)
- Add comprehensive tests for all supported formats
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
