CLI - error after setting CLOUDINARY_URL environment variable.
Hi,
I've been learning how to use the CLI, and things have been going well, until today. I ran a CLD command, and got an error that looked like I needed to reset my CLOUDINARY_URL environment variable. I ran the export command, using the URL from my control panel in place of the sample URL. After that any time I ran a CLD command, I got the error below.
export CLOUDINARY_URL=cloudinary://123456789012345:abcdefghijklmnopqrstuvwxyzA@cloud_name
$> cld config
Traceback (most recent call last):
File "/usr/local/bin/cld", line 5, in <module>
from cloudinary_cli.cli import main
File "/usr/local/lib/python3.9/site-packages/cloudinary_cli/__init__.py", line 3, in <module>
import cloudinary
File "/usr/local/lib/python3.9/site-packages/cloudinary/__init__.py", line 217, in <module>
_config = Config()
File "/usr/local/lib/python3.9/site-packages/cloudinary/__init__.py", line 180, in __init__
super(Config, self).__init__()
File "/usr/local/lib/python3.9/site-packages/cloudinary/__init__.py", line 107, in __init__
self._load_config_from_env()
File "/usr/local/lib/python3.9/site-packages/cloudinary/__init__.py", line 214, in _load_config_from_env
self._load_from_url(os.environ.get("CLOUDINARY_URL"))
File "/usr/local/lib/python3.9/site-packages/cloudinary/__init__.py", line 164, in _load_from_url
return self._setup_from_parsed_url(parsed_url)
File "/usr/local/lib/python3.9/site-packages/cloudinary/__init__.py", line 152, in _setup_from_parsed_url
config_from_parsed_url = self._config_from_parsed_url(parsed_url)
File "/usr/local/lib/python3.9/site-packages/cloudinary/__init__.py", line 187, in _config_from_parsed_url
raise ValueError("Invalid CLOUDINARY_URL scheme. Expecting to start with 'cloudinary://'")
ValueError: Invalid CLOUDINARY_URL scheme. Expecting to start with 'cloudinary://'
I'm not sure what to try next. It seems like I have an invalid configuration stored, but I'm not clear where the CLI stores its configuration. For reference, I'm on MacOS with ZSH.
Any help would be greatly appreciated. Thanks!
0
-
never mind - I found my error. I had a malformed export command that caused the problem. Once I corrected that, everything works fine now.
0
Post is closed for comments.
Comments
1 comment