I scraped through my code and don't seem to be using it anywhere so +1. On Fri, Mar 18, 2016 at 4:24 PM, Chris Price <[email protected]> wrote:
> > > On Wed, Mar 9, 2016 at 12:45 PM, Chris Price <[email protected]> wrote: > >> Hello, >> >> We're looking into the possibility of deprecating and removing the ` >> resource_types` endpoint from Puppet Server. >> > > Bump... haven't heard any objections to deprecating and removing the > resource_types endpoint. I'll plan on getting some more concrete tickets > about this into our issue tracker next week unless anyone raises any > last-minute objections between now and then. They'll be linked to > SERVER-1200 if anyone wants to follow along at home. Thanks! > > >> >> The current implementation can return information about a lot of different >> things in Puppet, but it's very expensive (in terms of CPU and memory >> usage), and has some unexpected side effects that can cause subsequent >> requests to other endpoints (including catalog compilation! see >> https://tickets.puppetlabs.com/browse/SERVER-1200 ) to misbehave. >> >> The main use case that we're aware of for the endpoint is to get a list of >> all of the classes (and their associated parameters) for an environment. >> We've just finished building a new HTTP endpoint called >> 'environment_classes' (which will ship in the upcoming releases of OSS and >> PE Puppet Server) that will provide that data in a cleaner, less expensive >> fashion. You can see a sneak preview of the documentation for this new >> endpoint, including its wire formats, here: >> >> >> https://github.com/puppetlabs/puppet-server/blob/dc58bdd94246e5b68bf1adff2d38bf574ca22662/documentation/puppet-api/v3/environment_classes.md >> >> Once that endpoint is available we'd like to deprecate and eventually >> remove the resource_types endpoint. However, we'd first like to make sure >> that there aren't other important use cases that users are relying on it >> for. (If there are, we'll probably try to address those by adding >> additional new HTTP endpoints until we're at feature parity for the things >> that people rely on resource_types for.) >> >> So... this is a solicitation for input. Do you currently rely on the >> resource_types endpoint for critical parts of your workflow? What kinds >> of >> things are you using it for? What would you be missing if it were to be >> removed? >> >> We've got a placeholder ticket in our issue tracking system for this >> deprecation / removal: >> >> https://tickets.puppetlabs.com/browse/SERVER-1120 >> >> It doesn't have a ton of detail yet, but if you're interested in tracking >> this, you can watch that ticket as that is where we'll end up tracking >> things as this progresses. >> >> Thanks in advance for your feedback! >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/CAMx1QfLs_SyqWe8FKdimQXmZUwLGXfcxf30d%2Bq5Sf1S7rktKzA%40mail.gmail.com > <https://groups.google.com/d/msgid/puppet-dev/CAMx1QfLs_SyqWe8FKdimQXmZUwLGXfcxf30d%2Bq5Sf1S7rktKzA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 -- This account not approved for unencrypted proprietary information -- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CANs%2BFoWG2KN3o8K%2BJxBGRv9tby5%3DCaUSE9h64BtCBJbBxOP5aw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
