uplsh580 commented on code in PR #61039:
URL: https://github.com/apache/airflow/pull/61039#discussion_r2875078208
##########
chart/values.yaml:
##########
@@ -2309,6 +2309,39 @@ dagProcessor:
# classpath: "airflow.dag_processing.bundles.local.LocalDagBundle"
# kwargs: {}
+ # Per-bundle deployment option
+ # When enabled, creates a separate deployment for each bundle in
`dagBundleConfigList`
+ deployPerBundle:
Review Comment:
Thank you for the feedback. I agree that maintaining two separate lists
could lead to configuration drift and unnecessary complexity.
To address this, how about nesting the deployment configuration directly
within the dagBundleConfigList? This way, each bundle's definition and its
deployment strategy are coupled together, ensuring better consistency.
Here is an example of the proposed structure:
```yaml
deployPerBundle: true # default is `false`
dagBundleConfigList:
- name: bundle1
classpath: ...
kwargs: ...
deploymentOverride: # Bundle-specific deployment settings
enabled: true
replicas: 3
resources: ...
- name: bundle2
classpath: ...
kwargs: {}
# If 'deployment' is omitted, it could fall back to default values
```
--
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]
