Ok, I'll give a shot at stripping out the dependancies of the other parameters.
Regards, -Roy On Thu, Oct 1, 2009 at 4:27 PM, Luke Kanies <[email protected]> wrote: > > On Oct 1, 2009, at 2:15 PM, Roy Nielsen wrote: > > > metaparameter name collisions.... > > > > I cannot make a "path" metaparameter as the exec path parameter is > > different from the k5login path parameter. > > > > A "user" metaparameter would cause problems as the cron type and > > exec type have different implementations of a "user" parameter. > > > > A "group" metaparameter might be a problem (hard for me to tell) as > > the exec and macauthorization seem to describe it differently. > > > > A "timeout" metaparameter would cause problems as the exec and > > macauthorization timeout parameter are definitely different. > > > > A "environment" metaparameter would cause problems as the exec and > > cron types have different implementations of their "environemnt" > > parameter. > > > > While an "unless" metaparameter might be written without the above > > metaparameter functionality . . . it doesn't seem like a good idea, > > it'd be a bit crippled without them. > > > > That's not to mention the name collisions from the supporting "def" > > statements. > > > > All of the above could be written with different, or slightly > > altered names, but that seems like a bit of a kludge to me. > > Well, to start with we could skip most of that -- checks would have to > run as the current user/group, couldn't set environment, and would > have to be fully specified. That would at least be a reasonable > start, and would reduce all of the other requirements. > > I don't think we'll ever get user/group into the top-level checks, and > there's already work begun on a timeout metaparam. The environment is > the only sticky one, IMO. > > > > > On Thu, Oct 1, 2009 at 1:46 PM, Roy Nielsen <[email protected]> wrote: > > ok, this is going to take some thinking.. > > > > It also appears to depend on exec's: > > > > path > > user > > group > > timeout > > environment > > > > parameters. > > > > Regards, > > -Roy > > > > > > On Wed, Sep 30, 2009 at 5:43 PM, Luke Kanies <[email protected]> wrote: > > > > I don't think this will quite work -- you want to define a 'check' > > parameter type, like exec does, and then modify some of the core > > system to actually run those checks. This is currently done in the > > 'returns' parameter of exec, but it should probably be moved into the > > Type's 'evaluate' method or something similar. > > > > On Sep 30, 2009, at 9:42 AM, Roy Nielsen wrote: > > > > > Hello, > > > > > > Below is a patch to the 0.25.1 rc1 /lib/puppet/type.rb file with the > > > code for an "unless" metaparameter. > > > > > > Unfortunately, I haven't had time (or the resources) to test it yet. > > > > > > Regards, > > > -Roy > <snip - see earlier email> > > -- > Happiness is not achieved by the conscious pursuit of happiness; it is > generally the by-product of other activities. -- Aldous Huxley > --------------------------------------------------------------------- > 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 -~----------~----~----~----~------~----~------~--~---
