[ https://issues.apache.org/jira/browse/BEAM-11444?focusedWorklogId=523615&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-523615 ]
ASF GitHub Bot logged work on BEAM-11444: ----------------------------------------- Author: ASF GitHub Bot Created on: 13/Dec/20 16:13 Start Date: 13/Dec/20 16:13 Worklog Time Spent: 10m Work Description: nikie commented on pull request #13541: URL: https://github.com/apache/beam/pull/13541#issuecomment-744030565 R:y1chi could you review, please? Not sure how this aligns with Beam conventions on handling display_data, if any. I considered configuring this with an option, but it is hard to imagine something relies on having correct password in display_data. ---------------------------------------------------------------- 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: us...@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 523615) Time Spent: 20m (was: 10m) > MongoDB Python connector shows password in display_data > ------------------------------------------------------- > > Key: BEAM-11444 > URL: https://issues.apache.org/jira/browse/BEAM-11444 > Project: Beam > Issue Type: Improvement > Components: io-py-mongodb > Environment: Google Cloud Dataflow > Reporter: Eugene Nikolaiev > Assignee: Yichi Zhang > Priority: P3 > Labels: mongodb, python > Fix For: 2.27.0 > > Time Spent: 20m > Remaining Estimate: 0h > > MongoDB connector's display_data shows password in *uri* and in > *mongo_client_spec* parameters. > h4. Example for Read step Info on Dataflow UI: > |*uri*|mongodb+srv://top:sec...@xyx456-pri.ab123.mongodb.net| > |*mongo_client_spec*|{"username": "top", "password": "secret"}| > h4. Example of how it could be shown if masked: > |*uri*|mongodb+srv://top:******@xyx456-pri.ab123.mongodb.net| > |*mongo_client_spec*|{"username": "top", "password": "******"}| -- This message was sent by Atlassian Jira (v8.3.4#803005)