From the cloud documentation you supplied it seems there is a way to do it via curl (albeit needs auth token) which can be done with one of Perl's user-agents (like LWP::UserAgent or Hijk etc.) after you translate the request parameters see Corion's answer Re: Overhead of Inline::Python?. That's probably the best way but it has the disadvantage of getting an auth token beforehand.

Here is my method. It is based on your Perl script selecting the files to upload and when ready it creates a file containing their details to a dir monitored by the following bash script. For each file appearing in that dir, the bash script will initiate a transfer using cloud provider's cmdline tool gsutil cp. The transfers can be done in parallel. If no files to be transfered the bash script just sits there and waits.

Edit: sure this is a bash script but I think it is worth a mention in PM because it demonstrates the use of GNU bash's sem, a Perl script to parallelise on N threads or less a list of tasks written by Ole Tange of Gnu::parallel fame. I am so happy I got reunited with my old friend Gnu::parallel I hope my deviation to bash land will be excused...

bw, bliako

#!/bin/bash # Unix GNUbash script to monitor a dir for '*.txt' files # containing a tab-separated pair of local-filename remote-object # which will copy to the cloud # if successful the file is moved to the done dir else to failed dir # (subdirs of monitor dir) # the process can be parallelised to up to NUMTHREADS threads using # GNU's creme-de-la-creme sem (which uses Perl) # The monitor dir is given as the only input param and should already +exists # The idea is that a separate Perl script will select the files to tra +nsfer # and create a signal file inside the monitor dir containing the detai +ls # of the transfer. # by bliako # for https://perlmonks.org/?node_id=11101534 # 20/06/2019 ##### NUMTHREADS=3 SLEEPTIME=2s ### nothing to change below ### MONITOR_DIR=$1 if [ "${MONITOR_DIR}" == "" ] || [ ! -d "${MONITOR_DIR}" ]; then echo "$0 : a 'monitor-dir' name must be given as 1st param pointin +g to an existing, readable dir" exit 1 fi DONE_DIR="${MONITOR_DIR}/done" mkdir -p "${DONE_DIR}" &> /dev/null FAILED_DIR="${MONITOR_DIR}/failed" mkdir -p "${FAILED_DIR}" &> /dev/null if [ ! -d "${DONE_DIR}" ] || [ ! -d "${FAILED_DIR}" ]; then echo "$0 : failed to create dir '${DONE_DIR}' and/or '${FAILED_DIR +}'" exit 1 fi function execu { local cmd="$1" local asignalfile="$2" local done_dir="$3" local failed_dir="$4" echo "execu() : called with cmd='${cmd}', asignalfile='${asignalfi +le}', done_dir='${done_dir}', failed_dir='${failed_dir}'" eval ${cmd} if [ $? -eq 0 ]; then echo "$0 : success executing ${cmd}" 1>&2 mv "${asignalfile}" "${done_dir}" else echo "$0 : command has failed ${cmd}" 1>&2 mv "${asignalfile}" "${failed_dir}" fi }; export -f execu while true; do nowdone=0 while IFS= read -r -d '' afwf; do # we found a file in the dir we are monitoring # it must containing the fullpath to the file to transfer # then tab and then the remote echo "checking '${afwf}'" declare -a fde=($(head -1 "${afwf}" | cut -d$'\t' -f1,2)) CMD="gsutil cp '${fde[0]}' 'gs://${fde[1]}'" echo "$0: executing ${CMD} ..." if [ "${NUMTHREADS}" -gt 1 ]; then echo "$0 : parallelising over ${NUMTHREADS} ..." sem -j${NUMTHREADS} execu "'${CMD}'" "'${afwf}'" "'${DONE_ +DIR}'" "'${FAILED_DIR}'" else echo "$0 : executing ..." execu "${CMD}" "${afwf}" "${DONE_DIR}" "${FAILED_DIR}" fi done < <(find "${MONITOR_DIR}" -maxdepth 1 -type f -name '*.txt' - +print0) totaldone=$((${totaldone}+${nowdone})) echo "$0 : sleeping some before next monitor, done ${totaldone} so + far" sleep ${SLEEPTIME} # sleep some done

In reply to Re: Overhead of Inline::Python? by bliako
in thread Overhead of Inline::Python? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.