potiuk edited a comment on issue #20100: URL: https://github.com/apache/airflow/issues/20100#issuecomment-988652407
@mik-laj @wsmolak - In principle - I do agree with Kamil. However I have a thought. I would not dismiss the option of leaving the ClusterGenerator stratight away. The API Guide was written for Airflow 1.10, and now when we are releasing new Google Provider every month, regularly like a clock things changed a bit. As long as someone (your team @wsmolak :) ? ) woudl regularly (even automatically - we used to have such a simple tool) monitor for changes and update the ClusterGenerator, that would pretty much work - there would be at most weeks delays between the release of updated API and release of Google Provider, and likely you could even add more parameters when they are in Beta or in-development. Another option (not sure if feasible) - maybe there is (even a convoluted and complex) way of adding new "unknown" fields to cluster config generated by the generator? In this case we could simply describe the user how they can add new field while they are waiting for a new provider. WDYT? -- 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]
