ansible-lint line length exceeded and ssh pub keys

[RobVerduijn]

Hi,

I noticed an interesting thing about the ansible-lint line length exceeded error.
It's fine when you're doing regular stuff, and most issues can be avoided by using yaml multi line tricks

But when you set up a host_var in host_vars/my_host.yml using the special ansible variable ansible_pubkey the line length exceeds the 160 character limit quite a bit

576 chars is the line length in my case ( pub key generated with ssh-keygen/openssh-8.8p1 on fedora37)
So snipping of my email and using multiline '>-' isn't really putting a dent in that number.
(there are 2 spaces in the entire line, the one after the ssh-rsa in the beginning and the one before the email at the end)

And disabling the length exceeded check globally isn't really what I'm looking for.

Any ideas on how to deal with this ?

Rob

[AndrewKvalheim]

Double-quoted flow scalars:

example: "ssh-rsa xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxx example"

[muellert]

@AndrewKvalheim I'm not sure what the question is. I thought we're discussing long lines here, and while I understand that there are ways to work around this in pure Yaml, I'm lacking a way to disable this check for code that is technically within a playbook, but can't adhere to Yaml conventions because it has different syntax and semantics (nginx configuration file, in my case). It would be nice to have a way to tell ansible-lint to ignore such embedded blocks.

[AndrewKvalheim]

@muellert I have no idea what question you’re talking about. I have been ignoring you because it sounds like you’re describing a different problem and I don’t understand why you’re raising it here.

[mickaelperrin]

Double-quoted flow scalars:

example: "ssh-rsa xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\
  xxxxxxxxxxxxxxxxxxxx example"

That's interesting, I am struggling on how to use ansible-lint with my repo. I have some pub keys in ansible variables, and can't get a way to pass the linter fix/check.

Currently, the double-quoted flow scalars syntax is automatically transformed by the ansible-lint --fix command to a single line that exceeds the line length.

As ansible-lint, check/fix the syntax of every files in the repo, I am unable to have a commit working with the precommit hook using the ansible linter. I have to use the "--no-verify" argument to every git commit currently.

I don't want to disable the rule because it worked well for every other types of lines where I can have spaces.

Any hint ?

[AndrewKvalheim]

Sounds like you’re describing #4233

[mickaelperrin]

Interesting, but I don't have a custom .yamllint file.

See the following file and repo, I reproduced the issue in a minimal example: https://github.com/mickaelperrin/ansible-lint-issues/blob/master/roles/ansible_lint_tests/tasks/main.yml