conda-forge / google-cloud-sdk-feedstock

A conda-smithy repository for google-cloud-sdk.

About google-cloud-sdk-feedstock

Feedstock license: BSD-3-Clause

Home: https://cloud.google.com/sdk/

Package license: Apache v2.0

Summary: Command-line interface for Google Cloud Platform products and services

Current build status

Azure

Variant Status linux_64_python3.10.____cpython linux_64_python3.11.____cpython linux_64_python3.12.____cpython linux_64_python3.8.____cpython linux_64_python3.9.____73_pypy linux_64_python3.9.____cpython osx_64_python3.10.____cpython osx_64_python3.11.____cpython osx_64_python3.12.____cpython osx_64_python3.8.____cpython osx_64_python3.9.____73_pypy osx_64_python3.9.____cpython osx_arm64_python3.10.____cpython osx_arm64_python3.11.____cpython osx_arm64_python3.12.____cpython osx_arm64_python3.8.____cpython osx_arm64_python3.9.____cpython

Current release info

Name	Downloads	Version	Platforms

Installing google-cloud-sdk

Installing google-cloud-sdk from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, google-cloud-sdk can be installed with conda:

conda install google-cloud-sdk

or with mamba:

mamba install google-cloud-sdk

It is possible to list all of the versions of google-cloud-sdk available on your platform with conda:

conda search google-cloud-sdk --channel conda-forge

or with mamba:

mamba search google-cloud-sdk --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search google-cloud-sdk --channel conda-forge

# List packages depending on `google-cloud-sdk`:
mamba repoquery whoneeds google-cloud-sdk --channel conda-forge

# List dependencies of `google-cloud-sdk`:
mamba repoquery depends google-cloud-sdk --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating google-cloud-sdk-feedstock

If you would like to improve the google-cloud-sdk recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/google-cloud-sdk-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @chapmanb
• @nehaljwani
• @scopatz

google-cloud-sdk-feedstock's Issues

@conda-forge-admin add bot automerge

Issue:

Environment (conda list):

$ conda list

Details about conda and system ( conda info ):

$ conda info

Add crcmod as dep for gsutil

Comment:

Without crcmod you get this message:

WARNING: gsutil rsync uses hashes when modification time is not available at
both the source and destination. Your crcmod installation isn't using the
module's C extension, so checksumming will run very slowly. If this is your
first rsync since updating gsutil, this rsync can take significantly longer than
usual. For help installing the extension, please see "gsutil help crcmod".

which indeed makes gsutil rsync very slow.

Things are much faster after mamba install crcmod so having it as default might be a good thing.

docker-credential-gcloud symlink missing

Apologies if this is an upstream issue, I figure posting here may help someone else if so

Issue:

After installing google-cloud-sdk, docker-credential-gcloud is not symlinked into the environment's bin/ which means it is not in system PATH.

$ gcloud auth configure-docker
WARNING: docker-credential-gcloud not in system PATH.
gcloud's Docker credential helper can be configured but it will not work until this is corrected.

The symlink has to be created manually eg.

ln -s ~/.conda/envs/my-env/share/google-cloud-sdk-277.0.0-0/bin/docker-credential-gcloud ~/.conda/envs/my-env/bin/

Could this feedstock be modified to create the symlink on install? This may be related to #77 .

Environment (conda list):

$ conda list
google-cloud-sdk          277.0.0                  py36_0    conda-forge
python                    3.6.7             h357f687_1006    conda-forge

Details about conda and system ( conda info ):

$ conda info

    conda version : 4.6.11
    conda-build version : 3.17.8
         python version : 3.7.3.final.0
       base environment : /home/khornlund/anaconda3  (read only)
           channel URLs : https://conda.anaconda.org/pytorch/linux-64
                          https://conda.anaconda.org/pytorch/noarch
                          https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/free/linux-64
                          https://repo.anaconda.com/pkgs/free/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/khornlund/anaconda3/pkgs
                          /home/khornlund/.conda/pkgs
       envs directories : /home/khornlund/.conda/envs
                          /home/khornlund/anaconda3/envs
               platform : linux-64
             user-agent : conda/4.6.11 requests/2.21.0 CPython/3.7.3 Linux/5.3.0-28-generic ubuntu/18.04.3 glibc/2.27
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

crcmod

Hi!

Is there any recommended way of install crcmod with this package?
I could only get it working by manually installing crcmod to pip afterwards, which doesn't seem optimal. Is it possible to include in the installation with some option, or parhaps as a default?

Include beta things

It seems that this doesn't include some of the beta stuff?

gcloud beta
ERROR: (gcloud) The components management action could not be performed because the installation root of the Cloud SDK could not be located. If you previously used the Cloud SDK installer, you could re-install the SDK and retry again.

Would it be possible to include those?