Can't ignore spercific line

[Alexhha]

We have the following yaml file

    logging:
# yamllint disable-line
%{ if cloudwatch_enabled == "true" ~}
      driver: awslogs
      options:
        awslogs-region: us-east-1
        awslogs-group: group
        awslogs-stream: ${node_id}
%{ else ~}
      driver: json-file
      options:
        max-size: "50m"
        max-file: "10"
%{ endif ~}

But I still get syntax error

$ yamllint -d '{extends: default, rules: {line-length: {max: 128}, document-start: disable, empty-lines: disable}}' docker-compose.tftpl
docker-compose.tftpl
  45:2      error    syntax error: expected alphabetic or numeric character, but found '{' (syntax)

Did I miss something ? How can I ignore terraform template syntax %{ if }...%{ else }...%{ endif } ?

P.S.

$ yamllint -v
yamllint 1.26.3

[perlpunk]

that's basically the same issue as rhe recent #460

[Alexhha]

Haven't seen the issue. Have I correctly understood - there is no way to skip checks just for 1 line in such case ?

[andrewimeson]

@Alexhha the problem is that the file isn't valid YAML, and thus yamllint can't parse it. You can't ignore parser errors. You wouldn't want yamllint to ignore parser errors, because it might incorrectly parse what comes next in the file leading to false positives or negatives.

A good workaround is to put the non-yaml content in comments, like this

    logging:
# %{ if cloudwatch_enabled == "true" ~}
      driver: awslogs
      options:
        awslogs-region: us-east-1
        awslogs-group: group
        awslogs-stream: ${node_id}
# %{ else ~}
      driver: json-file
      options:
        max-size: "50m"
        max-file: "10"
# %{ endif ~}

[Alexhha]

@andrewimeson

Unfortunately it doesn't work in such way. Got the following result

    logging:
      #       driver: json-file
      options:
        max-size: "50m"
        max-file: "10"
    #     ulimits:
      nproc: 65535
      nofile:
        soft: 32000
        hard: 40000

[mwgamble]

The real solution is to not use a string templating language to craft structured data. YAML files aren't plain text. They're structured data that has been serialised to a format that can be stored in a file (that happens to still be human editable, for better or worse).

You shouldn't rely on a string templating system that has no knowledge of what's being templated to do this properly. This is also how you wind up with cross-site scripting attacks, and it's one reason for why "traditional" stringy HTML templating engines have fallen out of favour, replaced by things like React and Vue.