Standardizing on use of cf-check on older workflow

raft-tech · Dec 4, 2024 · 23a4ef7 · 23a4ef7
1 parent 97bf95e
commit 23a4ef7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 11 deletions.
diff --git a/.circleci/deployment/commands.yml b/.circleci/deployment/commands.yml
@@ -285,16 +285,7 @@
         type: string
     steps:
       - checkout
-      - run:
-          name: Install dependencies
-          command: |
-            sudo apt update
-            sudo apt install jq
-            sudo apt install curl
-            # TODO: Add Signature check
-            curl -L "https://packages.cloudfoundry.org/stable?release=linux64-binary&version=v7&source=github" | tar -zx
-            sudo mv cf7 /usr/local/bin/cf
-            sudo chmod +x /usr/local/bin/cf
+      - cf-check
       - login-cloud-dot-gov:
           cf-password: <<parameters.cf-password>>
           cf-username: <<parameters.cf-username>>

diff --git a/scripts/cf-check.sh b/scripts/cf-check.sh
@@ -4,7 +4,7 @@ if command -v cf /dev/null 2>&1; then
     echo The command cf is available
 else
     apt-get update
-    apt-get install wget gnupg2 apt-transport-https
+    apt-get install wget gnupg2 apt-transport-https jq
 
     NEXUS_ARCHIVE="cf7-cli_7.7.13_linux_x86-64.tgz"
     NEXUS_URL="https://tdp-nexus.dev.raftlabs.tech/repository/tdp-bin/cloudfoundry-cli/$NEXUS_ARCHIVE"