You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 3, 2024. It is now read-only.
* We no longer need cloud-platform scope.
* The API has consolidated to cloud_debugger as the single scope.
cloud_debugletcontroller doesn't seem to be a valid scope anymore.
* Simplify readme.
// Require and start in the startup of your application:
27
27
var debug =require('@google-cloud/debug')();
28
28
debug.startAgent();
29
-
// No config necessary if your code is running on Google Cloud Platform.
29
+
// No auth necessary if your code is running on Google Cloud Platform.
30
30
31
31
// ... or, if you are running elsewhere, you can manually provide credentials:
32
32
var debug =require('@google-cloud/debug')({
@@ -41,23 +41,7 @@ the [Google Cloud Console][dev-console]. You can start adding snapshots and log-
41
41
42
42
## Running on Google Cloud Platform
43
43
44
-
There are three different services that can host Node.js application to Google Cloud Platform.
45
-
46
-
### Google App Engine Flexible Environment
47
-
48
-
If you are using [Google App Engine Flexible Environment ](https://cloud.google.com/appengine/docs/flexible/), you do not have to do any additional configuration.
49
-
50
-
### Google Compute Engine
51
-
52
-
Your VM instances need to be created with `cloud-platform` scope if created via [gcloud](https://cloud.google.com/sdk) or the 'Allow API access' checkbox selected if created via the [console](https://console.cloud.google.com) (see screenshot).
53
-
54
-

55
-
56
-
If you already have VMs that were created without API access and do not wish to recreate it, you can follow the instructions for using a service account under [running elsewhere](#running-elsewhere).
57
-
58
-
### Google Container Engine
59
-
60
-
Container Engine nodes need to also be created with the `cloud-platform` scope, which is configurable during cluster creation. Alternatively, you can follow the instructions for using a service account under [running elsewhere](#running-elsewhere). It's recommended that you store the service account credentials as [Kubernetes Secret](http://kubernetes.io/v1.1/docs/user-guide/secrets.html).
44
+
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).
61
45
62
46
## Running elsewhere
63
47
@@ -104,7 +88,7 @@ If your application is running outside of Google Cloud Platform, such as locally
104
88
105
89
gcloud beta debug source gen-repo-info-file
106
90
107
-
## Debug Agent Settings
91
+
## Debugger Agent Settings
108
92
109
93
You can customize the behaviour of the automatic debuggeragent. See [the agent configuration][config-js] for a list of possible configuration options. These options can be passed to the agent through the object argument to the startAgent method as shown below:
110
94
@@ -160,6 +144,7 @@ As soon as that line of code is reached in any of the running instances of your
0 commit comments