On Fri, Mar 06, 2020 at 07:53:05AM +0100, Adrian Reber wrote: ...snip... > > You are deleting files here in a third step which looks like the correct > order to sync it. > > > echo "Ending EPEL sync at $(date)" >> /var/log/s3-mirror/timestamps > > > > for file in $(echo /srv/pub/epel/6/*/repodata/repomd.xml | sed 's#/srv##g'); do > > @@ -94,10 +193,16 @@ for file in $(echo /srv/pub/epel/7/*/repodata/repomd.xml | sed 's#/srv##g'); do > > aws cloudfront create-invalidation --distribution-id E2KJMDC0QAJDMU --paths "$file" > > done > > > > +for file in $(echo /srv/pub/epel/8/*/repodata/repomd.xml | sed 's#/srv##g'); do > > + aws cloudfront create-invalidation --distribution-id E2KJMDC0QAJDMU --paths "$file" > > +done > > + > > But the invalidation happens here, right? So between delete and > invalidate there is a short time where the cache might point to files > which have been deleted a bit earlier. For me it seems that > '$CMD2 --delete ...' should be after invalidation. Same for the Fedora > sync a bit later. > > In the s3-sync-path.sh script the delete is done after the invalidation. > > Any reason to handle it differently in these two scripts? Nope. :( Let me do another commit here. ;) kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
