Peter Tribble wrote: > On Mon, Aug 17, 2009 at 11:17 PM, Ethan Quach<ethan.quach at sun.com> wrote: > >> Jon Aimone wrote: >> >>> Hi, >>> >>> So everyone in my group who currently adds manifests custom to a specific >>> machine (of which we have several hundred) will have to export the entire >>> service configuration (which includes every machine), modify it (only the >>> part that applies to their machine), and import again? Seem dangerous and >>> not very practical. >>> >> No, I think the suggestion here is for a different use case >> where the entire wad of all criteria for a service is spit out >> and then sucked back in as a single mass file. >> > > That's the one. > > I did think about suggesting all the other commands be removed, but a > moment's thought brought me back to the scenario Jon described. > > I was just suggesting that the way to think of the other subcommands > was that they just edited a subsection of the big blob. At least, I found > it a useful way of thinking about the problem. > > (In practice, while I might edit the wad directly [never underestimate > the power of a text editor as a systems administration tool] it's more > likely that this would be automated. Or maybe even simply exported > from a CMDB system.) >
I was thinking this functionality to be more useful in cases where we're duplicating a service (where this functionality would then be used internally really), or perhaps saving off the criteria configuration for whatever reason. For the one-off mod or addition of a criteria, why the preference for this style rather than the interfaces Sundar has proposed? thanks, -ethan
