Jira (PUP-5548) Debian provider fails on Debian 8 systems without systemd present
Title: Message Title William Hopper created an issue Puppet / PUP-5548 Debian provider fails on Debian 8 systems without systemd present Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/11/25 8:49 AM Environment: Debian 8 / Ubuntu 15.04 where systemd has been removed or is otherwise not present. Priority: Normal Reporter: William Hopper https://github.com/puppetlabs/puppet/commit/75160b78dc4a9189949da50a6b76e42172a45770#commitcomment-14619787 added a bit of logic in the Debian provider for Debian 8 / Ubuntu 15.04 and newer systems to use systemctl to properly determine service status. However, it's possible to remove systemd from a Debian 8 system all together and run entirely with sysvinit. In such a case, the provider will fail as systemctl doesn't exist. The provider should check that systemctl exists before attempting to use it in Debian 8 / Ubuntu 15.04.
Jira (HI-482) String literals should literally be literal
Title: Message Title Lee Lowder commented on HI-482 Re: String literals should literally be literal I really feel that closing this is the wrong thing to do, especially since the reason seems to be "this is hard, so no." 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-5547) Environment is evicted many times during compile
Title: Message Title Kylo Ginsberg commented on PUP-5547 Re: Environment is evicted many times during compile I wonder if we should elevate these two messages from Debug to Info: Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) My thought is that most people don't run with debug, so wouldn't have seen these messages. If they're running at Info, they would have seen a slew of Evicting/Caching message pairs and we might have got word of this issue earlier. 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-5547) Environment is evicted many times during compile
Title: Message Title Thomas Hallgren commented on PUP-5547 Re: Environment is evicted many times during compile This issue can be tested by running a puppet lookup with --debug on an environment that has a class with a variable that resolves parameters from Hiera. The environment_timeout must either be absent or set to 0. Without this fix, the debug output will show repeated messages like: Debug: Evicting cache entry for environment 'production' Debug: Caching environment 'production' (ttl = 0 sec) Debug: Performing a hiera indirector lookup ... When the fix is applied, the same output becomes: Debug: Performing a hiera indirector lookup ... Add Comment
Jira (HI-482) String literals should literally be literal
Title: Message Title Kyle Harper commented on HI-482 Re: String literals should literally be literal I understand that YAML and JSON don't treat double or single quotes differently; it's all up to hiera as to how the backend data is being interpreted. It's hiera that chose to look at single-quoted strings as interpretative. A common practice with Puppet features that break current conventions is: create a config option, leave the option default set to the current behavior, and monitor feedback and adoption rates. If the argument was that it would be very time consuming and you don't have resources for it, that's one thing. Otherwise, with all due respect, I feel this should get consideration from more than a single person before being shut down because of potential "incompatibilities" that can be completely avoided with a new option in hiera.yaml. A string-literal form is a very basic tenant of interpretive systems, including Puppet DSL. 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-5547) Environment is evicted many times during compile
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-5547 Environment is evicted many times during compile Issue Type: Bug Assignee: Thomas Hallgren Created: 2015/11/25 7:31 AM Fix Versions: PUP 4.3.2 Priority: Normal Reporter: Thomas Hallgren The environment might be evicted a large number of times during a compile. The reason for this is that the call to the data binding indirection passes the environment in string form rather than the instance which forces a lookup in Environments which in turn evicts an existing environment if environment_timeout = 0. That setting happens to be the default. Add Comment
Jira (PUP-5491) The "client_data" Directory Permissions Incorrect After Installation
Title: Message Title Ethan Brown commented on PUP-5491 Re: The "client_data" Directory Permissions Incorrect After Installation Attached the diagram that we put together of mapping out the runs / perms (for catalog directory). The most interesting scenarios play out when Puppet is installed as a manual service, and the first run is started as Administrator, then the subsequent run is as SYSTEM. With --trace --debug --verbose on, we can see changes being made as the settings catalog is applied, typically in an order like this: Debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/public_keys/vagrant-2008r2.corp.puppetlabs.net.pem]/mode: mode changed '0640' to '0644' Debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/ca.pem]/mode: mode changed '0640' to '0644' Debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/certs/vagrant-2008r2.corp.puppetlabs.net.pem]/mode: mode changed '0640' to '0644' Debug: /File[C:/ProgramData/PuppetLabs/puppet/etc/ssl/crl.pem]/mode: mode changed '0660' to '0644' Debug: /File[C:/ProgramData/PuppetLabs/puppet/cache/state/last_run_report.yaml]/mode: mode changed '0660' to '0640' Debug:
Jira (PUP-5550) linter should print warning for code that will result in logging or backups of secrets
Title: Message Title Jesse Endahl created an issue Puppet / PUP-5550 linter should print warning for code that will result in logging or backups of secrets Issue Type: Improvement Assignee: Unassigned Created: 2015/11/25 2:38 PM Priority: Normal Reporter: Jesse Endahl It would be great if `puppet lint` could print a warning anytime it sees a puppet file resource that references a file containing what is likely to be a secret. If a hit was found, the warning could look something like this: ``` WARNING: Potentially insecure use of file resource. String `BEGIN PRIVATE KEY` found in file referenced by your file resource at line 20. Your current Puppet code will result in logging and backups of this file whenever its contents are updated by Puppet. To prevent contents of this file from being written to log files, add the following line to the file resource: show_diff => false, To prevent filebucketing of this file, add the following line to the file resource: backup => false, ``` The linter would accomplish this by parsing the contents of files referenced by file resources and checking for various headers associated with secrets. For a start, looking for the string `BEGIN PRIVATE KEY` would catch both SSL and SSH private keys.
Jira (PUP-5538) Puppet fails to convert Windows Unicode group or user names to sids
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5538 Puppet fails to convert Windows Unicode group or user names to sids Change By: Ethan Brown Sprint: Windows 2015-12-16 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-5538) Puppet fails to convert Windows Unicode group or user names to sids
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5538 Puppet fails to convert Windows Unicode group or user names to sids Change By: Ethan Brown Fix Version/s: PUP 4.3.2 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-5538) Puppet fails to convert Windows Unicode group or user names to sids
Title: Message Title Larissa Lane updated an issue Puppet / PUP-5538 Puppet fails to convert Windows Unicode group or user names to sids Change By: Larissa Lane Labels: encoding i18n windows 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-5551) Unable to Install Puppet Agent on x86_64
Title: Message Title Thomas Lowry created an issue Puppet / PUP-5551 Unable to Install Puppet Agent on x86_64 Issue Type: Bug Affects Versions: PUP 3.8.4 Assignee: Unassigned Created: 2015/11/25 4:05 PM Environment: CentOS 6.6 (Final) Priority: Normal Reporter: Thomas Lowry Hello, I am unable to install the Puppet Agent on our server due to an discrepancy using yum to install it. Below is the commands used: yum install puppet.noarch When we install we are receiving this from the Transaction Check Error: package libselinux-2.0.94-5.8.el6.x86_64 (which is newer than libselinux-2.0.94-5.3.el6_4.1.i686) is already installed We have tried using the --setopt=protected_multilib=false option, however we still get the same error.
Jira (PUP-5491) The "client_data" Directory Permissions Incorrect After Installation
Title: Message Title Ethan Brown commented on PUP-5491 Re: The "client_data" Directory Permissions Incorrect After Installation So in an effort to test a different permissions issue, I stripped off all access rights to a file, aside from Administrators: (R), and attempted to read it as SYSTEM. What I found is that SYSTEM can read the file. I found a reference in Mechanics of User Identification and Authentication that explains this. SYSTEM is an implicit / hidden member of the Administrators group, which can be verified by opening a psexec session as SYSTEM and running whoami /groups in it: C:\Users\Administrator\Downloads> psexec -s cmd.exe PsExec v2.11 - Execute processes remotely Copyright (C) 2001-2014 Mark Russinovich Sysinternals - www.sysinternals.com Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Jira (HI-482) String literals should literally be literal
Title: Message Title
R.I.Pienaar commented on HI-482
Re: String literals should literally be literal
"it's all up to hiera as to how the backend data is being interpreted"
It's not really, hiera does YAML.parse("foo.yaml") and gets already parsed data back. It has literally no idea and no possibility of an idea without writing its own YAML parser if the string was single/double quoted. And that yaml parser would then not be portable meaning your data files become hiera data files and not yaml.
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-5482) Should a not found type be marked as such?
Title: Message Title Michael Smith commented on PUP-5482 Re: Should a not found type be marked as such? What other things are cached in the environment cache and would behave similarly? Is there a good place to look for a list? 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-5550) linter should print warning for code that will result in logging or backups of secrets
Title: Message Title
Jesse Endahl updated an issue
Puppet / PUP-5550
linter should print warning for code that will result in logging or backups of secrets
Change By:
Jesse Endahl
It would be great if `puppet lint` could print a warning anytime it sees a puppet file resource that references a file containing what is likely to be a secret. If a hit was found, the warning could look something like this: ``` {{ WARNING: Potentially insecure use of file resource. String `BEGIN PRIVATE KEY` found in file referenced by your file resource at line 20. Your current Puppet code will result in logging and backups of this file whenever its contents are updated by Puppet.To prevent contents of this file from being written to log files, add the following line to the file resource:show_diff => false,To prevent filebucketing of this file, add the following line to the file resource:backup=> false, }} ``` The linter would accomplish this by parsing the contents of files referenced by file resources and checking for various headers associated with secrets. For a start, looking for the string `BEGIN PRIVATE KEY` would catch both SSL and SSH private keys.
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.
Jira (PUP-5550) linter should print warning for code that will result in logging or backups of secrets
Title: Message Title
Jesse Endahl updated an issue
Puppet / PUP-5550
linter should print warning for code that will result in logging or backups of secrets
Change By:
Jesse Endahl
It would be great if `puppet lint` could print a warning anytime it sees a puppet file resource that references a file containing what is likely to be a secret. If a hit was found, the warning could look something like this:{ { quote} WARNING: Potentially insecure use of file resource. String `BEGIN PRIVATE KEY` found in file referenced by your file resource at line 20. Your current Puppet code will result in logging and backups of this file whenever its contents are updated by Puppet.To prevent contents of this file from being written to log files, add the following line to the file resource:show_diff => false,To prevent filebucketing of this file, add the following line to the file resource:backup=> false, {quote } } The linter would accomplish this by parsing the contents of files referenced by file resources and checking for various headers associated with secrets. For a start, looking for the string `BEGIN PRIVATE KEY` would catch both SSL and SSH private keys.
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
Jira (PUP-5060) Add support for --facts in 'puppet lookup' command
Title: Message Title Hailee Kenney commented on PUP-5060 Re: Add support for --facts in 'puppet lookup' command Pull request that fixes the bug: https://github.com/puppetlabs/puppet/pull/4467 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-5520) Exclude sendsigs from service init provider
Title: Message Title Rick Sherman commented on PUP-5520 Re: Exclude sendsigs from service init provider Initial testing of Cisco fix not working fully on our VM. Investigating. 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 (HI-482) String literals should literally be literal
Title: Message Title
Ben Ford commented on HI-482
Re: String literals should literally be literal
Would double quoting be an acceptable compromise?
---
message: "'this string gets returned exactly, including the single quotes around it.'"
irb(main):001:0> require 'yaml'
=> true
irb(main):002:0> p YAML.load(File.read('foo.yaml'))
{"message"=>"'this string gets returned exactly, including the single quotes around it.'"}
I'm not sure that's a reasonable solution either, because the ' and the " blend into one another so easily. But it could work.
Add Comment
Jira (HI-148) Support multiple backends of the same type
Title: Message Title Joseph Yaworski commented on HI-148 Re: Support multiple backends of the same type I have another solution that's different from the others here, so I'll just chime in. I have an r10k postrun script that symlinks YAML files on the puppetserver into the environment's hieradata directory after each deploy. 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-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title William Hopper updated an issue Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: William Hopper Story Points: 2 Sprint: Client Triage Scrum Team: Client Platform 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-5520) Exclude sendsigs from service init provider
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5520 Exclude sendsigs from service init provider Change By: Kenn Hussey Sprint: RE 2015-11-25 , RE 2015-12-02 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 (PDB-2211) refine our strategy around uuid/bytea columns
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2211 refine our strategy around uuid/bytea columns Issue Type: Improvement Assignee: Unassigned Created: 2015/11/25 10:41 AM Priority: Normal Reporter: Wyatt Alt We currently use _expression_ indexes on our uuid/hash columns to make queries fast, because we realized shortly before 3.2.2 that we were issuing queries against columns cast to text, which prevented the indexes from being used. _expression_ indexes were a quick fix without much migration overhead, but long term we should get this buttoned down so that we're using consistent types internally (preferably bytea/uuid, but varchar works too). This probably means either extending clojure.jdbc to do the type coercion on result sets, or adding some munging in the query namespaces to handle the byte arrays there. Add Comment
Jira (PUP-5549) package version behavior for epoch versioned rpm's in centos is broken.
Title: Message Title Josh Behrends created an issue Puppet / PUP-5549 package version behavior for epoch versioned rpm's in centos is broken. Issue Type: Bug Affects Versions: PUP 4.3.0 Assignee: Unassigned Created: 2015/11/25 10:41 AM Priority: Normal Reporter: Josh Behrends puppet-agent 1.3.0 CentOS 7 I just upgraded from puppet-agent 1.2.4 and all of a sudden I have multiple packages throwing the following notice every single puppet run: Notice: /Stage[main]/Logstash::Package/Logstash::Package::Install[logstash]/Package[logstash]/ensure: ensure changed '1:1.5.5-1' to '1.5.5-1' I'm not 100% positive, but it looks as though this change made be the culprit: https://tickets.puppetlabs.com/browse/PUP-5025 I tried adding the epoch to the begging of the version given to puppet and I get this:
Jira (HI-482) String literals should literally be literal
Title: Message Title
Kyle Harper commented on HI-482
Re: String literals should literally be literal
R.I.Pienaar Thanks for the demonstration.
Henrik Lindberg I see what you're saying now, and why hiera can't do what I was originally thinking.
It might be worth linking this issue on certain documentation pages which discuss Hiera. There's already a note that values must be quoted, and I know some recent updates helped cover the RewriteRule issue by using % {literal('%')}
, but it would help edify others to note:
1. Hiera doesn't parse YAML or JSON, ruby does. Therefore Hiera is subject to whatever ruby returns. (Show the example above from R.I.Pienaar). 2. Hiera's interpretations purposely remain simple, only interpreting %{} blocks.
Anyway, thanks for all the feedback.
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 (HI-148) Support multiple backends of the same type
Title: Message Title
Jason Kohles commented on HI-148
Re: Support multiple backends of the same type
FYI, the way I work around this is to clone each of the repos that needs to contribute configuration into the same directory, then prefix the hierarchy to make it work..
{{--- :backends: [ yaml ] :hierarchy:
"hieradata/hosts/%{::hostname}"
"hieradata/roles/%{::role}"
"hieradata/environments/%{::environment}"
"hieradata/networks/%{::network}"
"hieradata/virtual/%{::is_virtual}"
"hieradata/virtual/%{::virtual}"
"hieradata/common"
"global-hieradata/roles/%{::role}"
"global-hieradata/environments/%{::environment}"
"global-hieradata/networks/%{::network}"
"global-hieradata/virtual/%{::is_virtual}"
"global-hieradata/virtual/%{::virtual}"
"global-hieradata/common" :yaml: :datadir: /etc/configuration }}
Add Comment
Jira (PUP-3149) Removing packages on Suse should use zypper not rpm
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-3149 Removing packages on Suse should use zypper not rpm Change By: William Hopper Assignee: William Hopper 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 (HI-482) String literals should literally be literal
Title: Message Title Henrik Lindberg commented on HI-482 Re: String literals should literally be literal I should have given this some more thought before closing. I was so focused on the notion of double/single quoted string in the data format that I did not think about how to actually solve the problem. In fact, since we just introduced lookup_options in puppet's lookup function, and for automatic data binding. The lookup_options could be expanded to allow mapping if a string should be verbatim or not. That would also work with existing providers. See ticket(s) for lookup_options. If you like that idea, we can change this ticket into providing support for a "verbatim" option. (Ping R.I.Pienaar Kyle Harper). 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 (HI-482) String literals should literally be literal
Title: Message Title Henrik Lindberg commented on HI-482 Re: String literals should literally be literal sure - it should be able to have the entire string as an argument to `literal`. I know there are other problems in hiera with rules that have problems seeing multiple '%'. The new implementation in "data in modules" does not have that problem (afaik). That way you can have both verbatim/literal and interpolation in the same string. 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-5547) Environment is evicted many times during compile
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5547 Environment is evicted many times during compile Change By: Thomas Hallgren Fix Version/s: PUP 3.8.5 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-5547) Environment is evicted many times during compile
Title: Message Title Kylo Ginsberg commented on PUP-5547 Re: Environment is evicted many times during compile /cc Christopher Price and Nick Walker, since you've both been attending to compile performance issues. This one only applies if environment_timeout is 0, but in that scenario it could be a contributor to performance woes. How much so would likely depend on site-specifics, e.g. how much hiera lookup is used, etc. 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 (HI-482) String literals should literally be literal
Title: Message Title
R.I.Pienaar commented on HI-482
Re: String literals should literally be literal
Henrik Lindberg that's an interesting option but I do not know if it's really something you want to set on the key?
One common use case for the literal() function I see from people is that they want to for example set some piece of data that usually is fine but in one case there's a %{} in the particular piece of data they want to avoid parsing - sometimes even just on one specific piece of data rather than all data for a key.
Not saying it wouldnt be a good option - just not sure if it will address the common problem I've seen, perhaps others can throw in some more use cases they'd see for this ability?
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 (HI-469) Can't escape twice in a single hierarchy level
Title: Message Title Joseph Yaworski commented on HI-469 Re: Can't escape twice in a single hierarchy level I can also confirm that the workaround does work. 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-5285) Systemd service provider only handles .service units, when others can be useful
Title: Message Title Kylo Ginsberg commented on PUP-5285 Re: Systemd service provider only handles .service units, when others can be useful Forgot about this earlier PUP-1732 issue (even though I submitted and PR'd it, gulp), but thank you William Hopper for pointing this out. 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-5491) The "client_data" Directory Permissions Incorrect After Installation
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5491 The "client_data" Directory Permissions Incorrect After Installation Change By: Ethan Brown Attachment: PUP-5491 Permissions Notes.jpg 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-5482) Should a not found type be marked as such?
Title: Message Title
Henrik Lindberg commented on PUP-5482
Re: Should a not found type be marked as such?
The environment cache contains all loaded (used) types, and all used functions. One way to see this is to set an environment timeout that is long - say 5 minutes. Have a .pp function
function foo { notice "foo" }
Do an apply, change the function, "changed foo". See that the older version is still cached. Se that the not found type (that this ticket fixes) does not require stats. Then wait until the timeout. The function now outputs the changed value, and there is a stat for the not found entry. (or something like that).
Hope that helps.
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 (HI-482) String literals should literally be literal
Title: Message Title
R.I.Pienaar commented on HI-482
Re: String literals should literally be literal
A small example:
>> p YAML.load("foo: 'bar'");p YAML.load('foo: "bar"')
{"foo"=>"bar"}
{"foo"=>"bar"}
In both cases - single or double quotes - hiera just get a ruby data structure back. It has no insight into where that data come from or how the data file looked. Data files are YAML standard compliant, this is just how it is.
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
Jira (HI-482) String literals should literally be literal
Title: Message Title Henrik Lindberg commented on HI-482 Re: String literals should literally be literal I know for a fact that it is impossible to differentiate one kind of string from another. So it is much harder than just "hard" since it is neither hiera nor puppet that is transforming the YAML or JSON into objects. When hiera gets hold of them they are just strings. What is left is only syntax in the actual strings. Hiera currently squats on everything in terms of syntax and data types - so yeah, this is impossible without causing incompatible breakage. We would need to create a custom YAML or JSON parser in order to treat single or double quoted string differently. Alternatively encode the data differently by adding a top data file scope that is for instructions instead of keys (to allow some keys to be uninterpreted). The later can be achieved by implementing a custom backend - say by having data under they keys "verbatim:" and "processed" (or somesuch). 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 (HI-483) Allow compatibility mode of deep_merge
Title: Message Title Henrik Lindberg commented on HI-483 Re: Allow compatibility mode of deep_merge This needs to be reverted - the "compat" modes should not be exposed in the API. Here is the revert PR: https://github.com/puppetlabs/hiera/pull/325 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-5482) Should a not found type be marked as such?
Title: Message Title Henrik Lindberg commented on PUP-5482 Re: Should a not found type be marked as such? Note that the information is cached with the environment. If a "not found" is cached, an added type should be found when the environment cache times out, and not before that. 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-5482) Should a not found type be marked as such?
Title: Message Title Nacho Barrientos commented on PUP-5482 Re: Should a not found type be marked as such? +1 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 (HI-482) String literals should literally be literal
Title: Message Title Henrik Lindberg commented on HI-482 Re: String literals should literally be literal There are no difference between single quoted and double quoted strings in YAML and JSON. There is no simple solution to this problem since the "programming language" here is a data format and any changes to hiera interpretation of data is sensitive and will have incompatibilities that would silently just deliver different data to users. I am therefore closing this as a "won't 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-483) Allow compatibility mode of deep_merge
Title: Message Title Henrik Lindberg commented on HI-483 Re: Allow compatibility mode of deep_merge Revert merged. Please change or create a new PR with a solution that does not alter the API. This could be done by checking if the compat methods are available and then use them instead of the regular. That is if i have correctly understood how it is supposed to work (that you can call the compat versions and get the same behavior as you normally would if Rails had not blocked the options in the regular calls. Also note that for use with Puppet, the fix in hiera is not enough. Puppet now comes bundled with the deep merge gem, and it is used not only in the hiera project, but also by the hiera 4 implementation in puppet itself, and in the "data in modules" implementation. 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.
