Jira (HI-600) Hiera is Incorrectly detecting tabs (\t) as indent characters, when they are separation characters

[Tommy McNeely (JIRA)]

Title: Message Title

Tommy McNeely created an issue   Hiera / HI-600 Hiera is Incorrectly detecting tabs (\t) as indent characters, when they are separation characters Issue Type: Bug Assignee: Unassigned Created: 2018/04/24 2:59 PM Environment: CentOS 7.5 x86_64, Puppet Enterprise 2017.3.5 Priority: Normal Reporter: Tommy McNeely While adding saz-ssh, and the requisite hieradata, I copied some entries from /etc/ssh/sshd_config to the hiera key `ssh::server_options` and added the colons and indenting. The "AuthorizedKeysFile" apparently has a "tab" character between the key and value in the config file. Here is a very small snippet of the hiera config: hieradata/common.yaml ##### # ssh: https://forge.puppet.com/saz/ssh # NOTE: Remember to put 'yes' or 'no' in quotes so that it is a "string" and not a boolean (True/False) ssh::use_issue_net: true # CCE-CCE-27314-4 ssh::storeconfigs_enabled: false # For now ssh::server_options: AuthorizedKeysFile: .ssh/authorized_keys ChallengeResponseAuthentication: 'no' Ciphers: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc # CCE-CCE-27295-5     That configuration seemed to run fine with puppet apply, however with puppet agent (against PE 2017.3.5), I got the following error: error Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Unable to parse (/etc/puppetlabs/code/environments/hieratest/hieradata/common.yaml): found character '\t(TAB)' that cannot start any token. (Do not use \t(TAB) for indentation) while scanning for the next token at line 503 column 22 on node linux-sandbox.domain.corp NOTE: that is the (space)(space)AuthorizedKeys:(tab).ssh/authorized_keys line above. I have removed the offending tabs, as the error message was awesome in leading me exactly to the spot that it was unhappy about. However, according to the yaml spec: http://yaml.org/spec/1.2/spec.html#id2778241 the tab character is valid as a "separation" character (not an "indent" character). This means that tools like yamllint or yaml-lint do not detect this problem, but puppet runs barf. I am not entirely sure this isn't a puppetserver problem (as it works with puppet apply. Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.