-
Notifications
You must be signed in to change notification settings - Fork 238
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
Capture configuration files & runtime config in support bundle #2094
Capture configuration files & runtime config in support bundle #2094
Conversation
Ideally we should replace secret values with a placeholder. |
In the old agent one we used a custom yaml marshaller to redact the secrets, I feel we need to also redact the values here. |
Co-authored-by: Clayton Cornell <[email protected]>
…alloy into enh/support-bundle-config-file
Implemented a POC of redacting secrets in the AST & printer, but I need to consider how it affects the fmt command and other uses of printer. |
Looks reasonable but would like to see some tests around and if we need to make the behavior configurable. |
@@ -45,8 +45,11 @@ A support bundle contains the following data: | |||
* `alloy-runtime-flags.txt` contains the values of the runtime flags available in {{< param "PRODUCT_NAME" >}}. | |||
* The `pprof/` directory contains Go runtime profiling data (CPU, heap, goroutine, mutex, block profiles) as exported by the pprof package. | |||
Refer to the [profile][profile] documentation for more details on how to use this information. | |||
* The `sources/` directory contains copies of the local configuration files used to configure {{< param "PRODUCT_NAME" >}}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this include local modules? Totally fine if it doesnt but may want to add a bit more information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, minor documentation question
PR Description
Add configuration sources (local file & remote config) to the support bundle.
One thing that requires consideration -- this is not currently doing any redaction of the configuration files, should we make this opt-in/opt-out rather than always collected?
Which issue(s) this PR fixes
#2066
Notes to the Reviewer
PR Checklist