Skip to content

[AIRFLOW-5672][WIP] Rename CloudDLPHook to CloudDlpHook#6406

Closed
michalslowikowski00 wants to merge 2 commits intoapache:masterfrom
PolideaInternal:AIRFLOW-5672-rename-CloudDLPHook-to-CloudDlpHook
Closed

[AIRFLOW-5672][WIP] Rename CloudDLPHook to CloudDlpHook#6406
michalslowikowski00 wants to merge 2 commits intoapache:masterfrom
PolideaInternal:AIRFLOW-5672-rename-CloudDLPHook-to-CloudDlpHook

Conversation

@michalslowikowski00
Copy link
Copy Markdown
Contributor

Part of AIP-21

Jira

  • My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
    • https://issues.apache.org/jira/browse/AIRFLOW-5672
    • In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
    • In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
    • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

  • Here are some details about my PR, including screenshots of any UI changes:

Tests

  • My PR adds the following unit tests OR does not need testing for this extremely good reason:

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

Copy link
Copy Markdown
Member

@mik-laj mik-laj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we use shortcuts, we should write them Capitalized e.g. GKE, GCS

https://docs.google.com/document/d/1_rTdJSLCt0eyrAylmmgYc3yZr-_h51fVlnvMmWqhCkY/edit?ts=5bb72dfd#

We need to update our planned changes

@mik-laj mik-laj added the provider:google Google (including GCP) related issues label Oct 25, 2019
@mik-laj
Copy link
Copy Markdown
Member

mik-laj commented Oct 25, 2019

@michalslowikowski00
Copy link
Copy Markdown
Contributor Author

@mik-laj Should we leave CloudDLPHooka and follow the this rules?https://docs.google.com/document/d/1_rTdJSLCt0eyrAylmmgYc3yZr-_h51fVlnvMmWqhCkY/edit?ts=5bb72dfd#

@mik-laj mik-laj changed the title [AIRFLOW-5672] rename CloudDLPHook to CloudDlpHook [AIRFLOW-5672][WIP] Rename CloudDLPHook to CloudDlpHook Oct 28, 2019
@mik-laj mik-laj added the AIP-21 label Oct 29, 2019
@michalslowikowski00 michalslowikowski00 deleted the AIRFLOW-5672-rename-CloudDLPHook-to-CloudDlpHook branch December 9, 2019 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

provider:google Google (including GCP) related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants