You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/06/24 22:48:00 UTC

[jira] [Commented] (AIRFLOW-4846) Allow specification of an existing secret containing git credentials for init containers

    [ https://issues.apache.org/jira/browse/AIRFLOW-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871858#comment-16871858 ] 

ASF GitHub Bot commented on AIRFLOW-4846:
-----------------------------------------

george-miller commented on pull request #5475: [AIRFLOW-4846] Allow specification of an existing secret containing git credentials for init containers
URL: https://github.com/apache/airflow/pull/5475
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [x] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-4846
     
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI changes:
   
   I would like to specify username/password git credentials as a secret so that I don't have plaintext username/passwords stored in my airflow configuration file.  We can assume the given secret has GIT_USERNAME and GIT_PASSWORD fields.
   
   ### Tests
   
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### 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
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [x] 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](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
   
   ### Code Quality
   
   - [x] Passes `flake8`
   
 
----------------------------------------------------------------
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


> Allow specification of an existing secret containing git credentials for init containers
> ----------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-4846
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4846
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: executors
>    Affects Versions: 1.10.4
>            Reporter: George Miller
>            Assignee: George Miller
>            Priority: Major
>
> I would like to specify username/password git credentials as a secret so that I don't have plaintext username/passwords stored in my airflow configuration file.  We can assume the given secret has GIT_USERNAME and GIT_PASSWORD fields.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)