-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudinary Test Cloud returns invalid Public IDs #65
Comments
With some additional testing, I found that the Cloudinary test cloud is also returning invalid Public IDs with the following characters: |
Hey Chris, I don't see any upload failures and I couldn't find any examples of assets with unpermitted characters in your DAM. Are you receiving any error messages from Cloudinary? |
That is because the issue is with the Test Cloud, not my DAM. The test cloud is used when running python unit tests within the ci runners. I have added steps to reproduce in the issue description. |
@chrissnyder2337 , there is this support post: Nothing to do with the CLI. |
Yes this is not an issue with the CLI, it is an issue with the test cloud that the CLI uses. That is what I am trying to point out. The "test cloud" is returning illegal public ids, and does not match what a real Cloudinary cloud account would return. This impacts the CLI development because the "test cloud", used by tests in this project, is returning illegal public ids, and does not match what a real Cloudinary cloud account would return. This impacts the ability to write accurate tests. There may be another project/place that this issue could be moved to. |
@chrissnyder2337 Would you mind sharing the cloud name for both your production and test accounts? Thanks |
@chrissnyder2337 For security reasons, I had to delete your comment as you added your credentials and especially the |
@chrissnyder2337 @const-cloudinary - it seems the test clouds are using custom flags that are not used by classic accounts. Especially, the test clouds were configured to allow specific characters in a public_id. I believe that's why there was a difference |
Bug report for Cloudinary CLI
This is not necessarily an issue with the Cloudinary CLI itself, but with the test cloud it runs against.
Describe the bug in a sentence or two.
I found that the Test cloud returns invalid/inconsistent public ids for assets, especially when compared to running the same commands against a real Cloudinary account/enviroment. This impacts the ability to write accurate tests. I experienced this while trying to write tests for #63 .
Issue Type (Can be multiple)
Steps to reproduce
test_cli_upload_dir
command using the test Cloudinary environment (provided by running./tools/get_test_cloud.sh
). Note the command's output (by dumping/inspectingoutput.result
).:test_cli_upload_dir
command using a real Cloudinary environment (from https://cloudinary.com/console). Note the command's output (by dumping/inspectingoutput.result
).:)
,(
,+
,Error screenshots or Stack Trace (if applicable)
…
Operating System
Environment and Frameworks (fill in the version numbers)
Repository
If possible, please provide a link to a reproducible repository that showcases the problem
The text was updated successfully, but these errors were encountered: