From 34f8fe7b21800ea68ffb50a6cba0013440ff5cd7 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Thu, 16 Feb 2012 12:12:18 +0100 Subject: [PATCH] reference puppet documentation Signed-off-by: Nico Schottelius --- .../puppet-name-is-not-as-expected-but-classname.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/blog/puppet-name-is-not-as-expected-but-classname.mdwn b/blog/puppet-name-is-not-as-expected-but-classname.mdwn index 9626127b..4c5288e6 100644 --- a/blog/puppet-name-is-not-as-expected-but-classname.mdwn +++ b/blog/puppet-name-is-not-as-expected-but-classname.mdwn @@ -34,6 +34,17 @@ The internal alias message is a bit confusing (I did not intentionally create an alias), but that puppet is using the classname instead of the name supplied to file is surprising. +**Update:** I've found the correct documentation part in the +[puppet language guide](http://docs.puppetlabs.com/guides/language_guide.html) +that describes the feature I was trying to use: + + Most resources have an attribute (often called simply name) whose value + will default to the title if you don’t specify it. (Internally, this is + called the “namevar.”) For the file type, the path will default to the + title. A resource’s namevar value almost always has to be unique. + (The exec and notify types are the exceptions.) + + ## The solution Well, there are two solutions: