curl -X POST localhost:8081/v1/projects/<project-id>:export -H "Content-Type: application/json" -d "{\"output_url_prefix\":\"C:\Users\<user>\Desktop\Data\"}"
{"error":{"code":500,"message":"Failed to export entities.","status":"INTERNAL"}}
curl -X POST localhost:8081/v1/projects/<project-id>:import -H "Content-Type: application/json" -d "{\"input_url\":\"C:/Users/<user>/Desktop/Data/file.overall_export_metadata\"}"
{"error":{"code":400,"message":"Failed to parse overall export metadata file","status":"INVALID_ARGUMENT"}}
curl -X POST localhost:23868/v1/projects/<project-id>:import -H 'Content-Type: application/json' -d '{"input_url":"<path-to-overall_export_metadata>.overall_export_metadata"}'
{"error":{"code":400,"message":"Failed to parse overall export metadata file","status":"INVALID_ARGUMENT"}}
Please consider the environment before printing this mail
The information contained in this e-mail is private & confidential and may also be legally privileged. If you are not the intended recipient of this mail, please notify us, preferably by e-mail; and do not read, copy or disclose the contents of this message to anyone. Whilst we have taken reasonable precautions to ensure that any attachment to this e-mail has been swept for viruses, e-mail communications cannot be guaranteed to be secure or error free, as information can be corrupted, intercepted, lost or contain viruses. We do not accept liability for such matter or their consequences
Hello Ohm,
Please note that Google Groups are reserved for general Google Cloud Platform and product discussions and not for reporting issues, which is why I suggest moving the troubleshooting to Issue Tracker, where issues can be turned private in case we need to gather any project specific details.