ug-2766 : should check permission when putting a new entity to collection
Collapsed imports
Added processExportData to ManagementServiceImpl. Currently a placeholder, but it will eventually fire off the job and get a proper response back.
Management service was added the placeholder as well.
Added exportPath to ManagementService interface.

Created JobInfo class to hold the job status and it’s potential states in the queue system.
Export info class was created to extrapolate the json call for export.
Added getter methods to ExportInfo.
Changed imports back from .* notation to explicitly stated.
Added a comment on the validity of the return response in ManagementResource.
Added Export class to persistence entities. Can be accessed in that way, and it is exposed as a service by ExportService ( doesn’t export anything just yet).
Adding repair toolkit when application metadata mismatch
Abstracted ExportService.java
Added full implementation of Export in ExportServiceDos.
Added test case to check dummy response against /export endpoint.
Commented out previous export endpoint code, and added in an ExportInfo class to take in and parse the data.
Export.java is currently not being used and is left in just in case.
Revised test to post valid test data ( the export should still fail with the test though)
Made certain that the rest endpoint is being called. ( Test still fails due to having null for organizations though)
Added in all of the code needed for export collections into ExportServiceDos.
( still haven’t handled injects in this commit, maybe that is why things are failing).
Added export service wiring so services can freely use the implementation based by spring.
Renamed ExportServiceDos to ExportServiceImpl to make the code clearer.
Modified test , left commented code in to keep track of all the different types of ways I could post the entities.
Found way so that OauthResponse could be returned and the implementation wouldn’t complain about Objects.
Removed commented out code, then merged in the existing export code to work.
It Works!
Problems: I have a hardcoded path that dumps it to a specifically named file ( in this case derp.txt)
Don’t have a working error message or the endpoint.
I uncommented out the schedule, but that method has nothing in it and doesn’t affect usage currently.
Added field s3_accessId that will replace s3_token ( not currently but next commit).
Changed some of the file name credentials so that I could work using hardcoded paths.
Shamelessly took copytToS3 method form WarehouseExport . Added in export info for AWS credentials. Functions as intended.
Added a todo for admin authentication.
Removed useless payload test code.
Removed instances of s3_token and replaced with name admin token instead.
Created a todo for global filenames, where global filenames are not needed.
Took out the dumping of the collections file. Now only collection/app data is dumped into s3.
Added fix for one of the tests that would never pass due to status mismatch.
Added a batch job that will eventually need to be converted to a only one job instance. First pass doesn’t need multiple jobs
Will also need to have the job launch the schedule and have it be a component then have THAT method call the doExport method.
Added some logging to let you debug if there is no organization or no application. dummy data is set for the UUID as there is no class to hold that information yet.
Added a comment to export info that dictates the next steps to get jobs working.
Added a new test that creates 100 entities, but the test doesn’t contain file checking yet.
Re included authorization, but will most likely be taken out. Also re added the sch command but it will to call the doExport not just call both methods.
Created ExportJob component so that it can be called from ExportService.
Stored exportInformation and passed onto the job.
Removed ExportBatchJob as I only need to be able to run one job currently.
Removed exportService doExport methods as it will now be called with the sch.
Revised response message and added ability for user to get back Json response with UUID of job.
Added test that checks to make sure you are getting a UUID back.
Removed extra spaces in exportInfo class.
Uncomplicated imports in ManagementService.
Removed unused method processExportData.
ExportJob has the heartbeat in to let server know the job is still continuing.
Added setter method so that we could mock the ExportService.
Added getJobUUID to simplify the sending of the UUID to the user.
Added setS3Export method to be able to mock the transfer of data to s3.
Removed the copyToS3 method to a Impl method that would actually copy a file to s3.
Added spring wiring to find s3ExportImpl class.
Added ExportService to ServiceITSetup to allow calling of the service from setup.
Added a doJob test that correctly mocks the services from job to export.
Correctly writes export file to s3 using file stream buffers.
Re included the code that would save connections.
Re included the code that would save dictionaries.
Fix bug that the output stream would attach junk data whenever writing data.
Added integration test ( with stripped credentials)