[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-10。"],[[["This page explains how to manage custom plugins within a Cloud Composer 1 environment, specifically detailing how to install, view, delete, and download them."],["Custom plugins, which allow for in-house development of operators, hooks, sensors, or interfaces, are installed by uploading plugin code to the `plugins` folder in your Cloud Composer environment's Cloud Storage bucket."],["The process for managing plugins can be accomplished through the Google Cloud console, which uses the UI, or through the command line interface using `gcloud` commands."],["After uploading plugins, they are not automatically reloaded, therefore, restarting the web server or scheduler processes may be needed for the plugins to be active, or they can wait until the `[scheduler]num_runs` parameter count is hit."],["Cloud Composer 1 only supports plugins in Airflow 1 environments with disabled DAG serialization, and plugins must conform to the specified Airflow plugins template guidelines."]]],[]]