On Sun, Feb 22, 2009 at 12:02 PM, Luke Kanies <l...@madstop.com> wrote:
>
> On Feb 21, 2009, at 6:24 PM, Ohad Levy wrote:
>
>>
>>
>> On Sun, Feb 22, 2009 at 2:42 AM, Luke Kanies <l...@madstop.com> wrote:
>>
>>
>> I could see some other version numbers making their way to the URI at
>> some point, but those would likely be per-resource, rather than site-
>> wide, and each resource type has a lot of control over how its portion
>> of the URI is managed.
>>
>> Which kind of versions? If you mean module versions, than I would
>> prefer to have an environment build out of it rather then directly
>> accessing the modules.
>
> I mean API versions.  E.g., right now, the URI always looks like this:
>
> /$indirection_name/$key
>
> where $indirection_name is the type of resource, such as node,
> catalog, facts, etc., and $key is the specific resource (which can be
> a further portion of a URI, such as a relative file name).
>
> So we could say that this counts as version 1.0 of the API.  Then say
> we change it to look like:
>
> /$environment/$indirection_name/$key
>
> And we might say that's v2.0.
>
> Really, we should probably do something like:
>
> /$version/$environment/$indirection_name/$key
>
> Or maybe:
>
> /$environment/$indirection_name/$version/$key
>
> So that the indirection types can be versioned independently.  Hmm.
> Yeah, I think I like that best.
>
> Thoughts?

If you're going to go down this path, I would say you'd definitely
want the indirection types to be versioned independently.

-- 
Nigel Kersten
Systems Administrator
Tech Lead - MacOps

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com
To unsubscribe from this group, send email to 
puppet-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to