Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update guidance on service accounts #1120

merged 2 commits into from Dec 4, 2020


Copy link

@busunkim96 busunkim96 commented Dec 4, 2020

Link out to docs on service accounts since it is less likely to go stale.

Fixes #946

Link out to docs on service accounts since it is less likely to go stale.
@busunkim96 busunkim96 requested a review from googleapis/yoshi-python as a code owner Dec 4, 2020
@google-cla google-cla bot added the cla: yes label Dec 4, 2020
@busunkim96 busunkim96 requested a review from parthea Dec 4, 2020
parthea approved these changes Dec 4, 2020
Copy link

@parthea parthea left a comment


@busunkim96 busunkim96 merged commit b2ea122 into master Dec 4, 2020
3 checks passed
3 checks passed
Kokoro Build successful
cla/google All necessary CLAs are signed
@busunkim96 busunkim96 deleted the busunkim96-patch-13 branch Dec 4, 2020
Copy link

@javelinsubhash javelinsubhash commented Jan 20, 2021

Not sure if this should be a new issue, but docs show two different ways of creating keys with gcloud format

  "type": "service_account",
  "project_id": "project-id",
  "private_key_id": "key-id",
  "private_key": "-----BEGIN PRIVATE KEY-----\nprivate-key\n-----END PRIVATE KEY-----\n",
  "client_email": "service-account-email",
  "client_id": "client-id",
  "auth_uri": "",
  "token_uri": "",
  "auth_provider_x509_cert_url": "",
  "client_x509_cert_url": ""


  "name": "projects/project-id/serviceAccounts/service-account-email/keys/key-id",
  "privateKeyData": "private-key",
  "validAfterTime": "date",
  "validBeforeTime": "date",
  "keyAlgorithm": "KEY_ALG_RSA_2048"

For this client library are both formats valid? I'm asking because I'm having auth issues with the gcloud format for this repository

gcf-merge-on-green bot pushed a commit that referenced this pull request Mar 3, 2021
🤖 I have created a release \*beep\* \*boop\* 
## [2.0.0]( (2021-03-03)


* **deps:** require 3.6+ (#961)

### Features

* Add support for using static discovery documents ([#1109]( ([32d1c59](
* Update to copy discovery files from discovery-artifact-manager ([#1104]( ([af918e8](

### Bug Fixes

* Catch ECONNRESET and other errors more reliably ([#1147]( ([ae9cd99](
* **deps:** add upper-bound google-auth dependency ([#1180]( ([c687f42](
* handle error on service not enabled ([#1117]( ([c691283](
* Improve support for error_details ([#1126]( ([e6a1da3](
* MediaFileUpload error if file does not exist ([#1127]( ([2c6d029](
* replace deprecated socket.error with OSError ([#1161]( ([b7b9986](
* Use logging level info when file_cache is not available ([#1125]( ([0b32e69](

### Miscellaneous Chores

* **deps:** require 3.6+ ([#961]( ([8325d24](

### Documentation

* add networkconnectivity v1alpha1 ([#1176]( ([91b61d3](
* Delete redundant ([#1142]( ([70bc6c9](
* fix MediaIoBaseUpload broken link ([#1112]( ([334b6e6](
* fix regression with incorrect args order in docs ([#1141]( ([4249a7b](
* fix typo in thread safety example code ([#1100]( ([5ae088d](
* Reduce noisy changes in docs regen ([#1135]( ([b1b0c83](
* update docs/dyn ([#1096]( ([c2228be](
* update guidance on service accounts ([#1120]( ([b2ea122](

This PR was generated with [Release Please]( See [documentation](
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

3 participants