especially for our coworkers that aren't that deep into puppet and for which unerstanding hiera regularly is the most complicated part of the setup.
Thanks for the feedback, that is exactly the goal of the project. It makes me happy to know that someone sees potential in this. * Have you thoght about integrating support for hiera-enc? Wasn’t aware of it, so I need time to investigate what it does. * Some kind of git commit function for the changes done would be a neat feature. This would certain parts of our coworkers to stay completely in this kind of editor as they probably only interact with hiera data. If you are interested I have some ideas how this could be implemented in a safe and convenient way. Yes, that is definitely planned. I want it to the level the editor would highlight classes/yaml files/directories with green/blue/red colors to indicate staging status. Obviously, with commit/discard buttons. I also want to implement actual module installation (assuming everyone just adds them as submodules to their repo). * Is there support for changing a value at every depth of the configured hiera hierachy? Not quite sure about that, it can edit classes (their fields) and resources (and their fields), would appreciate an example of what you mean. * Does this include module-level data directories? Not as of yet. * Are you aware of jerakia (http://jerakia.io/). We don't use it yet but are considering it to be able to use our "hiera" data from ansible too. But I think it's a very interesting project. I am not but I am pretty sure we have different goals. I want make a tool for those who have no idea what Puppet is but need to use it. * Is the hieraresources part optional? We don't want to use hiera to define arbitrary resources as it would work around the way we define roles and profiles. It is, you can just do hiera_include('classes') instead if you only need to manage classes. But as long as you won’t create any resource in the tool it won’t populate the `resources` hash and thus the second line hiera_resources('resources') of the hieraresources module won’t do anything. I implemented this because there is a case when you actually need your instances of profiles several times. From: Karsten Heymann Sent: Wednesday, January 9, 2019 13:25 To: puppet-users@googlegroups.com Subject: Re: [Puppet Users] A GUI tool for Hiera Hi Alex, that sounds definitely very interesting, especially for our coworkers that aren't that deep into puppet and for which unerstanding hiera regularly is the most complicated part of the setup. Some questions and remarks: * Have you thoght about integrating support for hiera-enc? * Some kind of git commit function for the changes done would be a neat feature. This would certain parts of our coworkers to stay completely in this kind of editor as they probably only interact with hiera data. If you are interested I have some ideas how this could be implemented in a safe and convenient way. * Is there support for changing a value at every depth of the configured hiera hierachy? * Does this include module-level data directories? * Are you aware of jerakia (http://jerakia.io/). We don't use it yet but are considering it to be able to use our "hiera" data from ansible too. But I think it's a very interesting project. * Is the hieraresources part optional? We don't want to use hiera to define arbitrary resources as it would work around the way we define roles and profiles. So thank you for starting this, we are definitely interested in what progress you will make. Best regards Karsten Am Di., 8. Jan. 2019 um 18:57 Uhr schrieb desertkun <desert...@gmail.com>: Hello, everyone. I have made a small useful open source project for Puppet/Hiera, so I hope you can excuse me a bit of advertisement of it for greater good. https://github.com/desertkun/hiera-editor Basically it takes editing Hiera configurations to a new level. It parses modules with puppet-strings to extract class information like field names, types and doc strings, and retrieves default values of class fields by doing best-effort compilation (with puppet-parser) of Puppet AST on your machine. So no more typos and less of "commit-deploy-check" cycles. The goal of the project is to help manage servers with Puppet to those who far away from the back-end, including Puppet itself, like "I need to deploy nglinx but I have installed debian for the first time". So if you have a project that complex that requires Puppet to deploy it, having some tool to introduce Puppet to end users of your project might improve the learning curve. Would really appreciate any input on the idea, including concerns like "there's no need for this" as I just have made the project public and still not sure if I should continue. Regards. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1eb43a86-8f65-42d6-910f-9d45a8789256%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/YYFYaDphwbU/unsubscribe. To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAL017hCAj_XsOfG%3D7aaJAV56JbBXm96U1p32DqCXW1GXK--Z0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5c35df85.1c69fb81.9c0db.e020%40mx.google.com. For more options, visit https://groups.google.com/d/optout.
