Naresh-Challa commented on issue #19268:
URL: https://github.com/apache/superset/issues/19268#issuecomment-1162668469

   **Hi Team,**
   We are facing an issue in Importing the Dashboard 
   Export a dashboard with VERSIONED_EXPORT=true. export is working fine 
   When I try to import a dashboard on the same instance or another instance 
and it fails with a **command validation error.**
   
   **How to reproduce the bug**
   
   **Create a dashboard, save and export it (VERSIONED_EXPORT = true)**
   Try to import and fails with a validation error
   import the dashboard using the /import API. 
   The issue is that a simple dashboard with just one or two charts seems to 
work. A more involved dashboard such as the one I am building fails
   
   **Expected results**
   Import Dashboard should  be successful
   
   **Actual results**
   Fails import
   **Error:**
   Superset 1.5.0
   **API Version:**
   POST //api/v1/dashboard/import/ HTTP/1.1" 302 221 "-" "curl/7.65.0"
   
   curl -k -X 'POST' 'https://superset-URL/api/v1/dashboard/import/' -H 
'accept: application/json' -H "Authorization: Bearer $token" -H 'Content-Type: 
multipart/form-data' -F '[email protected];type=application/x-zip-compressed' 
-F 'overwrite=true' -F 'passwords={ "databases/MySQL_test.yaml":"Pwd", 
"databases/mysql_test2.yaml" : "PWD"}'
   
   
   **Screenshots**
   just Command error
   
   **Environment**
   UAT
   
   **API superset version 1.501**
   **any feature flags active:**
   VERSIONED_EXPORT=True from superset_config file
   
   please help on it, we are in trouble chasing it 
   
   Thanks
   Naresh Challa
   


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