Repository navigation
Example for GCE in authorization documentation seems wrong #712
Copy link
Copy link
Closed
Description
Activity
Great catch, thank you! PR is very welcome if you're up for it :)
Okay, will do.
@stephenplusplus: Actually, this already looks correct here (modulo incorrect Markdown syntax, which I've sent a pull request for). How is that page generated?
- added a commit that references this issue
on Nov 17, 2022 - added a commit that references this issue
on Jul 23, 2025 - added a commit that references this issue
on Jan 14, 2026 - added 2 commits that reference this issue
on Jan 14, 2026 - added a commit that references this issue
on Jan 21, 2026 - added a commit that references this issue
on Jan 21, 2026 - added a commit that references this issue
on Jan 27, 2026 5 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 2, 2026 - added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Feb 3, 2026 - added a commit that references this issue
on Feb 17, 2026 - added a commit that references this issue
on Feb 26, 2026
Metadata
Metadata
Assignees
Labels
No labels
In the section called "On Google Compute Engine", this page says that authorization is handled for me with no configuration. But the example directly below shows using an explicit JSON key file:
In fact, this is identical to the example used in the "Elsewhere" section.