Re: [I] Sensitive fields in connection extra_fields incorrectly marked as required [airflow]

2026-01-17 Thread via GitHub


jason810496 closed issue #60370: Sensitive fields in connection extra_fields 
incorrectly marked as required
URL: https://github.com/apache/airflow/issues/60370


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Sensitive fields in connection extra_fields incorrectly marked as required [airflow]

2026-01-11 Thread via GitHub


choo121600 commented on issue #60370:
URL: https://github.com/apache/airflow/issues/60370#issuecomment-3734496298

   @yuseok89 opened this issue and has kindly offered to work on it, so I’ll 
assign this issue to @yuseok89 
   When the PR is ready, it would be great to have help with the review 😉


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Sensitive fields in connection extra_fields incorrectly marked as required [airflow]

2026-01-11 Thread via GitHub


Lohith625 commented on issue #60370:
URL: https://github.com/apache/airflow/issues/60370#issuecomment-3734479100

   I’d like to take this issue and work on a PR. I’ll start by reproducing the 
behavior locally and then focus on the `redact_extra_fields` logic to ensure 
sensitive fields remain optional while still being masked correctly.
   I’ll post updates here once I have concrete findings or a proposed fix. 
Please let me know if there’s anything specific I should be aware of before 
starting.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Sensitive fields in connection extra_fields incorrectly marked as required [airflow]

2026-01-10 Thread via GitHub


Parthsuii commented on issue #60370:
URL: https://github.com/apache/airflow/issues/60370#issuecomment-3733854406

   I would like to contribute please assign it to me 


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Sensitive fields in connection extra_fields incorrectly marked as required [airflow]

2026-01-10 Thread via GitHub


yuseok89 commented on issue #60370:
URL: https://github.com/apache/airflow/issues/60370#issuecomment-3732854108

   I'd like to work on this issue. Could you please assign it to me?


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [I] Sensitive fields in connection extra_fields incorrectly marked as required [airflow]

2026-01-10 Thread via GitHub


boring-cyborg[bot] commented on issue #60370:
URL: https://github.com/apache/airflow/issues/60370#issuecomment-3732837274

   Thanks for opening your first issue here! Be sure to follow the issue 
template! If you are willing to raise PR to address this issue please do so, no 
need to wait for approval.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]