On Tue, Jun 11, 2013 at 12:16 PM, David Schmitt <[email protected]> wrote: > As if anybody who has enough configurations specifying an endpoint that > changing the version number is a problem would be in the position to speak > the current API at /latest/ everywhere at the same time.
The OP indicated they wanted to always use the latest, and that it was a bother to have to change URLs in all of those services. Presumably if changing the URLs is a bother, then they're not testing/modifying those services to use the new API version. You get a choice: either always use the latest, on the assumption it will still work, or use a particular version, with the requirement to test, modify, and upgrade at some point. Also, it makes me wonder .. isn't there some tool that could update URLs in configurations across the enterprise, and restart services when those changes are made? Dustin -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
