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
Please add a hash function that supports one or more algorithms - such as some of the more common options in this list like SHA-256 or MD5.
My use case only requires a cryptographic hash function, but I'm sure as a general-purpose feature then more types of hash algorithms should be supported.
I propose the hash function always returns a hex-encoded string, though an optional parameter to the hashing function could change that. Alternatively, add @hex or to_hex as an encoding function.
custom YAML parser that supports a reviver function
complex and unmaintainable mashup of shell, sed and awk
Use case:
Given
I have a YAML configuration file that contains a combination of banal data and secrets; and
I would like to compare versions of the config file and show what has changed between versions; and
I do not want to expose secrets in the output of the comparison.
Then
I would like to hash all secrets before comparison so that secrets that have changed can be flagged, but only output hashed values so secrets are not exposed (assuming SHA-256 or SHA-512).
Please add a
hash
function that supports one or more algorithms - such as some of the more common options in this list like SHA-256 or MD5.My use case only requires a cryptographic hash function, but I'm sure as a general-purpose feature then more types of hash algorithms should be supported.
I propose the hash function always returns a hex-encoded string, though an optional parameter to the hashing function could change that. Alternatively, add
@hex
orto_hex
as an encoding function.Given:
And we run a command:
yq '.country |= hash("md5")'
it could output
Things I've considered include:
Use case:
Given
Then
For example, given
and
the comparison (
yq '.avatar.password |= hash("sha256")'
on each file, thendiff
) would outputThe text was updated successfully, but these errors were encountered: