You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2019/12/12 17:41:48 UTC
[GitHub] [airflow] mik-laj commented on issue #6798: [AIRFLOW-6122] Rename
kms service
mik-laj commented on issue #6798: [AIRFLOW-6122] Rename kms service
URL: https://github.com/apache/airflow/pull/6798#issuecomment-565110244
We want to introduce naming conventions of operator names for GCP. This was voted in AIP-21 / case #6. All rules is available in [GCP Service Airflow Integration Guide](https://docs.google.com/document/d/1_rTdJSLCt0eyrAylmmgYc3yZr-_h51fVlnvMmWqhCkY/edit?ts=5bb72dfd#heading=h.d8ueq9nksq0c) in `Naming conventions` chapter.
We have a plan that introduces conventions for all GCP integrations. Our main goal is to provide a uniform experience when using any GCP operator. It is worth adding that this name is unique because there are several KMS services, but only the service from Google is called "**Cloud**KMS". This change is backward compatible and people who use the old name could still use it without problems. We have tests that verify that the operator is working from an old and new path. If the old path is used, a deprecation warning is also checked.
If you have further questions, I will be happy to answer.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services