Devika7733 opened a new issue, #35355:
URL: https://github.com/apache/superset/issues/35355

   ### Bug description
   
   Hi Team, While performing dashboard import through the API endpoint using 
the following curl command:  "curl -k -s -b cookies.txt --url 
https://superset-test.com/api/v1/dashboard/import/   --header 'accept: 
application/json'   --header "authorization: Bearer $ACCESS_TOKEN"   --header 
'content-type: multipart/form-data'   --header 'referer: 
https://superset-test.com'   --header "x-csrftoken: $CSRF_TOKEN"   --form 
'formData=@/mnt/c/Users/Downloads/dashboard_export_20250509T031336.zip'   
--form overwrite=true   --form 'passwords={"databases/TestReports.yaml": 
"DBPA$$WORd"}' We noticed that the password is visible in the action log. Is 
there any way to hide this password? We are currently encrypting the password 
using SOPS and decrypting it when passing to the API."
   
   ### Screenshots/recordings
   
   <img width="1182" height="317" alt="Image" 
src="https://github.com/user-attachments/assets/2110e0b7-a175-4847-857f-997a1b97eff3";
 />
   
   ### Superset version
   
   5.0.0
   
   ### Python version
   
   3.11
   
   ### Node version
   
   18 or greater
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to