On 2015-19-08 8:39, David Racodon wrote:
Hi John,
Thanks for your feedback. Actually, puppet-lint goes against this
recommendation because it flags quoted resource titles containing only a
variable as an issue: "string containing only a variable on line 8".
Which is a different problem,
Hi John,
Thanks for your feedback. Actually, puppet-lint goes against this
recommendation because it flags quoted resource titles containing only a
variable as an issue: string containing only a variable on line 8.
Regards,
David RACODON
Freelance QA Consultant
LinkedIn
On Saturday, August 15, 2015 at 9:12:53 PM UTC-5, Rich Burroughs wrote:
Hi David,
My guess is that this is because of the guideline in section 9.1 that all
resource titles be quoted. So that is the area where it should be done for
consistency. Otherwise if you have a standalone variable
Thanks for your feedback Rich.
David RACODON
Freelance QA Consultant
LinkedIn https://ch.linkedin.com/pub/david-racodon/11/62/283 | Twitter
https://twitter.com/davidracodon
On Sun, Aug 16, 2015 at 4:12 AM, Rich Burroughs r...@richburroughs.com
wrote:
Hi David,
My guess is that this is
Hi David,
My guess is that this is because of the guideline in section 9.1 that all
resource titles be quoted. So that is the area where it should be done for
consistency. Otherwise if you have a standalone variable elsewhere in your
manifest, it's not necessary to quote it.
Generally the
Hi,
The Puppet Language Style Guide states
at https://docs.puppetlabs.com/guides/style_guide.html#quoting that
Variables standing by themselves should not be quoted, unless they are a
resource title. So, it means that you should write:
file { ${foo}:
...
}
instead of:
file { $foo:
...