This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
Describe enabling Debugging API access scopes for GCE instances in README #224
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kjin
requested review from
ofrobots,
matthewloring,
cristiancavalli and
DominicKramer
googlebot
added
the
cla: yes
kjin
changed the title
matthewloring
suggested changes
Jan 20, 2017
|
|
||
| For new Google Compute Engine instances, you need to explicitly enable the Debugger API access scope. From the web UI, you can do this in one of two ways under **Identity and API access**: | ||
| * Use the Compute Engine default service account and select "Allow full access to all Cloud APIs" under Access scopes. | ||
| * Select a service account with the **Cloud Debugger Agent** role (or any role with at least the same permissions). You may need to create one if you don't have one already. |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
| Stackdriver debugger agent should work out of the box if your code is running on Google Cloud Platform, just make sure that the [Stackdriver Debugger API][debugger-api] is enabled on your project (this is the default). | ||
| The Stackdriver Debugger Agent should work without manually provided authentication credentials for instances running on Google Cloud Platform, as long as the [Stackdriver Debugger API][debugger-api] access scope is enabled on that instance. For Google App Engine instances, this is automatic if the Debugger API has been enabled for your project (which it is by default). | ||
|
|
||
| For new Google Compute Engine instances, you need to explicitly enable the Debugger API access scope. From the web UI, you can do this in one of two ways under **Identity and API access**: |
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
This comment was marked as spam.
This comment was marked as spam.
Sorry, something went wrong.
matthewloring
approved these changes
Jan 24, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GCP console doesn't automatically enable the Stackdriver Debugger API for new GCE instances with the default options, so I've made changes to the README describing how to do so.