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 2020/06/19 09:11:33 UTC

[GitHub] [airflow] potiuk opened a new issue #9401: All "private" images and binaries used by Airflow should be manage by community

potiuk opened a new issue #9401:
URL: https://github.com/apache/airflow/issues/9401


   **Description**
   
   We have a few Docker images in our build process that use "private" *personal" docker images. It would be great to have all the images either officially released and maintained by a community or to migrate the images to be managed by our Community.
   
   The images to move:
   
   * divya12/helm-unittest
   * ashb/apache-rat:0.13-1
   * godatadriven/krb5-kdc-server
   * polinux/stress
   * osixia/openldap:1.2.0 (?)
   
   **Use case / motivation**
   
   We depend on availability of the images in our tests, and while it is not critical, it would be great to have our own, independent storage of those images and an easy way to add a new one.
   
   **Related Issues**
   
   #9371 


----------------------------------------------------------------
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

[GitHub] [airflow] potiuk commented on issue #9401: All "private" images and binaries used by Airflow should be manage by community

Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #9401:
URL: https://github.com/apache/airflow/issues/9401#issuecomment-739806910


   All done here. Closing,


----------------------------------------------------------------
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

[GitHub] [airflow] aneesh-joseph commented on issue #9401: All "private" images and binaries used by Airflow should be manage by community

Posted by GitBox <gi...@apache.org>.
aneesh-joseph commented on issue #9401:
URL: https://github.com/apache/airflow/issues/9401#issuecomment-646702968


   @potiuk  - I had to change switch the helm unit test one  to `aneeshkj/helm-unittest`


----------------------------------------------------------------
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

[GitHub] [airflow] potiuk closed issue #9401: All "private" images and binaries used by Airflow should be manage by community

Posted by GitBox <gi...@apache.org>.
potiuk closed issue #9401:
URL: https://github.com/apache/airflow/issues/9401


   


----------------------------------------------------------------
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

[GitHub] [airflow] mik-laj commented on issue #9401: All "private" images and binaries used by Airflow should be manage by community

Posted by GitBox <gi...@apache.org>.
mik-laj commented on issue #9401:
URL: https://github.com/apache/airflow/issues/9401#issuecomment-649059524


   I looked at these dependencies and I am not worried about most because they are based on Open-Source licenses or are used only during development. However, these 3 of them are runtime dependencies is based on the proprietary/unknown(?) license and have no specific alternative.
   
   > astronomerinc/ap-statsd-exporter:0.11.0
   > astronomerinc/ap-pgbouncer:1.8.1
   > astronomerinc/ap-pgbouncer-exporter:0.5.0-1
   
   Thank Jarek for paying attention to this issue. I know I couldn't use the Helm Chart in its current form in any of my work. I am afraid that many members of our community would face similar problems if they tried to use it in a production environment.
   
   I described my fears on the mailing list in more detail:
   https://lists.apache.org/thread.html/r9d13709f5a968c849fb57733436d330561e5278a595ddad7c9b96a2b%40%3Cdev.airflow.apache.org%3E
   


----------------------------------------------------------------
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