Jira (PUP-3689) Complex merging not working
Title: Message Title
Rene Last created an issue
Puppet / PUP-3689
Complex merging not working
Issue Type:
Bug
Affects Versions:
PUP 3.7.2
Assignee:
Kylo Ginsberg
Components:
Catalog Application
Created:
2014/11/23 3:26 AM
Environment:
PE 3.7
Priority:
Normal
Reporter:
Rene Last
Complex merging not working when puppet does a hiera_hash lookup.
hiera.yaml:
— :backends: yaml :yaml: :datadir: /etc/puppetlabs/puppet/hiera :hierarchy:
%
Unknown macro: {operatingsystem}
Jira (PUP-3689) Complex merging not working
Title: Message Title
Rene Last updated an issue
Puppet / PUP-3689
Complex merging not working
Change By:
Rene Last
Complexmergingnotworkingwhenpuppetdoesahiera_hashlookup.hiera.yaml:{quote}---:backends:yaml:yaml::datadir:/etc/puppetlabs/puppet/hiera:hierarchy:-%{operatingsystem}-common:merge_behavior:deeper{quote}common.yaml:{quote}logrotate::logrsyslog:log:'/var/log/syslog'options:-'rotate7'-'daily'-'missingok'-'ifempty'-'delaycompress'-'compress'{quote}Ubuntu.yaml:{quote}logrotate::log:rsyslog:postrotate:-'reloadrsyslog/dev/null21||true'{quote}AlookupthroughhieragivesbackwhatIwouldexpect.{quote}hiera-hlogrotate::logoperatingsystem=Ubuntu{rsyslog={ log=/var/log/syslog,options=[rotate7,daily,missingok,ifempty,delaycompress,compress],postrotate=[reloadrsyslog/dev/null21||true] }}InmycodeIusethehiera_hashfunctiontoperformthesamelookup.Wheniuseanotifytoshowthedatathathiera_hashgotIgetthefollowingresult:{quote}Notice:{rsyslog={postrotate=[reloadrsyslog/dev/null21||true]}}{quote}Nomergingseemstohavebedoneonthisdata.Ingeneralmergingseemstobeworkingonsimplestructureslikearraysjustnotonthesemorecomplexstructures.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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
Jira (PUP-3689) Complex merging not working
Title: Message Title
Rene Last updated an issue
Puppet / PUP-3689
Complex merging not working
Change By:
Rene Last
Complexmergingnotworkingwhenpuppetdoesahiera_hashlookup.hiera.yaml:{quote}---:backends:yaml:yaml::datadir:/etc/puppetlabs/puppet/hiera:hierarchy:-%{operatingsystem}-common:merge_behavior:deeper{quote}common.yaml:{quote}logrotate::logrsyslog:log:'/var/log/syslog'options:-'rotate7'-'daily'-'missingok'-'ifempty'-'delaycompress'-'compress'{quote}Ubuntu.yaml:{quote}logrotate::log:rsyslog:postrotate:-'reloadrsyslog/dev/null21||true'{quote}AlookupthroughhieragivesbackwhatIwouldexpect.{quote}hiera-hlogrotate::logoperatingsystem=Ubuntu{rsyslog= {log=/var/log/syslog,options= [rotate7,daily,missingok,ifempty,delaycompress,compress],postrotate=[reloadrsyslog/dev/null21||true]} }InmycodeIusethehiera_hashfunctiontoperformthesamelookup.Wheniuseanotifytoshowthedatathathiera_hashgotIgetthefollowingresult:{quote}Notice:{rsyslog={postrotate=[reloadrsyslog/dev/null21||true]}}{quote}Nomergingseemstohavebedoneonthisdata.Ingeneralmergingseemstobeworkingonsimplestructureslikearraysjustnotonthesemorecomplexstructures.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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
Jira (PUP-3689) Complex merging not working
Title: Message Title
Rene Last updated an issue
Puppet / PUP-3689
Complex merging not working
Change By:
Rene Last
Complexmergingnotworkingwhenpuppetdoesahiera_hashlookup.hiera.yaml:{quote}---:backends:yaml:yaml::datadir:/etc/puppetlabs/puppet/hiera:hierarchy:-%{operatingsystem}-common:merge_behavior:deeper{quote}common.yaml:{quote}logrotate::logrsyslog:log:'/var/log/syslog'options:-'rotate7'-'daily'-'missingok'-'ifempty'-'delaycompress'-'compress'{quote}Ubuntu.yaml:{quote}logrotate::log:rsyslog:postrotate:-'reloadrsyslog/dev/null21||true'{quote}AlookupthroughhieragivesbackwhatIwouldexpect.{quote}hiera-hlogrotate::logoperatingsystem=Ubuntu{rsyslog={log=/var/log/syslog,options=[rotate7,daily,missingok,ifempty,delaycompress,compress],postrotate=[reloadrsyslog/dev/null21||true]}} {quote} InmycodeIusethehiera_hashfunctiontoperformthesamelookup.Wheniuseanotifytoshowthedatathathiera_hashgotIgetthefollowingresult:{quote}Notice:{rsyslog={postrotate=[reloadrsyslog/dev/null21||true]}}{quote}Nomergingseemstohavebedoneonthisdata.Ingeneralmergingseemstobeworkingonsimplestructureslikearraysjustnotonthesemorecomplexstructures.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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
Jira (PUP-1640) Provide agnostic mechanism for Hiera Based Data in Modules
Title: Message Title Henrik Lindberg commented on PUP-1640 Re: Provide agnostic mechanism for Hiera Based Data in Modules I started on an implementation of what I first suggested, but I soon realized that the solution was still both hiera specific, and very specific to the particular way that the hiera data in modules module had to be implemented due to the way the resource implementation looks up the one and only hiera to get default data. Doing the implementation that way has several problems (cannot support directory environments well, and they are standard in Puppet 4.0.0), there are issues with file watching (not evicting caches for environments that come and go) etc. The implementation I came up with is agnostic, and it clearly separates the older API (left unchanged) with an extendable/plugin mechanism to lookup data in an environment, and in modules. A write up of this implementation is found here: https://docs.google.com/a/puppetlabs.com/document/d/1N5xnmhrC4v0EqXaxjneAzVjNvlAZA31O0y6KRLym7bE/edit# I believe that it should be possible to use this very simple API to implement a data provider for hiera both for environments and modules, but I realize that the hiera config manipulation API may still be needed due to hiera's singleton nature. It would be a positive thing to not have to do all that hiera patching - which may be possible since the new API differentiates between the global singleton hiera, a call to lookup for the environment, and a call to lookup in a module, and these providers can have their own lifecycle and associate caches with either the environment, or the compiler (depending on what is being cached). The work is available on branches as noted in the document - for people to play with and give feedback. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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
Jira (PUP-1417) puppet parser not order independent
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1417 puppet parser not order independent Change By: Henrik Lindberg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2088) Parser functions have arguments passed by reference rather than value
Title: Message Title Henrik Lindberg commented on PUP-2088 Re: Parser functions have arguments passed by reference rather than value 3x functions receive arguments that are copies because the new evaluator has to transform them to comply with the 3x behavior regarding undef and also because the 3x functions are not prepared to deal with certain data types used in the 4x API. It is proposed to add functions in the puppet language during 4x (PUP-2080) - they are completely safe wrt to immutability Writing functions in Ruby should be seen as a system level thing, and not mutating is is only one of the rules an implementor must abide by - there is plenty of opportunity to do many horrible things We freeze far more data (make the data itself immutable) in the upcoming 4.0.0, and we can do more. We cannot however completely freeze every piece of data that is passed around since the system itself needs certain mutating powers. Seems like we should be able to ensure that the evaluator only produces strings, hashes, arrays etc. that are immutable - there should never be any need to mutate those in functions - instead they should fail if they attempt to do so. It may be possible to enforce that values returned from functions are frozen as well Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are
Jira (PUP-3398) Warn when a string is implicitly converted to a number
Title: Message Title Henrik Lindberg commented on PUP-3398 Re: Warn when a string is implicitly converted to a number Closing this since we decided to drop the automatic string to numeric conversion in 3.7.x future parser and in puppet 4.0. This can still be a problem in the implementations of types and providers, but it is then not a general problem and has to be addressed per type/provider (such as enforcing that file mode is a String and not a Number - which is also standard behavior in 4.0.0). Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3690) puppet gives red warning about allow_virtual on every run
Title: Message Title Geoff Williams created an issue Puppet / PUP-3690 puppet gives red warning about allow_virtual on every run Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Kylo Ginsberg Components: Client Created: 2014/11/23 4:25 PM Environment: Puppet Labs Training VM 2.13 (Build 3f4da74) [root@master ~]# puppet --version 3.7.2 (Puppet Enterprise 3.7.0) Priority: Normal Reporter: Geoff Williams Current versions of puppet are giving scary red warning messages about allow_virtual being changed from false to true on every agent run: Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want
Jira (PUP-1467) DIE :undef, DIE!
Title: Message Title Henrik Lindberg commented on PUP-1467 Re: DIE :undef, DIE! Since 4x functions are all implemented with expecting nil and producing nil for undef, there should be no issues there. For 3x functions, there is a transformation, since they require a quirky transformation where all top level undef values / nils are required to be empty strings (if this is not done, too many 3x functions break) - thus, 3x functions get nil transformed to empty string at top level and 'verbatim' at all other levels in arrays and hashes (including :undef and even illegal data types since we are forced to maintain this backwards compatibility to reduce breakage. In general (what users should do): Move functions to the 4x function API, do never use :undef in ruby code unless interfacing with old logic, and then never ever return :undef in the data being produced. Take the opportunity to refactor and use the type system to get type checking. Move to EPP (from ERB) to get puppet semantics in templates, and if possible refactor to use EPP that only exposes a given set of parameters rather than accessing everything in scope. So, what is left to do for 4.0? I think we have not explored the potential issues around ERB templates fully and need to ensure we have tests covering nil/undef combinations. Later in the 4x series we should deprecate all 3x functions (or at least severely restrict them wrt. what they have access to, and what they are given and allowed to produce - at some point we have to get rid of the odd transformations like some nil/undef values must be empty strings. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this
Jira (PUP-3691) Windows - Support puppet URLs for package's source attribute
Title: Message Title Josh created an issue Puppet / PUP-3691 Windows - Support puppet URLs for package's source attribute Issue Type: New Feature Assignee: Josh Cooper Created: 2014/11/23 6:29 PM Environment: Windows Labels: Windows Priority: Normal Reporter: Josh Puppet currently doesn't supporting using a Puppet URL when setting the source attribute for a package resource. In order to install a package on Windows, it typically has to be downloaded as a file resource. This increases the amount of work required to define a package resource and introduces additional steps each time the package is updated (i.e. need to get rid of the old installers on the user's computer). While Puppet does support UNC paths, it is difficult to use in production environments since the path must be accessible as the user account running the Puppet service.
Jira (FACT-759) Can not get ec2 facter with non-root user on FreeBSD
Title: Message Title
thisisnoman created an issue
Facter / FACT-759
Can not get ec2 facter with non-root user on FreeBSD
Issue Type:
Bug
Affects Versions:
FACT 2.2.0
Assignee:
Eric Sorenson
Components:
PE
Created:
2014/11/23 6:35 PM
Environment:
FreeBSD 9.2 release
Labels:
support
Priority:
Critical
Reporter:
thisisnoman
I can get outputs running facter |grep aws with root but get nothing with non-root user:
root# facter |grep aws ec2_metadata = {security-groups=default, services= {domain=amazonaws.com}
, instance-type=t2.micro,...} ec2_public_hostname = . ec2_services_domain = amazonaws.com root#
Jira (FACT-759) Can not get ec2 facter with non-root user on FreeBSD
Title: Message Title
thisisnoman updated an issue
Facter / FACT-759
Can not get ec2 facter with non-root user on FreeBSD
Change By:
thisisnoman
Icangetoutputsrunningfacter|grepawswithrootbutgetnothingwithnon-rootuser:root#facter|grepawsec2_metadata={security-groups=default,services={domain=amazonaws.com},instance-type=t2.micro,...}ec2_public_hostname=.ec2_services_domain=amazonaws.comroot#non-root%facter|grepawsnon-root%sowhenIusethefacter'ec2_public_ipv4'inpuppet,it failstogetresult.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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-1077) Move Nagios types and supporting from core to a module
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1077 Move Nagios types and supporting from core to a module Change By: Kylo Ginsberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1077) Move Nagios types and supporting from core to a module
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-1077 Move Nagios types and supporting from core to a module Change By: Kylo Ginsberg Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
