Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Sean Griffin QA Risk Assessment: Low QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Sean Griffin Attachment: init_manifest Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Sean Griffin Status: Ready for CI Test Assignee: Sean Griffin qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin assigned an issue to Unassigned Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg assigned an issue to Unassigned merged to stable at: 08fc9a5 Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Henrik Lindberg Release Notes Summary: The lookup command always compiled the entire catalog before performing the actual lookup of the given key. While correct, it can potentially be very time consuming, and produce unwanted logging. Since a full compilation is typically a special case (normally values does no interpolate arbitrary global puppet variables). A full compilation is now available for those that have data that is configured with interpolation of arbitrary (non fact/ENC variables) by using the flag --compile. Without this flag the command uses an empty catalog Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Sean Griffin Assignee: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Ok, good to know. Then it is fine. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output From a user perspective, I don't think it is confusing and technically loading and evaluating functions for a data provider is not compilation per se (it is loading, parsing, validation, evaluation). This, since "compilation" means "to compile a catalog" in puppet terminology. And from a user perspective; a catalog with a class noop (or some other empty construct we may even manage with completely empty input), is essentially the same as not compiling a catalog. It only happens that we technically choose to implement it as a compilation. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output The submitted PR adds the --compile option. As long as it stays there and we don't also add a --no-compile then I think it's clear enough. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output I think binary flag arguments automatically gets the no option. I don't care if it is available or not; we do not want to add it explicitly, but it does no harm if we get it automatically. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output The no option is only added for binary settings. It's not added for options for a specific application. For instance, there's no --no-debug or --no-verbose. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Another idea would be to make -manifest mutually exclusive to using -evaluate . Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Not sure what apply does there - it should work the same way; with apply using a path to a file and puppet code on the command line is mutually exclusive, but I think it still honors manifest, and possibly also code - but I am not sure. This command should work the same way, or it will be confusing. It is also separate from the issue if you want any manifest code at all to be evaluated or not. (Naturally, if you state that "hey, no evaluation please" and specifying manually that code should be evaluated (with --manifest, or --execute/--evaluate or --code or whatever) at the same time then that is an error since you asked for something that does not make sense (giving more specific values to what you are also saying should be ignored)). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Puppet apply treats the non-option argument as the manifest file name. There can only be one. Puppet lookup treats such arguments as the keys to lookup. So it's not possible to make them work the same way. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output So, you don't think it's valuable to be able to run a lookup "exactly as things are configured" ? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Jo Rhett a problem in the past with the hiera command line is that it does not do it quite the same way as lookups are made when compiling a catalog - this meant users had to use puppet apply and write a notify with a call to hira to see the actual real result. The results are different as real code can define things that affects the lookup - naturally that option needs to be available. Most do however not rely on that, and the execution of lookup command line will be speeded up by not loading and evaluating everything (all of the time). We have that figured out, it is many a question of UX regarding the command line options. I don't think we need to come up with a new special way of doing the actual searches for values - that is complex, and already implemented. What we are talking about is just compile or not, and what the flags should be. I think it is as simple as having one flag that turns on "full catalog" and that the rest is controlled with the settings and options already available in puppet. I can imagine calling this flag --compile and the default being --no-compile. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Well, it really does not have to do all the various things apply can do. You have an option to set variables that is probably what you want to do ayway. If you want something else, you can always use the --manifest setting to point to a file of your choice, or set -- code. I think that is good enough. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Jo Rhett commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output While I personally would enjoy flexibility, I believe that most users tend to assume "with the same config I'm already using" unless overridden. Some of the less intuitive parts of Puppet were due to things that made no assumptions, which is good for the coder but confusing for the user. I think the expected and reasonable response is for puppet lookup this.that to use exactly the same context that "puppet agent" or "puppet apply noop.pp" would have with no other options. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Well, puppet agent will run manifests/site.pp and puppet apply noop.pp will run noop.pp. The former might contain a whole slew of things. So which one would you consider to be best when lookup runs without options? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Jo Rhett, yes of course. All files under manifests. The reason we care about code in general is that Hiera interpolation can use scope variables. Any code can declare global variables in the top scope and may hence impact a lookup, both values and the actual lookup configuration. Henrik Lindberg, I like keeping it simple, but isn't ---no-compile a bit confusing. I think we will still compile things like function data providers. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Thomas Hallgren Scope Change Category: Found Affects Version/s: PUP 4.3.0 Affects Version/s: PUP 4.3.1 Scope Change Reason: Design flaw. Must be resolved A.S.A.P. Story Points: 1 Sprint: Language 2016-01-13 Scrum Team: Language Fix Version/s: PUP 4.3.2 Add Comment
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title
Thomas Hallgren commented on PUP-5461
Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
I think a user will find it rather surprising that a lookup invocation actually evaluates the catalog. I therefore suggest that we change this and make the default evaluation evaluate something that is harmless and silent like:
class noop{}
We could then equip the lookup command with an additional option to enforce the normal default evaluation such as --evaluate to make it perform the default evaluation (i.e. site.pp).
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title
Henrik Lindberg commented on PUP-5461
Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
I agree with Thomas (only evaluating something like class noop {}, and also avoiding calls that populates the catalog with classes to include from an ENC etc. I think that is a default that suits most users.
I think it would be better to say something other that default to get "no evaluation" since the word "default" is ambiguous, is it the default production env, the default manifest (site.pp) or something else? The flags should also correspond to what is already in use for other puppet commands (i.e
e/evaluat is for evaluating what is given on the command line,
-manifest is for referencing the site.pp/manifest to evaluate etc. Have no immediate suggestion on name of flag though.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Jo Rhett commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Actually agent defaults to --manifestdir manifests/ now doesn't it? (probably due to ignorance) I'm having trouble imagining why we'd care about code that isn't a data provider. So I think that would mean: 1. Read the global data (Hiera v3) for the lookup key 2. Read the environment.conf for an environment_data_source. Look for key if available. 3. Identify the classes to run, check each module for a data_provider and query that. Hm. Seems like a lot of work. Why not just grab the looked up values from the last catalog stored? tricky tricky stuff. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Thomas Hallgren commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output The term "default" was chosen to mean whatever puppet would normally evaluate. The exact meaning must be specified in the config. We could use a term like 'as_configured' but I personally like 'default' better. I think there are four cases: Don't evaluate anything (use the noop class). Evaluate whatever Puppet is configured to evaluate (what I call --evaluate default) Provide a script string to --evaluate
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Remember that --manifest is a setting, so it is always set to something, and that makes it confusing since --evaluate default would use that file - so you would need to set both if you wanted a specific file (I guess it can be gleaned if it is given on the command line, (but I think there is some magic involved that drops settings from args at one point, or if you grab them, that you take over the responsibility)). It is more a question of "fast" vs. "full" (catalog), where you can control the "full" catalog with manifest or execute or code settings. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Jo Rhett commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output This catalog production seems to have another effect. On non-server nodes, it creates a new SSL CA directory and populates it with a new key in the local node's name. See PUP-5644 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Henrik Lindberg commented on PUP-5461 Re: puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Uncertain what the best way of handling this is. I can imagine: setting a log-level so that only warnings and errors appear (not info logging) redirecting logs Setting log level as an application default may be a simple way to get around the problem. A user that wants more can then simply change that on the command line (as well as redirecting the logs). It is worth an experiment, and if that works and produces a reasonable result then I would like this in the 4.3.0 release. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5461) puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output
Title: Message Title Sean Griffin created an issue Puppet / PUP-5461 puppet lookup command too verbose: implied application of manifest (site.pp by default) and all its output Issue Type: Bug Assignee: Unassigned Created: 2015/10/30 9:15 AM Priority: Normal Reporter: Sean Griffin 'puppet lookup symbol' is supposed to return the value of symbol as discovered by the lookup() function. There is an implied application of a manifest (production environment, site.pp by default). If these manifests generate output, then that becomes part of the output of the puppet lookup command. Here is an example using branch=master, sha = ef9569c59088b85ad8476695a24d479be0dfb376 [root@lmrgtt9kjyg5esn manifests]# puppet --version 4.3.0 [root@lmrgtt9kjyg5esn manifests]# pwd
