Package Details: google-cloud-sdk 305.0.0-1

Git Clone URL: https://aur.archlinux.org/google-cloud-sdk.git (read-only, click to copy)
Package Base: google-cloud-sdk
Description: A set of command-line tools for the Google Cloud Platform. Includes gcloud (with beta and alpha commands), gsutil, and bq.
Upstream URL: https://cloud.google.com/sdk/
Keywords: cloud gcloud gcp google sdk
Licenses: Apache
Submitter: barnybug
Maintainer: sudoforge (sudobot)
Last Packager: sudoforge
Votes: 145
Popularity: 4.27
First Submitted: 2014-06-03 08:10
Last Updated: 2020-08-11 22:18

Pinned Comments

sudoforge commented on 2018-09-10 15:11

PLEASE NOTE

This PKGBUILD is maintained on GitHub. Please use the following repository to submit patches, ask questions, and raise issues:

https://github.com/sudoforge/pkgbuilds

sudoforge commented on 2018-08-21 22:09

IMPORTANT NOTE!

Commit e01da1e449882ad8e4fe590b01cd09624b58143a removes the appengine components from this package. These components, along with all of the others, will be made available as independent packages in the future.

If you need any of the additional components for your day-to-day workflow, set "disable_updater": false in /opt/google-cloud-sdk/lib/googlecloudsdk/core/config.json and manage components using gcloud components <command>.

Be sure to install any dependencies for the additional components that you may need.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

sudoforge commented on 2019-11-06 00:41

@bswartz thanks for catching that; python3 should have been an optdep.

bswartz commented on 2019-11-06 00:27

This package no longer builds. The error message is:

==> Starting package()...
Copying core SDK components
Running bootstrapping script
/home/arch/google-cloud-sdk/PKGBUILD: line 38: python2: command not found
==> ERROR: A failure occurred in package().
    Aborting...

sudoforge commented on 2019-09-18 12:05

Hey folks,

The PKGBUILD has been updated from 261.0.0 to 263.0.0. I apologize for skipping 262.0.0's release; I was out of town.

I'm in the process of working out how I want to automate these updates, since Google is a trusted source (at least in terms of package integrity). I currently use a mashed up shell script to do this for me, but it still needs to be manually invoked -- after it's completion, I create the commit and handle pushing to Github (the source of truth for the PKGBUILD) and then subtree the google-cloud-sdk directory out to the AUR.

I'll almost certainly have to do two things:

1) Stop signing the Git commits with my PGP key

2) Use a passwordless key to push to the AUR

1 is more or less unimportant, as I doubt anyone has workflows that rely on my key. 2 is more concerning, as it would mean that the machine I'm using to update the AUR package is able to hit the git server with a passwordless RSA key. To limit the attack vector to packages which have a "trusted upstream source" (like this one), I'll be adding a bot user as a co-maintainer. I may eventually remove my personal account from this package if this proves successful.

Let me know if:

  • Your workflow will break if my commits are no longer signed with my PGP key, or
  • Your workflow will break if the package owner changes

sudoforge commented on 2019-05-04 12:37

@Brinox:

I have confirmed this regression and updated the pinned comment.

Brinox commented on 2019-01-27 10:54

The described mechanism of installing additional components by modifying the _additional_components variable does not work. The SDK installer just won't install the given components, because "disable_updater" is set to true. This seems to affect the bootstrap install, too.

sudoforge commented on 2019-01-15 09:03

@esbdb and @oskar - There has been a pinned comment with instructions for managing components since August 2018.

oskar commented on 2019-01-15 08:42

I wasn't able to update kubectl component either due to the following error:

ERROR: (gcloud.components.remove) You cannot perform this action because this Cloud SDK installation is managed by an external package manager. Please consider using a separate installation of the Cloud SDK created through the default mechanism described at: <https://cloud.google.com/sdk/>

I circumvented this by installing kubectl package from AUR (which is up-to-date) and removing /opt/google-cloud-sdk/bin/kubectl.

esbdb commented on 2018-10-30 06:56

How do I actually update installed components? I'm still running kubectl 1.7.2. Even when update gcloud, gcloud components update never gets run.

sudoforge commented on 2018-10-20 15:36

@mathieu.clabaut:

You can follow the very straightforward instructions in the pinned comment to add additional components. No additional components will be added to this PKGBUILD at any time now or in the future.

mathieu.clabaut commented on 2018-10-20 12:23

First, I must thank you for your useful package.

I'd like to ask if it Wouldn't be possible to keep the app engine component in this package until the other package is available ?