Skip to main content

Rename Uploaded Cloudinary Files in bulk

Comments

8 comments

  • Marissa Masangcay

    Hi,

    Currently the way to do a bulk rename would be to write a script that traverses through each resource that you would like to rename and you can call our API rename method on each resource. You can refer to our documentation to read more about how to rename resources here:

    https://cloudinary.com/documentation/image_upload_api_reference#rename

    Thanks,

    Marissa

    0
  • Willemijn Schneyder

    Hi,

    Wondering if there are news on this besides the suggested way?

    Thank you.

    0
  • Raz Ziv

    Hi Willemijn,

    I'm afraid that currently, the only solution for achieving this remains writing a script, according to the guidelines suggested by Marissa.

    We will be more than happy to assist you in generating such a script. If interested, please open a support ticket at https://support.cloudinary.com/hc/en-us/requests/new and we will continue our communication over there.

    Thanks,

    Raz

    0
  • Daniel

    Hello,

    I am using the rename function only because it allows me to change the resource access type
    (authenticated / upload) of the resources but I see that rename can't manage bulk of resources.

    Is there a way to do that in a bulk? (without renaming the resources)

    Thank you,
     Daniel

     

    0
  • Francis Tagbo

    Hi Daniel,

    While the rename method currently only supports a single public id at a time, it does have a high concurrency rate (of about 40-50 concurrent calls) so you can use multi-threads to send many requests at once.

    Regards,

    Francis

    0
  • Daniel

    Thank you Francis!
    That can be a great solution.

     

    0
  • Daniel

    Hi,

    When I am using multi-threads to send 8 rename requests at once it works fine but I get this warning for 7 of the 8 requests that I am sending:

    WARNING:urllib3.connectionpool:Connection pool is full, discarding connection: api.cloudinary.com

    I assume that the urllib3.connectionpool is managing it correctly (Discarding only the connection part) and that it knows to work with the existing connection when this warning happens because everting seems to work fine but I am not sure.

    Am I correct?
    If not... how would you recommend for me to solve this?

    Thank you for your help,
      Daniel

    0
  • Francis Tagbo

    Hi Daniel,

    Could you please create a support ticket thru https://support.cloudinary.com/hc/en-us/requests/new and share with us your code so we could check on it?

    Regards,
    Francis

    0

Post is closed for comments.