Repository navigation
Clarify API Enablement instructions in the Authorization section of readme.md #710
Description
Activity
Great ideas! I think it would be best to show the services supported by this library and the matching APIs that must be enabled. Along with that, we can leave a reminder to only enable the ones you need.
This is also something that would benefit all the gcloud-* projects...
Maybe it's time to create gcloud-common, push some Markdown and screenshots to that library, and submodule them in...?
Sounds good to me; are we renaming meta or starting new?
- I think we still need a place to have private conversations, so this would be gcloud-common, a new repo. Thoughts?
Private roadmap stuff does come up now and then, so that makes sense.
- Sweet :-D
This was fixed over in gcloud-common, but will wait for #734 to merge before calling this resolved.
- added a commit that references this issue
on Nov 17, 2022 - added 2 commits that reference this issue
on Jan 24, 2023 11 remaining items
- added a commit that references this issue
on Jan 28, 2026 - added 2 commits that reference this issue
on Jan 29, 2026 - added a commit that references this issue
on Feb 17, 2026 - added a commit that references this issue
on Feb 25, 2026 - added a commit that references this issue
on Mar 18, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026
Metadata
Metadata
Assignees
Labels
No labels
In the Authorization -> Elsewhere section of the readme, readers are instructed to:
Navigate to APIs & auth > APIs section and turn on the following APIs (you may need to enable billing in order to use these services):
Given this description is API agnostic, it is slightly confusing why these three APIs are chose. I would recommend either:
or
As a small nit, lets use the language 'enable' and 'disable' for consistency with the experience when they get to the GUI.