454b36e66d39d265499090c7bfadebb86bfcc433
We hit issues where cloudfront had cached the repomd.xml file and it had become out of date and was causing issues because the repo metadata files it pointed to were deleted (because there was a new set of files that had been created).
WIP for now.
"to" the target?
That seems like an expensive way to do cp :) There's --remove-destination which would be useful here.
cp
--remove-destination
--exclude
Minor: inconsistent quoting of that last arg compared to the earlier invocations.
Is there a way to make sure we always hit this case in production? E.g. error out if the bucket name matches the prod bucket and these conditions fail.
rebased onto 8846b96ebfc9eb80caae900ba9d5c0229ebaf25d
rebased onto 22ca9194b3c0e37791ea4524e8b59151237c8a3d
pushed up a new version trying to address comments
LGTM!
rebased onto 454b36e66d39d265499090c7bfadebb86bfcc433
Pull-Request has been merged by dustymabe
We hit issues where cloudfront had cached the repomd.xml file and
it had become out of date and was causing issues because the repo
metadata files it pointed to were deleted (because there was a new
set of files that had been created).