Open dhoogfr opened 1 year ago
@dhoogfr what is the OS being used ?
@NiviPari The OS is Linux (Linux Mint / Ubuntu)
Thanks for reporting the issue @dhoogfr. We do check if the user has the OCI CLI installed already. We will try to reproduce it and post the update here.
same issue with Windows 11 and VS Code 1.79. Thank you for any update.
@dhoogfr @dhoogfr Can you please try it with v1.0.2
Having the same issue on Mac OS Ventura and OCI Toolkit v1.0.3. Can please suggest a way to fix this?
on my mac os sonama, with OCI toolkit v1.0.4, I am facing below issue, when I allow it to install oci-cli as part of oci tool kit
Successfully installed PyYAML-6.0.1 arrow-1.3.0 certifi-2024.2.2 cffi-1.16.0 circuitbreaker-1.4.0 click-8.0.4 cryptography-42.0.5 jmespath-0.10.0 oci-2.125.3 oci_cli-3.39.1 prompt-toolkit-3.0.29 pyOpenSSL-24.1.0 pycparser-2.22 python-dateutil-2.9.0.post0 pytz-2024.1 six-1.16.0 terminaltables-3.1.10 types-python-dateutil-2.9.0.20240316 wcwidth-0.2.13
Traceback (most recent call last):
File "
I already have the OCI CLI installed on my workstation via pip. After I installed VS Code toolkit, I keeps asking me if I want to install the OCI CLI as part of the toolkit
Is there a way to disable this and still have the CLI integration functioning within VS Code? The installation was done in the default directories and are the same as the integration has as default. So would actually expect the integration to notice that these are already installed