[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-08-04(UTC)"],[[["\u003cp\u003eCloud Composer 1 utilizes the Apache Airflow command-line interface (CLI) for managing tasks like triggering DAGs, accessing DAG run details, and handling connections and users.\u003c/p\u003e\n"],["\u003cp\u003eCloud Composer 1 supports two different syntaxes for CLI commands: Airflow 1.10 CLI syntax for environments with Airflow 1.10, and Airflow 2 CLI syntax for environments running Airflow 2.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003egcloud composer environments run\u003c/code\u003e command is used to execute Airflow CLI commands in Cloud Composer environments, requiring specification of the environment name, location, subcommand, and subcommand arguments.\u003c/p\u003e\n"],["\u003cp\u003eWhen using the \u003ccode\u003egcloud composer environments run\u003c/code\u003e command, arguments for Airflow CLI subcommands should be separated by \u003ccode\u003e--\u003c/code\u003e, and different syntax rules apply for Airflow 1 and Airflow 2 environments.\u003c/p\u003e\n"],["\u003cp\u003eFor private IP environments, Airflow CLI commands must be run from a machine with access to the GKE cluster's control plane, and if public endpoint access is disabled, \u003ccode\u003ekubectl\u003c/code\u003e can be used directly with cluster credentials.\u003c/p\u003e\n"]]],[],null,[]]