molcay commented on PR #37223: URL: https://github.com/apache/airflow/pull/37223#issuecomment-1961153709
Hi @akashsriv07, I will propose a different approach for the folder/module structure. Since GDC might have different APIs, or different inner working mechanisms, it can be good to separate the GDC related things (like `hooks`, `operators`, `sensors`) from the `cloud` one. In the future, if you want to add more things (like `hooks`, `operators`, `sensors`), it can be easily extended in a more structured way. Also, you will have access for the existing Google Cloud `operators`, `sensors`, etc. Hence, I am suggesting creating a new module inside a `google` provider (at the same level with the `cloud` module). Something like the following: ``` airflow/providers/google ├── ads ├── cloud ├── common ├── firebase ├── gdc # <-- this is the new one ├── leveldb ├── marketing_platform ├── suite ├── CHANGELOG.rst ├── go_module_utils.py ├── __init__.py └── provider.yaml ``` What do you think? -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
