-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix KubernetesPodOperatorAsync
to consider kubernetes connection id and details in trigger
#815
Conversation
Codecov ReportBase: 98.51% // Head: 98.51% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #815 +/- ##
=======================================
Coverage 98.51% 98.51%
=======================================
Files 87 87
Lines 4777 4777
=======================================
Hits 4706 4706
Misses 71 71
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@pankajastro @pankajastro @phanikumv Can you review this PR |
did we test this on astro cloud? |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
title, description and the commit msg do not describe why this change is done
kubernetes_conn_id
in trigger and hookKubernetesPodOperatorAsync
to consider Kubernetes connection id and details in trigger
KubernetesPodOperatorAsync
to consider Kubernetes connection id and details in triggerKubernetesPodOperatorAsync
to consider kubernetes connection id and details in trigger
kube_config_path
orkube_config
(JSON) from Kubernetes connection was not consider inKubernetesPodOperatorAsync
. Because the connection id is set to None in the trigger, So now it is fixed to consider the Kubernetes connection id and details in trigger.closes: #745