[AIRFLOW-5099] Implement Google Cloud AutoML operators

[turbaszek]

Adds Google Cloud AutoML operators.

Make sure you have checked all steps below.

Jira

• My PR addresses the following Airflow Jira issues and references them in the PR title.
  • https://issues.apache.org/jira/browse/AIRFLOW-5099

Description

• Adds Google Cloud AutoML operators.

Tests

• My PR adds the following unit tests:
• tests/contrib/hooks/test_gcp_automl_hook.py
• tests/contrib/operators/test_gcp_automl_operator.py

Commits

• My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does
  • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

Code Quality

• Passes flake8

[turbaszek]

@potiuk @mik-laj @lwander

[potiuk]

Knowing that most of it automatically generated, it looks good :).

[potiuk]

Knowing that most of it automatically generated, it looks good :).

[lwander]

Nice! Looks clean :) Just a few small comments

[lwander]

Do we need as get_deploy_dag:? It's not referenced in the snippet below unless I've missed something

[turbaszek]

It's a common to use as name for DAGs. Usually examples contains only one DAG (as dag).

[lwander]

Does this mean the model_id must be supplied in this payload? Could it help to update the comment to show the name & format of the required field?

[turbaszek]

No, model_id is not a part of payload. The payload is described in AutoML docs and it depends on service type. I assume that user will be familiar / will check the official REST API / Python SDK. I think it could be worth to put there a comment with link to payload definition. @lwander WDYT?

[potiuk]

Still some tests fail :(

[rasmi]

No review comments here, I'm just excited for this to be merged -- thank you all for your work!

[mik-laj]

Suggested change

	# For now only this location is supported
	# For now only this location is supported

This comment is not needed. It is better not to add information that may change in the documentation. This is a similar problem as with the prices of services in the documentation. Have you noticed that prices are only in one place and no official documentation contains calculations of service prices? When a price is needed, a reference to the table or calculator is added.

[mik-laj]

Suggested change

	) -> Operation:
	) -> Operation:

I think, hook should wait for the result of the operation. Let's talk about it on Monday.

[mik-laj]

Let's merge. We will not be able to resolve inconsistencies with MessageToDict now. This requires work at the level of all GCP operators. I think that in the near future we will face this problem.

[Ark-kun]

Knowing that most of it automatically generated, it looks good :).

What generator was used here?

[turbaszek]

@Ark-kun here is our internal repo with generators for GCP stuff:
https://github.com/PolideaInternal/airflow-munchkin

It still requires some final touches and minimal improvements but it gives a really nice base for developing operators. All suggestions are appreciated ;)