Jira (HI-152) %{calling_class} yaml paths do not function on windows
Title: Message Title
Rob Reynolds commented on HI-152
Re: %{calling_class} yaml paths do not function on windows
Is this resolved by
PUP-3462
?
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-152) %{calling_class} yaml paths do not function on windows
Title: Message Title
Rob Reynolds updated an issue
Hiera / HI-152
%{calling_class} yaml paths do not function on windows
Change By:
Rob Reynolds
Fix Version/s:
HI 1.4.0
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-152) %{calling_class} yaml paths do not function on windows
Title: Message Title
Joshua Cooper updated an issue
Hiera / HI-152
%{calling_class} yaml paths do not function on windows
Change By:
Joshua Cooper
Labels:
windows
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-152) %{calling_class} yaml paths do not function on windows
Title: Message Title
Laurent Rolaz commented on an issue
Re: %{calling_class} yaml paths do not function on windows
Maybe it'll be clean to export a calling_class_location pseudo-variable that represents the path inside the module. It's actually the way :: is represented in the filesystem.
Example :
profile::ssh::server
is stored in the module profile and folder ssh/server. The pseudo-variables might be :
calling_module = "profile"
calling_class = "profile::ssh::server"
calling_class_location = "ssh/server"
Should work ...
Add Comment
Hiera / HI-152
%{calling_class} yaml paths do not function on windows
My organization has a pre-existing hiera configuration which uses {calling_class}.yaml configuration files, like: classes/base::openldap.yaml Which get pulled into hiera via this path in the hierarchy. :hierarchy: ... - "%{environment}/classes/%{calling_class}" This does not work on Windows. Windows does not support colons in filenames so ...
T
Jira (HI-152) %{calling_class} yaml paths do not function on windows
Title: Message Title
Ben Hines created an issue
Hiera / HI-152
%{calling_class} yaml paths do not function on windows
Issue Type:
Improvement
Affects Versions:
1.3.0
Assignee:
Eric Sorenson
Created:
23/Jan/14 4:49 PM
Priority:
Normal
Reporter:
Ben Hines
My organization has a pre-existing hiera configuration which uses {calling_class}.yaml configuration files, like: classes/base::openldap.yaml Which get pulled into hiera via this path in the hierarchy. :hierarchy: ... - "%{environment}/classes/%{calling_class}
"
This does not work on Windows. Windows does not support colons in filenames so the .yaml can't even be checked out from source control. This presents issues when developing our puppet manifests on windows and sharing them with a Vagrant VM, for example.
It'd be really nice if hiera supported reading calling_class files from files which did not use colons as separators. Perhaps it could look up the class via a 'backup' parameter if the colon version does not exist? (and it'd have to do this on every OS.. since the problem is a directory which is checked out on both windows and linux.. perhaps could be an option?)
Maybe a new field, {%calling_class_safe}
which reads from profile_base.yaml instead of profile::base.yaml? ? I'm not sure what the cleanest fix is.
thanks-
