The quotation mark and closing parenthesis were swapped.
Before:
```
$ echo "Hello kitty" | yq eval 'test("(?i)cats)"'
Error: bad expression - probably missing close bracket on TEST
```
After:
```
$ echo "Hello kitty" | yq eval 'test("(?i)cats")'
false
```
1.6 KiB
String Operators
RegEx
This uses Golang's native regex functions under the hood - See their docs for the supported syntax.
Case insensitive tip: prefix the regex with (?i) - e.g. test("(?i)cats").
match(regEx)
This operator returns the substring match details of the given regEx.
capture(regEx)
Capture returns named RegEx capture groups in a map. Can be more convenient than match depending on what you are doing.
test(regEx)
Returns true if the string matches the RegEx, false otherwise.
sub(regEx, replacement)
Substitutes matched substrings. The first parameter is the regEx to match substrings within the original string. The second parameter specifies what to replace those matches with. This can refer to capture groups from the first RegEx.
String blocks, bash and newlines
Bash is notorious for chomping on precious trailing newline characters, making it tricky to set strings with newlines properly. In particular, the $( exp ) will trim trailing newlines.
For instance to get this yaml:
a: |
cat
Using $( exp ) wont work, as it will trim the trailing newline.
m=$(echo "cat\n") yq -n '.a = strenv(m)'
a: cat
However, using printf works:
printf -v m "cat\n" ; m="$m" yq -n '.a = strenv(m)'
a: |
cat
As well as having multiline expressions:
m="cat
" yq -n '.a = strenv(m)'
a: |
cat
Similarly, if you're trying to set the content from a file, and want a trailing newline:
IFS= read -rd '' output < <(cat my_file)
output=$output ./yq '.data.values = strenv(output)' first.yml