Jira (PUP-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-3918 There should be a Node Terminus that uses a local YAML file like an External Node Classifier. Change By: Moses Mendoza Labels: redmine 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-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title Sean McDonald updated an issue Puppet / PUP-3918 There should be a Node Terminus that uses a local YAML file like an External Node Classifier. Change By: Sean McDonald Labels: redmine 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-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title Matthias Saou commented on PUP-3918 Re: There should be a Node Terminus that uses a local YAML file like an External Node Classifier. I personally don't really care, though I think this would be nice to have "out of the box" given how trivial it seems to me to just read the yaml from a file. Also, the use case of wanting to copy/paste as-is an ENC YAML output to debug using puppet apply seems quite valid to me : It's so much easier and less error prone than to have to translate the YAML to Puppet DSL, or even to Hiera YAML since the ENC classes+parameters hash needs to be split up into a classes array + separate parameters for the Hiera auto lookup (unless I'm mistaken). 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 (PUP-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title Henrik Lindberg commented on PUP-3918 Re: There should be a Node Terminus that uses a local YAML file like an External Node Classifier. Does this have to be in puppet itself as opposed to being in a module? 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 (PUP-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title Matthias Saou commented on PUP-3918 Re: There should be a Node Terminus that uses a local YAML file like an External Node Classifier. I would also really like this feature. I tried the yaml node_terminus, and as some others have mentioned, it's not suitable because it expects some other kind of YAML. My use case is having a custom ENC, where changes are difficult to make since it's on production, and developers want to be able to quickly replicate a node's entire state. It's trivial to extract a node's YAML from the ENC, and once a developer has it, it needs to be used with "puppet apply". Here is my current workaround : $ cat .cat #!/bin/bash # Silly script, required for now. See : # https://tickets.puppetlabs.com/browse/PUP-3918 exec cat `dirname $0`/apply.yaml And I execute something along these lines : puppet apply -v --show_diff \ --hiera_config=/dev/null \
Jira (PUP-3918) There should be a Node Terminus that uses a local YAML file like an External Node Classifier.
Title: Message Title redmine.exporter created an issue Puppet / PUP-3918 There should be a Node Terminus that uses a local YAML file like an External Node Classifier. Issue Type: New Feature Assignee: Unassigned Created: 2015/01/28 9:06 AM Labels: redmine Priority: Normal Reporter: redmine.exporter I wrote a node terminus that pulls the node data from a local file (/etc/puppet/node.yaml) in the same format as the external node classifier. I use this in order to do experiments on a single node by running stand-alone puppet, in an environment that usually uses an external node classifier. With a local copy of the node classifier output, and a local copy of the manifests, my development cycle is: edit the node.yaml, edit the manifests, run puppet, repeat; then merge working changes up. I also use this for entirely stand-alone hosts, such as Amazon EC2 instances launched with an external node classifier Yaml file passed as User Data. Local Yaml node terminus: https://github.com/brothers/puppet/commit/251e46cadc8d366404c74d1195b874f55a2a0b66 I also wrote an mcollective client/agent pair to execute the classifier and copy the output to a local file on the node. Local Yaml client/agent: https://github.com/brothers/mcollective-plugins/commit/59ecd42fa8c9051f5f0abc83ee10d7ba445b5f57 I would like to receive feedback on this, before I clean it up and write tests for it.