Right now the REST endpoint used to import configs calls the extractFolder() method in RepositoryConfigServiceImpl to iterate through a file and upload it to an appId location in an OC docbase. This method could instead take a base path parameter and be used to upload any zip file to any location and be moved to ZipUtil. This currently isn't possible since the upload location is hard coded to hpi-root/theZipName. The import configs REST endpoint currently ensures the appId folder for the import exists and then calls extractFolder so this change would also include altering some of the endpoint logic.
Right now the REST endpoint used to import configs calls the
extractFolder()method inRepositoryConfigServiceImplto iterate through a file and upload it to an appId location in an OC docbase. This method could instead take a base path parameter and be used to upload any zip file to any location and be moved toZipUtil. This currently isn't possible since the upload location is hard coded tohpi-root/theZipName. The import configs REST endpoint currently ensures the appId folder for the import exists and then callsextractFolderso this change would also include altering some of the endpoint logic.