baylisscg commented on issue #51877:
URL: https://github.com/apache/airflow/issues/51877#issuecomment-2986662287
@astro-anand I suppose. For schemes that support `username:password` format
userinfo remove remove the `password` component iff it exists and is not the
empty string. So something like:
```python
if scheme.lower() in PASSWORD_AUTH_SCHEMES and ":" in userinfo:
(username,password) = userinfo.split(":")
if password and len(password) > 0:
# Warning / Error / Notice
userinfo = ""
```
And add a nice warning notice on the Assets docs that it'll do this and
_only_ for passwords in the userinfo segment. Catching pre-signed URLs or other
forms of sharing links would be an absolute nightmare.
You would be second guessing the user. In academia this one ftp/http/sftp
server with a shared password is terrifyingly common and unavoidable. So a
"Hey, if you need to do this define a Connection and ObjectStoragePath"
If Asset is intended as a form of syntactic sugar for defining an event
channel for triggering DAGs then sanitising URIs makes sense as `uri` would be
loosely equivalent to `task_id` and `name` would be `task_display_name`
--
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]
