Creating PR with the latest changes

[tommyg-cld]

Brief Summary of Changes

What does this PR address?

• GitHub issue (Add reference - #XX)
• Refactoring
• New feature
• Bug fix
• Adds more tests

Are tests included?

• Yes
• No

Reviewer, please note:

• Updates made to sync module to accommodate this new module as well changes to functions on api_utils which is used by other modules so need to pay extra attention here.

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I ran the full test suite before pushing the changes and all the tests pass.

[const-cloudinary]

That is a good catch!

I would change line 127 to:

        if "batch_id" in result:
            disp_str = f"asynchnously with batch_id: {result['batch_id']}"
        else:
            disp_str = f"as {result['public_id']}" if not disp_path \
                else f"as {disp_path} with public_id: {result['public_id']}"

then you can remove this line (if "async" not in options:)

and in
def asset_source(asset_details):

change to

  base_name = asset_details.get('public_id', '')

    if not base_name:
        return base_name

[tommyg-cld]

This is done.

I had to also update the last line to asset_details.get('format', '') as non-raw files still get the public_id as we specify them so this will prevent no format error as the response won't contain the format

Finally, I updated the display message to say it's processing when uploading asynchronously as well.

[const-cloudinary]

We can combine -Tand -t into one. it's easy to check if it's a saved config, or a cloudinary url or not both.

[const-cloudinary]

This can be removed

[const-cloudinary]

Doc string seems to be invalid

[const-cloudinary]

I would rename base_cloudname to source_cloud_name

[const-cloudinary]

Instead of loading target, and then resetting, you can just create a new instance of cloudinary.Config() class and use it.

[const-cloudinary]

auto paginate looks redundant

[carlevison]

A few questions and some typo fixes.

[carlevison]

Should the -f be -fi? It's related to the tag,context fields, right?

[carlevison]

Does this allow for a saved config?

[carlevison]

It would be good to show an example, or state the valid options.

[carlevison]

Is the -T really necessary? You're always going to have to specify a target environment. If you look at the sync command, for example, local_folder and cloudinary_folder are mandatory (no option letter).

[carlevison]

Doesn't -o conflict with the way you specify optional parameters?