On Tue, May 1, 2012 at 10:32, R.I.Pienaar <[email protected]> wrote: > ----- Original Message ----- >> From: "Daniel Pittman" <[email protected]> >> To: [email protected] >> Sent: Tuesday, May 1, 2012 6:17:53 PM >> Subject: Re: [Puppet-dev] Hiera should have an save API >> >> On Tue, May 1, 2012 at 09:31, Kelsey Hightower >> <[email protected]> wrote: >> >> > I'm thinking of adding a new save API to Hiera. The idea is that >> > Hiera >> > should provide an iterface for saving data, which should make it >> > easy for >> > front-end tools to interact with backends that support saving data. >> >> Why does it make it any easier than having tools with already know >> about their back-end semantics directly managing that data? It has >> substantial limitations (eg: no user concept, no credentials, and no >> way to determine the appropriate set based on the back-end.) > > This has been my main concern too and why I never implemented anything like > this > in the first place - I think the data being queried is best modelled > elsewhere. > The data is best created at the time when you classify a node in that same UI > - > hiera should query that data but not know too much about the visual aspects of > it.
I am not certain they need to be tied together in time like that, but I agree that Hiera does better as middleware for query between some rich backend that owns "how to update me", and the consumers of the data. > This would be usable for small installs who just use the json/yaml backends > and > have no node classification system (other than maybe hand editing these files > and using hiera_include or something). People who are already happy to just > hand hack JSON/YAML anyway. ...even if the "how to update me" is to use a text editor. >> > Do people think this is a good idea? I see this as a foundational >> > bit for building UI's on top of Hiera. >> >> The principal is reasonable, but this isn't even close to a proposal >> for a save API that works in the real world. > > I would love to see a solution for this but its deceptively hard to do > and I think ultimately better solved by exposing a REST API into your > dasbhoard/foreman/etc where you have RBAC and the other points you > raised That is where I would generally lean - I think of the Puppet / Hiera / "modify data for Hiera" thing as a cycle - three parts, talking to each other, and each separate. Having a smarted back-end like Dashboard or Foreman feels like a better fit, overall, than trying to put abstraction in place over save. -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
