Closed peterdesmet closed 1 year ago
Glad the logging adjustments are working.
Up to now I did not consider this scenario of files no longer existing in the S3 bucket. Not sure what the inventory is doing with removed files and if these willl be no longer enlisted in a next inventory. @TheJenne18 ?
The inventory system in Amazon S3 provides a snapshot of the objects within a bucket at a specific point in time. When a file is deleted, it will not appear in the inventories generated after the deletion.
However, if the file was deleted recently (in this case on August 21 or 22), and the inventory with the CLI routine 'vph5_to_vpts --modified-days-ago 2' was performed during that time frame, it might still include the now-deleted file.
Note: I got the another notification for the same file tonight. Will see if I get it tomorrow.
Ok, mystery solved: those notifications were send from the UAT environment, where those files are not deleted.
I got an AWS notification email today:
It now includes the name of the file 👍. The mentioned file is however no longer in the repository. It was deleted August 21 or 22 (2 or 1 days ago). I'll see tomorrow if the issue resolves itself, i.e. the inventory is updated and the file is no longer listed there and no notification is generated.
@stijnvanhoey @TheJenne18 can deleted files linger in the inventory? Should this resolve itself automatically? Not sure we considered this when designing the architecture.
Note this error did not stop the creation of the daily and monthly files 👍