-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add log passthrough support #300
Conversation
node-red:3.1.x-main-linux-amd64 scan results6 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
node-red:2.2.3-main-linux-amd64 scan results26 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
node-red:3.0.2-main-linux-amd64 scan results1 files ±0 4 suites ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
file-server:main-linux-amd64 scan results1 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
node-red:2.2.3-main-linux-arm64 scan results26 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
node-red:3.0.2-main-linux-arm64 scan results1 files ±0 4 suites ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
forge-k8s:main-linux-amd64 scan results1 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
file-server:main-linux-arm64 scan results1 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
node-red:3.1.x-main-linux-arm64 scan results6 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
forge-k8s:main-linux-arm64 scan results1 tests ±0 0 ✅ ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit f6be221. ± Comparison against base commit 23a0f51. ♻️ This comment has been updated with latest results. |
part of FlowFuse/flowfuse#3324
Description
Allows NR Pod log output to be enabled
Related Issue(s)
FlowFuse/flowfuse#3324
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
backport
labelarea:migration
label