We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I see some strange behaviour of strict_indent when linting my Bolt plans.
strict_indent
pdk bundle exec puppet-lint plans/fix_bond0.pp ... WARNING: indent should be 8 chars and is 0 on line 23 (check: strict_indent)
Line 23 is 1st line of an indented heredoc (https://puppet.com/docs/puppet/7/lang_data_string.html#lang_data_string_heredocs-stripindent)
[Match]
I tried to change indentation of the heredoc but it didn't help.. message is still the same.
Plan is below (slightly redacted):
plan example::fix_bond0( TargetSpec $targets, String $run_as = 'root', Boolean $noop = true, ) { apply_prep($targets, { _run_as => $run_as }) $res = apply($targets, { _run_as => $run_as, _noop => $noop, _catch_errors => true, }) { $bond0 = $facts['networking']['interfaces']['bond0'] file { '/etc/systemd/network/bond0.network': ensure => 'file', backup => '.bak', owner => 'root', group => 'root', mode => '0644', show_diff => true, content => @("EOD"), [Match] Name=bond0 [Link] MTUBytes=${bond0['mtu']} MACAddress=${bond0['mac'].upcase} ActivationPolicy=always-up [Network] VLAN=public VLAN=private | EOD } ~> exec { 'networkctl_reload': command => '/usr/bin/networkctl reload', refreshonly => true, } } }
The text was updated successfully, but these errors were encountered:
Duplicate of #20
Sorry, something went wrong.
No branches or pull requests
I see some strange behaviour of
strict_indent
when linting my Bolt plans.Line 23 is 1st line of an indented heredoc (https://puppet.com/docs/puppet/7/lang_data_string.html#lang_data_string_heredocs-stripindent)
I tried to change indentation of the heredoc but it didn't help.. message is still the same.
Plan is below (slightly redacted):
The text was updated successfully, but these errors were encountered: