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 2021/06/26 20:31:46 UTC

[GitHub] [airflow] ecerulm commented on issue #14597: Provide jinja template syntax to access connections

ecerulm commented on issue #14597:
URL: https://github.com/apache/airflow/issues/14597#issuecomment-869058271


   >  I for example create V1Secret for them in the namespace then I can reference them from secrets of KubernetesPodOperator:
   
   Yes, I can manually do that , but
   *  I do really want to handle the secrets in a single place. I would prefer not to have to update both the Airflow connection and corresponding kubernetes secret every time I rotate the credentials for this particular database. 
   * The users that can create and modify airflow connections  are not necessarily  the same with access (and skill) to create a corresponding kubernetes secret (I don't want them to call me everytime that they need to update the password)


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

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org