Jira (PDB-1228) investigate a paging solution for multi-row responses
Title: Message Title Kenneth Barber commented on PDB-1228 Re: investigate a paging solution for multi-row responses The Jira API shows another example of how to deal with expansion, this example is for issue gets: https://docs.atlassian.com/jira/REST/latest/#d2e2619 Here it takes a parameter 'expand' which takes a list of fields that it will expand out into full json. It also has the use of 'self' keys which explain how to get at the data directly. 'fields' works like our projection operator. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4016) Consider short circuiting data binding if lookup is called as the default value
Title: Message Title Daniele Sluijters commented on PUP-4016 Re: Consider short circuiting data binding if lookup is called as the default value I'm not overly enthusiastic with the prospect of shoving function calls back into class parameters again. Wasn't that part of what we were trying to combat with data bindings? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4016) Consider short circuiting data binding if lookup is called as the default value
Title: Message Title Henrik Lindberg commented on PUP-4016 Re: Consider short circuiting data binding if lookup is called as the default value The alternative is to solve this on the data side - e.g. to add metadata for a key to specify its lookup behavior (merge strategy with parameters etc.). (I actually like that solution better - it does require new hiera backend implementations though). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3997) Audit and update puppet acceptance tests that assume the puppet user and group are present
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3997 Audit and update puppet acceptance tests that assume the puppet user and group are present Change By: Josh Cooper Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4018) Execute puppet AIO acceptance against puppetserver
Title: Message Title Josh Cooper created an issue Puppet / PUP-4018 Execute puppet AIO acceptance against puppetserver Issue Type: Task Assignee: Unassigned Created: 2015/02/16 8:05 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Josh Cooper AIO acceptance tests need to execute against JVM puppetserver. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4018) Execute puppet AIO acceptance against puppetserver
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4018 Execute puppet AIO acceptance against puppetserver Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4019) Add agent role back to the master
Title: Message Title Josh Cooper created an issue Puppet / PUP-4019 Add agent role back to the master Issue Type: Task Assignee: Unassigned Created: 2015/02/16 8:34 PM Fix Versions: PUP 4.0.0 Priority: Normal Reporter: Josh Cooper Two acceptance tests fail when the master has the agent role in the AIO pipeline running against the JVM puppetserver. I removed the agent role to workaround the issue for now. This ticket is to ensure the agent role is added back. Add Comment
Jira (PUP-4019) Add agent role back to the master
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4019 Add agent role back to the master Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-46) Hiera should support alternate environments
Title: Message Title Henrik Lindberg commented on HI-46 Re: Hiera should support alternate environments I agree that the current pattern of having an overall hierarchy that includes levels that refer to data directories inside of the current environment is an anti-pattern. (Even worse if it is looking in multiple environments). The new solution makes data in modules and environments self contained - it does not matter what is in the top level hierarchy, or even if it is used at all (well, you can always use it to override what is configured in any environment; which is possibly a good feature for patching and mocking in a test environment, but use should be kept to a minimum). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4017) Make parser an environment specific setting
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4017 Make parser an environment specific setting Change By: Henrik Lindberg Sprint: Language2015-02-18 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-4017) Make parser an environment specific setting
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4017 Make parser an environment specific setting Issue Type: New Feature Assignee: Unassigned Components: DSL Created: 2015/02/16 5:48 AM Fix Versions: PUP 3.7.5 Priority: Normal Reporter: Henrik Lindberg To help people migrating to 4.0.0 it is of value to be able to run the master in such a way that only certain environments use the setting parser=future. The way it works now is to switch the entire master. This may be as simple as just making the setting environment specific with a default value taken from the main section parser. However, there may be behavior that is conditional on Puppet[parser] that is sticky and the first task is to review those conditionals to ensure we do not have such sticky behavior. Note, that when merging this up to master, the construct needs to be reverted since the parser setting is then removed.
Jira (PUP-4008) Inferred type of empty hash not assignable to HashString,String
Title: Message Title Henrik Lindberg commented on PUP-4008 Re: Inferred type of empty hash not assignable to HashString,String merged to stable at 0dd8797433ee64e58ab6ef2fc79575be7477f7da merged to master at 0b0c2efdf951e5593bfbe7f7099ccf5e7ec3ba17 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Thomas Hallgren commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data It's perhaps best to solve it in this ticket since the implementation is new and not yet finalized. I suggest the following: Remove the 'accept_undef' flag. Instead, rely on the caller to provide a value_type that will allow or disallow undef as needed Let Data Binder and the data providers raise a specific KeyNotFoundError when no match is found for the given key and return undef for a key with undef value Change the lookup logic so that it rescues and remembers such errors and treat undef obtained without errors as any other value Only consult defaults (default_values_hash, default_value, or code block) when all attempts to find a match ended in error and let lookup raise an error when no default alternative is provided Worth noting: The dispatch needs to change so that it can be determined whether or not a default was provided (by using different dispatch methods) since undef becomes a valid value (i.e. we can't use default_value=nil in a Ruby parameter declaration). It will be legal for a code block to return undef since it is a valid default value. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (FACT-824) Reduce calls to 'ip link show' in Facter::Util::IP
Title: Message Title Arthur Holstvoogd created an issue Facter / FACT-824 Reduce calls to 'ip link show' in Facter::Util::IP Issue Type: Improvement Affects Versions: FACT 1.7.4 Assignee: Arthur Holstvoogd Created: 2015/02/16 12:23 AM Environment: Linux (Debian 7.8 Wheezy) Priority: Normal Reporter: Arthur Holstvoogd Facter::Util:IP.get_interface_value calls get_bonding_interface for every possible value. However the result is only used for macaddress lookups. Since get_bonding_interface makes a call to `ip link show` this can become a performance issue if many interfaces are present. Already affects facter 1.5.3. Add Comment
Jira (FACT-824) Reduce calls to 'ip link show' in Facter::Util::IP
Title: Message Title Arthur Holstvoogd commented on FACT-824 Re: Reduce calls to 'ip link show' in Facter::Util::IP I'll make a pull request to improve this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Henrik Lindberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data If we are changing APIs, then we can throw an exception (cheaper as it does not populate a stack trace) - this is how this is done for non existing variables in the current Scope implementation. Or, we could perhaps pass around a block to be called on 'not found' (not sure how great that is in a composition of providers/backends). For the new scope implementation I changed that to pass around a codeblock to be called in case of 'not found', it is supposed to either return nil or raise an error. Have not yet measured if this is more expensive than catching exception or error. The main intent for this impl was to simplify different kinds of lookup / check for existence - i.e. I want the value if it exists (possibly nil), otherwise something else that earlier required two stack lookups Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-46) Hiera should support alternate environments
Title: Message Title David Chute commented on HI-46 Re: Hiera should support alternate environments Yes, I think you have got my point. So IMO this 'feature' is a trap. We should be asking why people want this feature and addressing that in a better way. This is a feature asking for a shared component between multiple environments. That component is (at the very least) the part that does the environment switching (as you put it, the routing logic). How will you test an update to that switch/data-routing-logic when it is part of both your dev and your live infrastructure? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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.
