-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admin S3 Object Deletion - Build out - add Asset Image File field.... #1575
Comments
Update: Image Field
Tests run in local dev environment attached to development content:
|
@jkueloc I tested the small import using test Lincoln items and the storage image field successfully populated. Image replacement also worked successfully. But deletion failed for 1 or more items -- recieved a 500 error. |
Testing was also successful with an import of 9,000+ images. I did not see a noticeable delay in import time. I also tested asset replacement and deletion with this group. Replacement worked well and I was able to delete many assets at a time, successfully removing the Concordia record and the AWS files/directories. In fact, I was able to delete up to 7 items including 657 assets, much higher than we were previously able to do. So I also tried a much larger deletion of 133 items including 8,189 assets, the remainder of the imported campaign. As I expected, the task appeared to fail showing me a 500 error, but when I checked Concordia and AWS it did successfully delete all of the Concordia records and all of the AWS files and directories! |
@lalgee That's great! Thank you for testing! The 500 is that response time thing between the UI and the backend. Which was a topic of a possible solution in the chuck or celery task conversation on the research ticket #1573, as well as prefetching of an older delete ticket #1090. Building that out will be part of the batch|bulk delete | campaign/project retire ticket(s) that I haven't created / broken out into new tickets yet. I'd like to talk about that in the meeting tomorrow. I still need to build out the production worthy solution to populate the existing asset storage image fields - but that should inform (for me at least) the coming new tickets. |
This ticket will close once set permissions in AWS are applied to test, stage, and prod |
The permissions in AWS have been applied to test, stage, prod. |
Admin S3 Object Deletion - Build out - add Asset Image File field
Research/discussions ticket #1573
Solution Decision ticket #1574 (should be more than one ticket/issue to be granular about the path of individual choices and results that lead to the 'whole' solution...?)
The text was updated successfully, but these errors were encountered: