Add google-cloud-sdk
to bare-metal prognostic run environments
#2374
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It occurred to me that not everyone will already have
google-cloud-sdk
(and namelygsutil
) installed in their searchPATH
on Stellar or Gaea, so this addsgoogle-cloud-sdk
to the conda environment created in theinstall_base_software.sh
script.gsutil
is used within the post-processing step of the prognostic run, and without it one will encounter errors. No authentication is needed if just moving files around locally (as is the case when running on HPC).Note we similarly install
google-cloud-sdk
in the prognostic run docker image, so this is not anything particularly new:fv3net/.environment-scripts/gnu_docker/install_base_software.sh
Line 50 in 61f3a55
Coverage reports (updated automatically):