#15245 - passing custom image family name to the DataProcClusterCreateoperator

[pateash]

Closes: #15245

This is my first PR. I tried to follow the CONTRIBUTING guide step by step. It passed all the pre-commit tests.

My PR adds a new argument to DataprocCreateClusterOperator which allows user to pass custom image family while creating GCP DataProc cluster. any advice or suggestions are welcome.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (flake8, pylint and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it’s a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[marcosmarxm]

Just one question, overall LGTM;

[xinbinhuang]

@asamasoma Thanks for the contribution! Can you also add an extra test case to verify the generated cluster config is as expected with custom_image_family and single_node?

[pateash]

@xinbinhuang Thanks for the review,
I have added a test case to verify the generated cluster config is as expected with custom_image_family and single_node.

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest master or amend the last commit of the PR, and push it with --force-with-lease.

[xinbinhuang]

LGTM! Just need to remove the print statement in the test case, then we can merge it:)

[boring-cyborg]

Awesome work, congrats on your first merged pull request!