Issue #23131 has been reported by Kylo Ginsberg.
----------------------------------------
Bug #23131: Empty string element in containment path array
https://projects.puppetlabs.com/issues/23131
* Author: Kylo Ginsberg
* Status: Accepted
* Priority: Normal
* Assignee: Kylo Ginsberg
* Category:
* Target version:
* Affected Puppet version:
* Keywords:
* Branch:
----------------------------------------
Now that we are storing resource containment paths in PuppetDB, we've noticed
that many of the paths that puppet passes around contain an empty element.
For example, if you watch the log messages on an agent run, you may see a
resource path logged like this:
/Stage[main]//Foo/Notify['bar']
Note the double slash after Stage. When we receive the containment path in the
report processor, it's represented as an array of strings, and in a case like
the one above, the array would look like this:
["Stage[main]", "", "Foo", "Notify['bar']"]
I'm questioning whether or not that empty string at index 1 is intentional or
not. It seems like it's probably not, and that we should probably tweak puppet
to get rid of it...
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
