Jira (PUP-3026) 3 Keys needed for uniqueness of host entries
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3026 3 Keys needed for uniqueness of host entries Change By: Moses Mendoza Labels: help_wanted triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3026) 3 Keys needed for uniqueness of host entries
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3026 3 Keys needed for uniqueness of host entries Change By: Josh Cooper Labels: help_wanted triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3026) 3 Keys needed for uniqueness of host entries
Title: Message Title Josh Cooper commented on PUP-3026 Re: 3 Keys needed for uniqueness of host entries Thank you for filing this issue. We agree it is likely an improvement, but due to other issues demanding precedence, we don’t anticipate being able to address this any time soon. As such we are closing this as “Won’t Fix.” We may revisit it at a later time, and if so will re-open this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3026) 3 Keys needed for uniqueness of host entries
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-3026
3 Keys needed for uniqueness of host entries
Change By:
Josh Cooper
A client is trying to add new solaris zones using puppet but they also need to set host entries per zone. This means that they end having duplicate entries for hosts because they want to add the same entry for multiple zones. The difference in the host resource entries is the target directory.The enhancement would be to include the target directory as a third variable that should be used to determine uniqueness. {code:puppet} host { 'anentry': name => 'blah.example.com', ensure => present, host_aliases => ['blah1','blah2'], ip => '8.8.8.8',}host { 'bnentry': name => 'blah.example.com', ensure => present, host_aliases => ['blah1','blah2'], ip => '8.8.8.8', target => '/etc/aaa',} {code} The above code should thus end up being valid and not invalid as it currently stands.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3026) 3 Keys needed for uniqueness of host entries
Title: Message Title
Gerrard Geldenhuis created an issue
Puppet / PUP-3026
3 Keys needed for uniqueness of host entries
Issue Type:
Improvement
Assignee:
Unassigned
Created:
07/Aug/14 5:49 AM
Priority:
Normal
Reporter:
Gerrard Geldenhuis
A client is trying to add new solaris zones using puppet but they also need to set host entries per zone. This means that they end having duplicate entries for hosts because they want to add the same entry for multiple zones. The difference in the host resource entries is the target directory.
The enhancement would be to include the target directory as a third variable that should be used to determine uniqueness.
host { 'anentry': name = 'blah.example.com', ensure = present, host_aliases = ['blah1','blah2'], ip = '8.8.8.8', }
host { 'bnentry': name = 'blah.example.com', ensure = present, host_aliases = ['blah1','blah2'], ip = '8.8.8.8', target = '/etc/aaa', }
The above code should thus end up being valid and not invalid as it currently stands.
Add Comment
