Script for migrating blobs from one blob store to an other. This script expects a config/private.tmp.yml file which will be renamed to config/private.yml when blobs are downloaded. The contents for the new config/final.yml are hardcoded into the script. You should fill in your own target blobstore credentials

migrate_blobs.sh

#!/bin/sh

# reset stuff
sudo rm -r .blobs
rm -r blobs
rm -r blobs_import
git checkout -- config/blobs.yml
git checkout -- config/final.yml
rm config/private.yml

# get blobs
bosh sync blobs

mv blobs blobs_import

# Format for private.tmp.yml:
# ---
# blobstore:
#   s3:
#     access_key_id:     ACCESS
#     secret_access_key: PRIVATE

# switch config to new blob store
cp config/private.tmp.yml config/private.yml
cat > config/final.yml <<EOF
---
final_name: cf-contrib
blobstore:
  provider: s3
  options:
    bucket_name: cf-services-contrib-release
    # AWS s3 user: blobstore-reader
    access_key_id: AKIAJPWUHOHV42IMTNQQ
    secret_access_key: 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
    encryption_key: cloudfoundry-community
EOF

# clear blobs.yml
cat > config/blobs.yml <<EOF
---
{}
EOF

# re-add blobs
for blob in `cd blobs_import && find */*`
do
  dir=`echo $blob | cut -d'/' -f1`
  bosh add blob blobs_import/$blob $dir
done

# upload blobs
bosh upload blobs

But it does mean that private.yml shouldn't need deleting & copying. You should be able to create a config/private.yml up front and just use that.

Nice script - would be nice if you didnt have to type 'yes' for each blob to upload though.. there doesnt seem to be a switch to auto-yes each blob upload :/

Looks like TieWei commented that check out in his BOSH fork though :D
https://github.com/TieWei/bosh/commit/d5c3aa93f918da38a52094993d2ff37d7184d91f

bosh -n upload blob stops the yes prompt