enjoyear opened a new pull request #2771: [GOBBLIN-918] Implement a task that is able to execute Azure data fac… URL: https://github.com/apache/incubator-gobblin/pull/2771 Dear Gobblin maintainers, Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below! ### JIRA - [X] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-918] My Gobblin PR" - https://issues.apache.org/jira/browse/GOBBLIN-918 ### Description - [X] Here are some details about my PR, including screenshots (if applicable): ADFPipelineExecutionTask is an example implementation of AbstractADFPipelineExecutionTask which can execute an Azure Data Factory pipeline. It has the following two abstract methods implementation: * It gets pipeline parameters from the configuration - azure.data-factory.pipeline.params * It gets the authenticate through Azure Active Directory based on the service principal's id and secret The ADFPipelineExecutionTask first gets the token and caches it using CachedAADAuthenticator, then it calls the REST endpoint constructed via ADFPipelineExecutionUriBuilder with the payload constructed from a JSON string. The ADFPipelineExecutionTask entends the HttpExecutionTask, which a general task class that can handle REST calls ### Tests - [X] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: CachedAADAuthenticatorTest ADFPipelineExecutionTaskTest ADFPipelineExecutionUriBuilderTest ### Commits - [X] 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](http://chris.beams.io/posts/git-commit/)": 1. Subject is separated from body by a blank line 2. Subject is limited to 50 characters 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"
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
