Jira (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-500 Incoherence in YAML parser Change By: Henrik Lindberg Team: Puppet Developer Support 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 (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg commented on HI-500 Re: Incoherence in YAML parser The hiera_xxx functions do not work with data in environments and modules. They never will. The intent is to use automatic data binding, using lookup of exactly the same key as the automatic data binding performs is a no-op (meaningless) as if the key exists it is set and the default value _expression_ (calling the lookup) is never evaluated. Using a lookup in the default vallue _expression_ is only meaningful if you are looking up a different key. I think you would benefit from discussion how to do these things with members of the community, on IRC or via the mailinglist. Nevertheless, there seems to be something that is different depending on if yaml files are correct with '' tag or not. I am not sure I understood exactly how you derived at this difference. Ping Thomas Hallgren any thoughts on this? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-500) Incoherence in YAML parser
Title: Message Title
Maxime Anciaux commented on HI-500
Re: Incoherence in YAML parser
Here my module (init.pp)
class firewall (
$fw_rules
) {
$fw_rules.each |String $name, Hash $rule| {
create_resources('firewalld',{$name => $rule})
}
}
Configuring to use data_provider hiera (in the metadata.json) I even try using the lookup function
(something like that, and with the hiera function instead of lookup)
class firewall (
) {
Jira (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg commented on HI-500 Re: Incoherence in YAML parser Thanks, that took this a bit further... What do you mean by "when I use a lookup on my module"? I do understand the config you have and the command that worked. I need to understand what your configuration was / what the files looked like when it did not work, what you did, and what you expected the outcome to be. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-500) Incoherence in YAML parser
Title: Message Title Maxime Anciaux commented on HI-500 Re: Incoherence in YAML parser I'll try to be more explicit then. I'm using hiera format 4 with code like this: --- version: 4 datadir: data hierarchy: - name: "Nodes" backend: yaml path: "node.yaml" - name: "common" backend: yaml path: "common.yaml" Node.yaml look like :
Jira (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-500 Incoherence in YAML parser Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg commented on HI-500 Re: Incoherence in YAML parser Obviously YAML files must be valid YAML. What is valid is unfortunately decided by the YAML implementation, and it may vary between Ruby versions. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg commented on HI-500 Re: Incoherence in YAML parser Maxime Anciaux Can you describe in more detail what you defined, what you expected and what you got. It is hard to understand your description of the problem. What we need is to be able to reproduce the problem. Can you help us with that? I am keeping this ticket in the Hiera project until we know what the problem really is. When using lookup there are two parts in play; the hiera project and its backends, and the corresponding implementation in Puppet (hiera format 4, and the data providers for environments and modules). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg assigned an issue to Maxime Anciaux Hiera / HI-500 Incoherence in YAML parser Change By: Henrik Lindberg Assignee: Aaron Armstrong Maxime Anciaux Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-500) Incoherence in YAML parser
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-500 Incoherence in YAML parser Change By: Henrik Lindberg Component/s: PE Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 (HI-500) Incoherence in YAML parser
Title: Message Title Maxime Anciaux created an issue Hiera / HI-500 Incoherence in YAML parser Issue Type: Improvement Assignee: Aaron Armstrong Components: Community, PE Created: 2016/02/26 2:17 AM Priority: Minor Reporter: Maxime Anciaux My YAML file missed the '---' at the beginning. When I ran 'puppet lookup my_var' I was getting the first encountered value, but in my module, I was getting only the last one (common.yaml). After adding those '---', I was getting the first encountered value. Those 2 different behavior seems incoherent to me. Add Comment
