Revert "Save cleaned data of Ingestion Server to AWS S3 (#4163)" #4443
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit 43d4d09.
Fixes
Fixes ingestion server deployments to production.
Description
This PR reverts #4163 since it was causing the image data refresh process to hang, and we won't need to file for tags anyway. I re-added the changes to use
perf_counter()
for times and a little fix in the slack unit test to avoid a warning, but I'm happy to omit those in this PR if it's preferred to make those changes separately.Testing Instructions
Try
just api/recreate,
which runs the data refresh in the ingestion server, and verify the API results continue working as expected.Checklist
Update index.md
).main
) or a parent feature branch.just catalog/generate-docs
for catalog PRs) or the media properties generator (just catalog/generate-docs media-props
for the catalog orjust api/generate-docs
for the API) where applicable.Developer Certificate of Origin
Developer Certificate of Origin