Answers.Body: <p>I assume that you are running Terra on Google Cloud Platform (GCP)?</p>
  <p>It is weird, because Terra is supposed to run on GCP - that is what its intended purpose - and finding gcloud is automatic, you don't need to configure it.</p>
  <p>Three suggestions:</p>
  <ol>
  <li>If the cloud is GCP it is appears to could be a bug with the Broad Institutes platform and should be reported directly on their website. They will know immediately, so if they don't respond immediately its a user problem. This is because they will prioritise system bugs, but user errors they may not respond to.</li>
  <li>At a guess the error suggests you just need to point to gcloud within .bashrc or .profile, but you don't need to do this on GCP because gcloud is its modus operandi*.</li>
  <li>Run WDL directly outside Terra.</li>
  </ol>
  <p><em>The simplest approach is to install miniconda and use it to install gcloud-sdk package and then install Terra from within conda. Assuming Terra is present on &quot;-c bioconda&quot;. At this point Terra is forced to see gcloud</em>.</p>
  <p>However, it feels like Terra is being installed on a cloud outside GCP and hence the error.</p>
  <ul>
  <li>To those who don't know GCP gcloud = google cloud.</li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-09T14:01:06.143Z
Answers.Text: Thank you!  Also, the Terra help desk gave me a few lines to add to my docker to do a setup.  Meanwhile, I have found a different way to run my wdl and Rscript so pursuing that for a few days.  Thanks so much for the advice.
Answers.UserDisplayName: Liz Litkowski
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-09T14:10:11.260Z
Answers.Text: Good it helps. Importantly good to know the Broad Institute actively support Terra. Upvotes would be welcome.
Answers.UserDisplayName: M__
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-01-07T04:01:19.527Z
Answers.LastActivityDate: 2022-01-08T12:48:06.873Z
Answers.LastEditDate: 2022-01-08T12:48:06.873Z
Answers.UserDisplayName: M__
Body: <p>I have run into the following problem</p>
  <pre><code>Error: failed to find 'gcloud' binary; set option or environment variable 'GCLOUD_SDK_PATH'
  </code></pre>
  <p>when executing this line of R code:</p>
  <pre><code>avfiles_ls( recursive = FALSE,
              namespace = avworkspace_namespace('bdcat-cohort3-stanislawski'),
              name = avworkspace_name('SOLGeneticTopMed')
  )
  </code></pre>
  <p>This works when I run it in a notebook in a cloud environment but not when I am running an R script inside a wdl on Terra.</p>
  <p>Is there a way to more fully quality where the namespace is?</p>
  <p>Thanks.
  Liz</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2022-01-08T12:49:36.107Z
Comments.Text: Are you running Terra on GCP?
Comments.UserDisplayName: M__
Tags: <python>
Title: 'GCLOUD_SDK_PATH' Error
ThreadText: # 'GCLOUD_SDK_PATH' Error
  
  (Asked by: username_0 on 2022-01-05)
  
  I have run into the following problem
  
  ```
  Error: failed to find 'gcloud' binary; set option or environment variable 'GCLOUD_SDK_PATH'
  
  ```
  
  when executing this line of R code:
  
  ```
  avfiles_ls( recursive = FALSE,
              namespace = avworkspace_namespace('bdcat-cohort3-stanislawski'),
              name = avworkspace_name('SOLGeneticTopMed')
  )
  
  ```
  
  This works when I run it in a notebook in a cloud environment but not when I am running an R script inside a wdl on Terra.
  
  Is there a way to more fully quality where the namespace is?
  
  Thanks.
  Liz
  
  **Tags:** python
  
  > **Comments:**
  > **username_1**: Are you running Terra on GCP?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-01-07. Score: 2
  
  I assume that you are running Terra on Google Cloud Platform (GCP)?
  
  It is weird, because Terra is supposed to run on GCP - that is what its intended purpose - and finding gcloud is automatic, you don't need to configure it.
  
  Three suggestions:
  
  1. If the cloud is GCP it is appears to could be a bug with the Broad Institutes platform and should be reported directly on their website. They will know immediately, so if they don't respond immediately its a user problem. This is because they will prioritise system bugs, but user errors they may not respond to.
  2. At a guess the error suggests you just need to point to gcloud within .bashrc or .profile, but you don't need to do this on GCP because gcloud is its modus operandi\*.
  3. Run WDL directly outside Terra.
  
  *The simplest approach is to install miniconda and use it to install gcloud-sdk package and then install Terra from within conda. Assuming Terra is present on "-c bioconda". At this point Terra is forced to see gcloud*.
  
  However, it feels like Terra is being installed on a cloud outside GCP and hence the error.
  
  * To those who don't know GCP gcloud = google cloud.
  
  > **Comments:**
  > **username_0**: Thank you!  Also, the Terra help desk gave me a few lines to add to my docker to do a setup.  Meanwhile, I have found a different way to run my wdl and Rscript so pursuing that for a few days.  Thanks so much for the advice.  
  > **username_1**: Good it helps. Importantly good to know the Broad Institute actively support Terra. Upvotes would be welcome.  
  
  ---
  
  