On Aug 17, 2009, at 8:12 AM, Nigel Kersten wrote: > > On Sun, Aug 16, 2009 at 5:19 PM, Luke Kanies<[email protected]> wrote: >> On Aug 14, 2009, at 6:38 PM, Nigel Kersten wrote: >>> I'm more than happy to work on getting this fixed. It's just been >>> unclear to me what is the expected behaviour in 0.25.x in this area. >> >> Expected behaviour is this: >> >> * plugins should correctly download from specific environments (and I >> could swear I tested this and they did) > > So to be absolutely clear, we should be able to have plugins in > modules in environments and have them work correctly?
If by "work" you mean "download to the client and work there", then yes. > > I just don't see any other way we get to specify plugin sources on a > per-environment basis without using $environment in $pluginsource on > the clients. All fileserving, including plugin downloading, includes the environment in the URI; something like: /$environment/$datatype/$thin It's all handled internally by the REST support, you should never have to specify it. > >> * plugins loaded into memory on the server (e.g., functions) do not >> correctly work in environments >> >> Is that clear enough? Are the other behaviours unspecified here? >> >> If you can spend time on this, great, otherwise Markus or I can try >> to >> track it down. > > looking today. Awesome. -- Everything that is really great and inspiring is created by the individual who can labor in freedom. -- Albert Einstein --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
