-
Notifications
You must be signed in to change notification settings - Fork 42
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
[nexus] support bundle diag commands should be saved in json #7462
[nexus] support bundle diag commands should be saved in json #7462
Conversation
Created using spr 1.3.6-beta.1 [skip ci]
Created using spr 1.3.6-beta.1
) | ||
.await?; | ||
let json = serde_json::to_string(&output)?; | ||
tokio::fs::write(path.join(format!("{command}.txt")), json).await?; |
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.
Should we use a .json
suffix here?
Related: Do we want the error types to be serialized to JSON too?
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.
Fixed in e610f80
I am inclined to leave the error file alone as I feel like most of the structured output parsing will happen on the "success" path where there may be multiple commands that have ran with output that you would like to filter through.
Created using spr 1.3.6-beta.1 [skip ci]
Created using spr 1.3.6-beta.1
Created using spr 1.3.6-beta.1 [skip ci]
Created using spr 1.3.6-beta.1 [skip ci]
Created using spr 1.3.6-beta.1 [skip ci]
Created using spr 1.3.6-beta.1 [skip ci]
Created using spr 1.3.6-beta.1
Created using spr 1.3.6-beta.1 [skip ci]
Created using spr 1.3.6-beta.1
Created using spr 1.3.6-beta.1
Re-running checks due to: |
Diagnostic commands now output the json serialized value rather than the debug output for the inner type.
This is on top of: