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
Copy file name to clipboardExpand all lines: test/README.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,3 +93,29 @@ Run with:
93
93
*`npm run test:integration:apk`
94
94
*`npm run test:integration:apt`
95
95
*`npm run test:integration:rpm`
96
+
97
+
## Debugging with Tilt ##
98
+
99
+
Tilt allows you to run and debug the snyk-monitor while it is running in a container. Tilt deploys the snyk-monitor using the same Helm chart that we publish to users.
100
+
101
+
You can download Tilt from the [Tilt GitHub repository](https://github.com/tilt-dev/tilt#install-tilt).
102
+
103
+
### Start a debugging session ###
104
+
105
+
First, ensure you have the snyk-monitor namespace set up and the snyk-monitor Secret with your integration ID and dockercfg (as per the prerequisites for installing snyk-monitor).
106
+
107
+
Finally, put breakpoints in the code and run `tilt up`.
... it means that the `readOnlyRootFilesystem` protection on the snyk-monitor Helm Deployment causes issues with Tilt. This can be fixed by removing the `readOnlyRootFilesystem: true` value from the Helm chart located in `snyk-monitor/templates/deployment.yaml`.
118
+
119
+
### Cleaning up ###
120
+
121
+
Run `tilt down` to tear down the debugging session.
0 commit comments