[Puppet - Bug #18023] Puppet needs a public, clearly-defined Ruby API
Issue #18023 has been updated by eric sorenson. Priority changed from Normal to High Target version changed from 3.x to 3.1.0 This is underway as part of the Ruby DSL in #16937. Bumping priority/target to indicate it's in the current workload. Bug #18023: Puppet needs a public, clearly-defined Ruby API https://projects.puppetlabs.com/issues/18023#change-80128 Author: eric sorenson Status: Accepted Priority: High Assignee: eric sorenson Category: Target version: 3.1.0 Affected Puppet version: Keywords: backlog Branch: One of the problems people run into using Puppet as part of an infrastructure ecosystem is that there isn't a clearly defined Ruby API for it. There are REST endpoints that expose some functionality over the network, but they do not cover much of the total surface area of what Puppet can do, and things that are important for third parties aee probably never going to be exposed over the network. (A real-world use case: Foreman wants access to puppet master's configuration settings so it can integrate with the CA auth/issuance code). Today, people poke directly at internal methods, which both makes it difficult to change method signatures and control flow AND provides a crappy experience for tool authors. So Puppet should have a real, public, published (see #16426) API that the development team commits to and the outside world can trust. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #18023] Puppet needs a public, clearly-defined Ruby API
Issue #18023 has been updated by eric sorenson. Priority changed from High to Immediate Bug #18023: Puppet needs a public, clearly-defined Ruby API https://projects.puppetlabs.com/issues/18023#change-80136 Author: eric sorenson Status: Accepted Priority: Immediate Assignee: eric sorenson Category: Target version: 3.1.0 Affected Puppet version: Keywords: backlog Branch: One of the problems people run into using Puppet as part of an infrastructure ecosystem is that there isn't a clearly defined Ruby API for it. There are REST endpoints that expose some functionality over the network, but they do not cover much of the total surface area of what Puppet can do, and things that are important for third parties aee probably never going to be exposed over the network. (A real-world use case: Foreman wants access to puppet master's configuration settings so it can integrate with the CA auth/issuance code). Today, people poke directly at internal methods, which both makes it difficult to change method signatures and control flow AND provides a crappy experience for tool authors. So Puppet should have a real, public, published (see #16426) API that the development team commits to and the outside world can trust. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #18023] Puppet needs a public, clearly-defined Ruby API
Issue #18023 has been updated by R.I. Pienaar. Which part of that ticket addresses this? I wasnt aware this was part of that, I am working on a new Puppet agent for mcollective so would be good to know whats up Bug #18023: Puppet needs a public, clearly-defined Ruby API https://projects.puppetlabs.com/issues/18023#change-80138 Author: eric sorenson Status: Accepted Priority: Immediate Assignee: eric sorenson Category: Target version: 3.1.0 Affected Puppet version: Keywords: backlog Branch: One of the problems people run into using Puppet as part of an infrastructure ecosystem is that there isn't a clearly defined Ruby API for it. There are REST endpoints that expose some functionality over the network, but they do not cover much of the total surface area of what Puppet can do, and things that are important for third parties aee probably never going to be exposed over the network. (A real-world use case: Foreman wants access to puppet master's configuration settings so it can integrate with the CA auth/issuance code). Today, people poke directly at internal methods, which both makes it difficult to change method signatures and control flow AND provides a crappy experience for tool authors. So Puppet should have a real, public, published (see #16426) API that the development team commits to and the outside world can trust. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #18023] Puppet needs a public, clearly-defined Ruby API
Issue #18023 has been updated by eric sorenson. RI - as part of the dsl, henrik and patrick added YARD docs throughout the codebase to declare public/private methods and document the method signatures https://github.com/puppetlabs/puppet/pull/1366 Bug #18023: Puppet needs a public, clearly-defined Ruby API https://projects.puppetlabs.com/issues/18023#change-80141 Author: eric sorenson Status: Accepted Priority: Immediate Assignee: eric sorenson Category: Target version: 3.1.0 Affected Puppet version: Keywords: backlog Branch: One of the problems people run into using Puppet as part of an infrastructure ecosystem is that there isn't a clearly defined Ruby API for it. There are REST endpoints that expose some functionality over the network, but they do not cover much of the total surface area of what Puppet can do, and things that are important for third parties aee probably never going to be exposed over the network. (A real-world use case: Foreman wants access to puppet master's configuration settings so it can integrate with the CA auth/issuance code). Today, people poke directly at internal methods, which both makes it difficult to change method signatures and control flow AND provides a crappy experience for tool authors. So Puppet should have a real, public, published (see #16426) API that the development team commits to and the outside world can trust. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
[Puppet - Bug #18023] Puppet needs a public, clearly-defined Ruby API
Issue #18023 has been updated by R.I. Pienaar. I totally commented on the wrong ticket, d'oh, ignore that :) Bug #18023: Puppet needs a public, clearly-defined Ruby API https://projects.puppetlabs.com/issues/18023#change-80145 Author: eric sorenson Status: Accepted Priority: Immediate Assignee: eric sorenson Category: Target version: 3.1.0 Affected Puppet version: Keywords: backlog Branch: One of the problems people run into using Puppet as part of an infrastructure ecosystem is that there isn't a clearly defined Ruby API for it. There are REST endpoints that expose some functionality over the network, but they do not cover much of the total surface area of what Puppet can do, and things that are important for third parties aee probably never going to be exposed over the network. (A real-world use case: Foreman wants access to puppet master's configuration settings so it can integrate with the CA auth/issuance code). Today, people poke directly at internal methods, which both makes it difficult to change method signatures and control flow AND provides a crappy experience for tool authors. So Puppet should have a real, public, published (see #16426) API that the development team commits to and the outside world can trust. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To post to this group, send email to puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
