Adding legacy resolver param in config.yml to avoid pip related issues

splunk · Dec 9, 2020 · 4957503 · 4957503
1 parent 0dfa7aa
commit 4957503
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -62,7 +62,7 @@ jobs:
       - run:
           name: Install Tools
           command: |
-            pip install /tmp/workspace/dist/*
+            pip install /tmp/workspace/dist/* --use-deprecated=legacy-resolver
   publish:
     docker:
       - image: circleci/python:3.7-node

diff --git a/splunk_add_on_ucc_framework/__init__.py b/splunk_add_on_ucc_framework/__init__.py
@@ -236,6 +236,7 @@ def _install_libs(requirements, ucc_target, installer="python3"):
                 + ucc_target
                 + "\""
             )
+            os.system(installer +" -m pip install pip --upgrade")
             os.system(install_cmd)
             remove_files(ucc_target)
     logging.info(f"  Checking for requirements in {path}")