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
The mount_options field for a CSI volume can contain sensitive data, so we redact it in all our logs and API response. But the nomad volume status command shows a Mount Options = <none> field because we null-out the field when we convert from nomad/structs to api/structs (ref csi_endpoint.go#L110-L113). We should instead either send the [REDACTED] message over the wire when the value is non-nil (preferred) or remove the field from the command output entirely.
Note for reviewers: this may get tossed if I manage to get to #10470 but that's not on my "immediate todo" list.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
The
mount_options
field for a CSI volume can contain sensitive data, so we redact it in all our logs and API response. But thenomad volume status
command shows aMount Options = <none>
field because we null-out the field when we convert fromnomad/structs
toapi/structs
(refcsi_endpoint.go#L110-L113
). We should instead either send the[REDACTED]
message over the wire when the value is non-nil (preferred) or remove the field from the command output entirely.Note for reviewers: this may get tossed if I manage to get to #10470 but that's not on my "immediate todo" list.
The text was updated successfully, but these errors were encountered: