Jira (PUP-11868) New default strict=error breaks all deprecation warnings
Title: Message Title Daniel Parks commented on PUP-11868 Re: New default strict=error breaks all deprecation warnings Also, this isn’t just a big problem for module authors who deprecate a function, it’s also a big problem for anybody who uses that module. Module writers will have to choose between supporting stdlib < 9 and Puppet ≥ 6, or supporting stdlib ≥ 9 and Puppet ≥ 7. Users will be harmed because they won’t be able to use modules that make different compatibility choices. If module A decides to support stdlib ≥ 9, and module B decides to support stdlib < 9, then they cannot be used together. Finally, users will not know that they can set strict=warning. I am an expert user (I worked on the Puppet SRE team for years and have written types & providers) and I did not know that this was a setting until I found the puppetlabs-stdlib #1365. Other people will encounter this and understand it to be a fundamental incompatibility between modules. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.486431.1685855267000.4540.1685856720048%40Atlassian.JIRA.
Jira (PUP-11867) Documentation: default is now strict=error
Title: Message Title Daniel Parks commented on PUP-11867 Re: Documentation: default is now strict=error I filed PUP-11868 about the new default breaking deprecation warnings. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.486430.1685854485000.4539.1685855340029%40Atlassian.JIRA.
Jira (PUP-11868) New default strict=error breaks all deprecation warnings
Title: Message Title Daniel Parks created an issue Puppet / PUP-11868 New default strict=error breaks all deprecation warnings Issue Type: Bug Affects Versions: PUP 8.0.1, PUP 8.0.0 Assignee: Unassigned Created: 2023/06/03 10:07 PM Priority: Normal Reporter: Daniel Parks Puppet Version: 8.0.0 Puppet Server Version: N/A OS Name/Version: all Puppet 8 now defaults to strict=error despite what the official docs say (I filed PUP-11867). One of the impacts of this is that all warnings become errors. This is particularly problematic for deprecation warnings, since now by default deprecations take place immediately. An example of this is the recent change to puppetlabs/stdlib to namespace all its functions. Using the old function names, e.g. ensure_packages (puppetlabs-stdlib #1365), will now result in an error that terminates the Puppet run. Desired Behavior: Deprecation warnings should, by default, be warnings that don’t block Puppet runs. Actual Behavior: Deprecations warnings immediately terminate Pupet runs. Example: From a recent CI job on one of my modules: Error: Evaluation Error: Error while evaluating a Function Call, deprecation. shell_escape. This function is deprecated, please use stdlib::shell_escape instead. at ["/etc/puppetlabs/code/environments/production/modules/rustup/templates/env.sh.epp", 7]:["/etc/puppetlabs/code/environments/production/modules/rustup/manifests/global.pp", 100] (file: /etc/puppetlabs/code/environments/production/modules/rustup/templates/env.sh.epp, line: 7, column: 24) on node 4e706a032afe.hgz2n3xr2b2uteg1gmg5rpevog.jx.internal.cloudapp.net
Jira (PUP-11867) Documentation: default is now strict=error
Title: Message Title Daniel Parks created an issue Puppet / PUP-11867 Documentation: default is now strict=error Issue Type: Bug Affects Versions: PUP 8.0.1, PUP 8.0.0 Assignee: Unassigned Components: Docs Created: 2023/06/03 9:54 PM Priority: Normal Reporter: Daniel Parks Puppet Version: 8.0.0 Puppet Server Version: N/A OS Name/Version: N/A The official documentation says that the default for the strict setting is warning, but the actual default is error. I believe the documentation for strict_variables is also incorrect, but I haven’t run into it myself. Unfortunately, this is very confusing, because it causes all warnings to become errors (I’m filing a separate issue about that). So, it’s particularly important that this documentation be correct. Desired Behavior: Documentation has correct default for strict setting. Actual Behavior: Documentation has incorrect default for strict setting. Add Comment
Jira (PUP-11693) puppet apply --show-diff does nothing
Title: Message Title
Daniel Parks updated an issue
Puppet / PUP-11693
puppet apply --show-diff does nothing
Change By:
Daniel Parks
*Puppet Version:* 7.21.0*Puppet Server Version:* N/A*OS Name/Version:* Ubuntu 22.04.1 Jammy{{puppet apply}} (and presumably {{ {} agent { }} } ) accepts a {{ \ --show-diff}} parameter without failing, but it doesn’t do anything. (The correct name for the parameter is {{ {} \ --show_diff { }} } ; note the underscore.)This is mostly a problem because {{ \ --show-diff}} is a natural guess based on the configuration reference. I’m not sure it’s actual name is documented outside of the help for the {{ \ --test}} option.*Desired Behavior:* either fail with “invalid option” or succeed as if {{ \ --show_diff}} was specified.*Actual Behavior:* ignores the option{code}❯ rm -f /tmp/foo ; touch /tmp/foo❯ puppet apply --show_diff -e 'file { "/tmp/foo": content => "${facts[system_uptime][seconds]}\n" }'Notice: Compiled catalog for vm3.oxidized.org in environment production in 0.01 secondsNotice: /Stage[main]/Main/File[/tmp/foo]/content: --- /tmp/foo 2022-12-15 05:22:48.650776253 -0800+++ /tmp/puppet-file20221215-13413-13tokve 2022-12-15 05:22:52.354791664 -0800@@ -0,0 +1 @@+77133Notice: /Stage[main]/Main/File[/tmp/foo]/content: content changed '{sha256}e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855' to '{sha256}9bd523e3860777cd1c2d38207b95a7bc0bd8ed1d47afc839da1378ce71ad28f3'Notice: Applied catalog in 0.02 seconds❯ sleep 1 ; puppet apply --show-diff -e 'file { "/tmp/foo": content => "${facts[system_uptime][seconds]}\n" }'Notice: Compiled catalog for vm3.oxidized.org in environment production in 0.01 secondsNotice: /Stage[main]/Main/File[/tmp/foo]/content: content changed '{sha256}9bd523e3860777cd1c2d38207b95a7bc0bd8ed1d47afc839da1378ce71ad28f3' to '{sha256}3b9cd754c5b3f7219943c3ebdf2b51b972980cfc0d478e645784ae2b78699314'Notice: Applied catalog in 0.01 seconds❯ puppet apply --invalidError: Could not parse application options: invalid option: --invalid{code}
Add Comment
Jira (PUP-11693) puppet apply --show-diff does nothing
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-11693
puppet apply --show-diff does nothing
Issue Type:
Bug
Assignee:
Unassigned
Created:
2022/12/15 5:26 AM
Priority:
Normal
Reporter:
Daniel Parks
Puppet Version: 7.21.0 Puppet Server Version: N/A OS Name/Version: Ubuntu 22.04.1 Jammy puppet apply (and presumably agent) accepts a -show-diff parameter without failing, but it doesn’t do anything. (The correct name for the parameter is -show_diff; note the underscore.) This is mostly a problem because -show-diff is a natural guess based on the configuration reference. I’m not sure it’s actual name is documented outside of the help for the -test option. Desired Behavior: either fail with “invalid option” or succeed as if --show_diff was specified. Actual Behavior: ignores the option
❯ rm -f /tmp/foo ; touch /tmp/foo
❯ puppet apply --show_diff -e 'file { "/tmp/foo": content => "${facts[system_uptime][seconds]}\n" }'
Notice: Compiled catalog for vm3.oxidized.org in environment production in 0.01 seconds
Notice: /Stage[main]/Main/File[/tmp/foo]/content:
Jira (PUP-11692) Apt package installs sometimes fail silently
Title: Message Title Daniel Parks created an issue Puppet / PUP-11692 Apt package installs sometimes fail silently Issue Type: Bug Assignee: Unassigned Created: 2022/12/14 9:30 PM Priority: Normal Reporter: Daniel Parks Puppet Version: 7.21.0 Puppet Server Version: N/A OS Name/Version: Ubuntu 22.04.1 Jammy Apparently apt-get install interprets the package name as a regular _expression_ if it can’t find the exact package name. This causes Puppet to incorrectly register a success when installing a package name that doesn’t exist, but matches a different package. Desired Behavior: resource fails Actual Behavior: resource succeeds as a change on every run ❯ docker run -it ubuntu:22.04 root@10d181367a3d:/# apt-get update -qq && apt-get install -y curl >/dev/null debconf: delaying package configuration, since apt-utils is not installed root@10d181367a3d:/# curl -OsS https://apt.puppet.com/puppet7-release-jammy.deb root@10d181367a3d:/# dpkg -i puppet7-release-jammy.deb >/dev/null
Jira (PDOC-268) Colliding internal anchors on autogenerated pages
Title: Message Title Daniel Parks commented on PDOC-268 Re: Colliding internal anchors on autogenerated pages I fixed this in Puppet Strings: PR #303 (Issue #300). See the PR for a description of the change (pasting it here doesn’t work well), or look at these two changes: param link, fragment normalization Unfortunately, it appears that Forge strips the elements out of the generated documentation, so they are still broken there. For example, https://forge.puppet.com/modules/dp/golang/reference#golang–from_tarball Would you like me to file a new ticket for that? It’s arguably a separate issue. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.280893.1539770862000.41597.1664938680050%40Atlassian.JIRA.
Jira (PUP-11632) locator.extract_tree_text does returns bad string on simple function call
Title: Message Title Daniel Parks commented on PUP-11632 Re: locator.extract_tree_text does returns bad string on simple function call Thanks for the explanation, Henrik Lindberg; it makes sense. I sincerely hope somebody else gets to this first, but I may end up doing it if not. I should get over my irrational fear of debugging parsers at some point, right? No, Puppet::Pops::Adapters::SourcePosAdapter is only slightly related and doesn’t appear to be source of the issue. An explanation: before my PR, Puppet Strings used ::Puppet::Pops::Adapters::SourcePosAdapter.adapt(node).extract_text to get the text of an AST node, which internally just calls node.locator.extract_text(node.offset, node.length). The problem the PR addressed was that when you fed an _expression_ like 1 + 1 to object.locator.extract_text it returned '+' which was definitely not what we wanted. If this bug came into play it wasn’t at all obvious because we were only getting a fragment of the _expression_. I changed Puppet Strings to use node.locator.extract_tree_text(node), which actually handles expressions. That’s where this issue popped up. A pleasant side effect of all this is that the next release of Puppet Strings won’t use Puppet::Pops::Adapters::SourcePosAdapter at all. (Also, thanks for asking the help desk about my old account, Christopher Thorn!) Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this
Jira (PUP-11632) locator.extract_tree_text does returns bad string on simple function call
Title: Message Title
Daniel Parks commented on PUP-11632
Re: locator.extract_tree_text does returns bad string on simple function call
Found another broken case. The default value of:
String $os = $facts['kernel'] ? {
'Linux' => 'linux',
'Darwin' => 'darwin',
default => $facts['kernel'],
}
The output loses the closing brace and the final comma (though that seems reasonable). I’m adding these cases to my puppet-strings branch: https://github.com/puppetlabs/puppet-strings/compare/main...danielparks:puppet-strings:fix_default_expressions
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11632) locator.extract_tree_text does returns bad string on simple function call
Title: Message Title Daniel Parks commented on PUP-11632 Re: locator.extract_tree_text does returns bad string on simple function call Also, you may be pleased to hear that fixing this will allow me to remove Puppet String’s dependency on Puppet::Pops::Adapters::SourcePosAdapter! Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.469454.166422969.36801.1664233740039%40Atlassian.JIRA.
Jira (PUP-11632) locator.extract_tree_text does returns bad string on simple function call
Title: Message Title Daniel Parks commented on PUP-11632 Re: locator.extract_tree_text does returns bad string on simple function call Also — sorry for bringing it up here, but there doesn’t seem to be a better place — my old Jira acccount (danielparks) seems to be gone. Can it be restored? I had tickets under it. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.469454.166422969.36775.1664229840025%40Atlassian.JIRA.
Jira (PUP-11632) locator.extract_tree_text does returns bad string on simple function call
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-11632
locator.extract_tree_text does returns bad string on simple function call
Issue Type:
Bug
Affects Versions:
PUP 7.19.0
Assignee:
Unassigned
Created:
2022/09/26 3:01 PM
Priority:
Normal
Reporter:
Daniel Parks
Puppet Version: 7.20.0 (main: 948a4bec67def5244595a6f69976a9a2479f1df1) OS Name/Version: macOS 12.6.0 ast.locator.extract_tree_text(ast) returns an incorrect string for a simple function call. it 'extracts a simple function call' do parser = Puppet::Pops::Parser::Parser.new() model = parser.parse_string('$param.func()').model expect(model.body.locator.extract_tree_text(model.body)).to eq('$param.func()') end This is causing a problem for Puppet Strings. See https://github.com/puppetlabs/puppet-strings/issues/240#issuecomment-1257153890 Desired Behavior: The above test should succeed. Actual Behavior: The above test (I added it to spec/unit/pops/parser/locator_spec.rb) fails with got "$param.func(".
Add Comment
Jira (PDB-3284) PQL operators sometimes whitespace sensitive
Title: Message Title Daniel Parks commented on PDB-3284 Re: PQL operators sometimes whitespace sensitive I don't think that = suffixes will be an issue… with a LR(1) parser you should be able to distinguish since facts.endswithequals= "foo" is invalid, facts.endswithequals= = "foo" works. If you have another fact named “endswithequals” it's exactly the opposite. So, you should be able to distinguish them. You're going to have problems with facts with spaces in the name anyway (I think those are allowed). Even if you couldn't distinguish them, it would be a lot clearer to allow syntax like facts["endswithequals="] or facts.endswithequals\=. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Daniel Parks commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist We generally want to run the agent in that environment for a while, since often reverting the environment early will cause undesirable changes. It's general enough that we set the current environment in puppet.conf from within our Puppet code. This boils down to three requirements: I can set the environment on a node from the node itself. Ideally, this can be enforced with Puppet code. The environment will be reverted to production when the branch is deleted. Built into puppet. I don't really care about the implementation. A nice to have is being able to get the current environment with puppet config print. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title
Daniel Parks commented on PUP-9296
Re: ^ and $ shouldn't match newlines in Pattern
Thanks Jean Bond!
If you are matching against a string that contains newlines, use \A and \z instead of ^ and $, as the latter match beginning and end of a line. This is a common mistake that can cause your regexp to unintentionally match multiline text.
Unfortunately, I don't think this is quite clear enough. The issue is that ^ and $ will match newlines in strings you don't expect to have newlines. For example, if you use ^https:// on a URL string, you still could match 'http://bad\nhttps://'. Most people wouldn't expect that string to have a newline. Most users should always use \A and \z, and never use {}, $, or \Z. There are very few cases where Puppet users need {}, $, or \Z — I found one place in our control repo, and that was in code I wrote. Communicating this sort of thing is pretty clearly not my strong point, though. Should I file a new ticket in DOCS? — Henrik Lindberg agreed, I don't think a new type would be helpful. And, I figured the implementation of this would be a pain, since you would need to switch to something like PCRE, and then you would have to figure out all of the tiny differences, and… giant pain. — I will submit PRs or file tickets with various modules to get this fixed. I'll also look into getting it added to puppet-lint.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because
Jira (PUP-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title Daniel Parks commented on PUP-9296 Re: ^ and $ shouldn't match newlines in Pattern The Pattern documentation is actually incorrect — it should be \z not \Z. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title
Daniel Parks commented on PUP-9296
Re: ^ and $ shouldn't match newlines in Pattern
I did the research, so I might as well add it here. I checked our control repo and all of its modules, and found one instance of {} and $ being used correctly — and that was in code I'd written. It looks like the few modules that use \A, \Z, or \z don't consistently use those instead of {} and $. I only found one place where changing the behavior would break the code, and that was in our control repo. Almost all of this was in data validation, which is why I'm bringing this up. It's a potential (but unlikely) security issue. I searched with:
ag --puppet 'Pattern.*/.*(\\A|\\Z|\\z|\^|\$)' . modules/*/
ag --puppet '=~\s*/.*(\\A|\\Z|\\z|\^|\$)'
ag --puppet 'regsubst.*,.*(\\A|\\Z|\\z|\^|\$)' . modules/*/
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title Daniel Parks commented on PUP-9296 Re: ^ and $ shouldn't match newlines in Pattern I put up a poll on /r/puppet. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title
Daniel Parks commented on PUP-9296
Re: ^ and $ shouldn't match newlines in Pattern
Where do you see the specification? I've tested it on macOS and Linux, and they both behave identically for both basic and extended regexes:
regex-test.c
Show all
#include
#include
int main(int argc, char** argv) {
regex_t re;
int ret;
regmatch_t pmatch[1];
ret = regcomp(, "^foo$", REG_EXTENDED);
if (ret != 0) {
printf("regcomp returned %d\n", ret);
Jira (PUP-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title Daniel Parks commented on PUP-9296 Re: ^ and $ shouldn't match newlines in Pattern I keep running into this — it's really surprising behavior to both Puppet and Ruby users. It's also not traditional regex behavior. See BSD regex, PCRE, Python, _javascript_, Java, Go, Awk, etc. I didn't find an example of another regex library that behaves this way (except for $ behaving like \Z in Python for some reason). I don't think we need to follow the Ruby pattern. Most of the people using Puppet aren't Ruby programmers, let alone expert ones who would know the difference. We have incorrect code in Puppet-supplied modules, including: puppetlabs-stdlib puppetlabs-apt — uses $ puppetlabs-apt — uses \Z instead of \z puppetlabs-apache puppetlabs-java — okay, there are a few other issues there. puppetlabs-postgresql Every module I looked at that used Pattern had at least one error, and most of them didn't use \A or \z at all. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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,
Jira (PUP-9301) Reduce noise from notify resource
Title: Message Title
Daniel Parks commented on PUP-9301
Re: Reduce noise from notify resource
The issue is with notify in general:
❯ puppet apply -e 'notify { "boo": }'
Notice: Compiled catalog for marla.local in environment production in 0.01 seconds
Notice: boo
Notice: /Stage[main]/Main/Notify[boo]/message: defined 'message' as 'boo'
Notice: Finished catalog run in 0.01 seconds
Note that it outputs “boo” three times. I think a decent solution would be a function that does this. It would output in --test mode, but it wouldn't create a resource, so it would have the extra noise, and it wouldn't register as a change in the report. I'll be tracking this from my community account Daniel Parks after 1/31.
Add Comment
This
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Daniel Parks commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist Currently we (InfraCore) are using something that is functionally identical to puppetlabs-operations/puppet-cron, but written in Python (I got distracted trying to figure out packaging for the Go one). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Daniel Parks commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist Apparently I can change the assignee from a community account I unassigned myself, since it's not waiting on me (if I'm incorrect, let me know). Should this now be assigned to Josh Cooper? I'm not really sure what your workflow is. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Daniel Parks assigned an issue to Unassigned Puppet / PUP-8376 Revert to production when agent-specified environment doesn't exist Change By: Daniel Parks Assignee: Daniel Parks Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-1168) Add values to default resources with the plusignment
Title: Message Title
Daniel Parks commented on PUP-1168
Re: Add values to default resources with the plusignment
For future people who stumble upon this, here is a puppet apply command line that demonstrates the problem:
❯ puppet apply <<'EOF'
define echo ( $lines = ['one'] ) {
exec { "echo ${title}":
command => "/bin/echo ${$lines.join(', ')}",
logoutput => true,
}
}
echo { 'a': }
echo { 'b': lines => ['two'] }
Echo <| |> { lines +> ['three'] }
EOF
Notice: Compiled catalog for marla.corp.puppetlabs.net in environment production in 0.13
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Daniel Parks assigned an issue to Henrik Lindberg Puppet / PUP-8376 Revert to production when agent-specified environment doesn't exist Change By: Daniel Parks Assignee: Daniel Parks Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9394) File mode X should work with the = operator
Title: Message Title Daniel Parks assigned an issue to Unassigned Puppet / PUP-9394 File mode X should work with the = operator Change By: Daniel Parks Assignee: Daniel Parks Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9394) File mode X should work with the = operator
Title: Message Title Daniel Parks commented on PUP-9394 Re: File mode X should work with the = operator Right. I'm asking for it not to match chmod's behavior. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9394) File mode X should work with the = operator
Title: Message Title Daniel Parks updated an issue Puppet / PUP-9394 File mode X should work with the = operator Change By: Daniel Parks Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9394) File mode X should work with the = operator
Title: Message Title Daniel Parks created an issue Puppet / PUP-9394 File mode X should work with the = operator Issue Type: Improvement Assignee: Unassigned Created: 2019/01/03 12:13 AM Priority: Normal Reporter: Daniel Parks Setting mode => 'u=rwX,go=rX' or similar symbolic modes on File resources fails with the following error: File[/foo]/mode: change from '0755' to 'u=rwX,go=rX' failed: X only works with the '+' operator at "u=rwX" in symbolic mode "u=rwX,go=rX" It would be helpful if X worked with the = operator. In that case, it would only set the execute bit if the resource represented a directory. I realize that this isn't the way chmod works. I know that I can use '0644' and it will automatically apply '0755', but that's weird and surprising. Using X in symbolic mode is much clearer and more intuitive. Add Comment
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Daniel Parks commented on PUP-8376 Re: Revert to production when agent-specified environment doesn't exist Apologies for the 11 month delay! We generally run puppet by hand with the environment specified (puppet agent -tE devbranch). There a number of reasons for this, the largest of which is convenience (a CLI tool on the node is always going to be more convenient). Furthermore, using a custom ENC would be a giant pain, since we would have multiple people changing it, often at the same time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9358) Setting Windows group gid fails on second run
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-9358
Setting Windows group gid fails on second run
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/12/11 12:16 PM
Labels:
customer0
Priority:
Normal
Reporter:
Daniel Parks
Puppet Version: 6.0.2 Puppet Server Version: 2019.0.0 OS Name/Version: Windows Server 2012 R2 group { gid => 1000 } works fine when creating the group, but fails on the second run.
PS C:\Program Files\Puppet Labs> .\Puppet\bin\puppet.bat resource group foobar ensure=present gid=1000
Notice: /Group[foobar]/ensure: created
group { 'foobar':
ensure => 'present',
gid=> 'S-1-5-21-3100550808-3956625304-3008681921-1010',
Jira (PDB-4208) resources { inventory {} } implicit subquery
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-4208
resources { inventory {} } implicit subquery
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/12/08 9:54 PM
Labels:
customer0
Priority:
Normal
Reporter:
Daniel Parks
It would be really handy if this worked:
resources { type = "My::Type" and inventory { facts.os.name = "Debian" }
In general, it would be awesome if there were implicit subqueries for all combinations of parent and child objects with a certname attribute.
Add Comment
Jira (PUP-9301) Reduce noise from notify resource
Title: Message Title Daniel Parks created an issue Puppet / PUP-9301 Reduce noise from notify resource Issue Type: Improvement Assignee: Unassigned Created: 2018/11/01 9:34 PM Labels: customer0 Priority: Normal Reporter: Daniel Parks Currently the notify resource produces a lot of extra output in --test: Notice: User['kfj'] not created because they don't have a password. Notice: /Stage[main]/Virtual::Users/Account::User[kfj]/Account::User::Windows[kfj]/Notify[User['kfj'] not created because they don't have a password.]/message: defined 'message' as 'User[\'kfj\'] not created because they don\'t have a password.' That outputs the message three times. I can reduce that slightly by setting the title to something else, but then I have to be careful to use a unique title. It would be awesome if it just outputted the message once. Or, if it outputted the message once and the title once — that would be worth it for certain messages.
Jira (PUP-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-9296
^ and $ shouldn't match newlines in Pattern
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/10/31 11:28 PM
Labels:
customer0
Priority:
Normal
Reporter:
Daniel Parks
Pattern currently matches ^ and $ to newlines as well as start and end of string (multiline mode). It would be less surprising if they behaved like \A and \z (or maybe \Z). I've seen a number of places where people use the wrong anchors. The most obvious place is in stdlib, e.g. Stdlib::Unixpath.
❯ puppet apply -e 'notice("foo\nbar\nbah" =~ Pattern["^bar$"])'
Notice: Scope(Class[main]): true
❯ puppet apply -e 'notice("foo\nbar\nbah" =~ Pattern["\\Abar\\z"])'
Notice: Scope(Class[main]): false
Jira (PUP-9289) lookup_options/convert_to should be able to convert values in hashes
Title: Message Title Daniel Parks commented on PUP-9289 Re: lookup_options/convert_to should be able to convert values in hashes I figured this would a tricky one. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9289) lookup_options/convert_to should be able to convert values in hashes
Title: Message Title
Daniel Parks updated an issue
Puppet / PUP-9289
lookup_options/convert_to should be able to convert values in hashes
Change By:
Daniel Parks
Labels:
customer0
Summary:
lookup_options/convert_to should be able to convert Hash values in hashes
It would be very helpful if {{convert_to}} could convert values in hashes. In particular, this would be useful for converting {{Hash [String, String] }} values to {{ Hash[String, Sensitive ] }}. Individual Being able to convert individual values (e.g. {{account::user[password]}}) would be nice, but needing to specify something like {{Hash[String, Struct[…]]}} would work too.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9289) lookup_options/convert_to should be able to convert Hash values
Title: Message Title Daniel Parks created an issue Puppet / PUP-9289 lookup_options/convert_to should be able to convert Hash values Issue Type: Improvement Assignee: Unassigned Created: 2018/10/29 9:38 PM Priority: Normal Reporter: Daniel Parks It would be very helpful if convert_to could convert values in hashes. In particular, this would be useful for converting Hash values to Sensitive. Individual values would be nice, but needing to specify something like Hash[String, Struct[…]] would work too. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9141) Ability to destroy multiple CSRs at once
Title: Message Title Daniel Parks updated an issue Puppet / PUP-9141 Ability to destroy multiple CSRs at once Change By: Daniel Parks Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-9141) Ability to destroy multiple CSRs at once
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-9141
Ability to destroy multiple CSRs at once
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/09/14 2:50 PM
Priority:
Normal
Reporter:
Daniel Parks
It would be super helpful to be able to destroy multiple pending certs at once, for example:
sudo puppet ca destroy bad-host.example.net other-bad-host.example.net
We end up getting a lot of bad CSRs, and it would be very expensive to fix on the other end. We currently have 450+. I end up dong things like:
sudo puppet ca list | awk '/bad-host/ {print$1}' | xargs -n 1 sudo puppet ca destroy
Jira (BOLT-792) Plan usage needs human friendly TargetSpec type string
Title: Message Title Daniel Parks created an issue Puppet Task Runner / BOLT-792 Plan usage needs human friendly TargetSpec type string Issue Type: Improvement Assignee: Unassigned Created: 2018/08/20 1:46 PM Priority: Normal Reporter: Daniel Parks The type string for TargetSpec parameters is not very human-friendly: ❯ bundle exec bolt --modulepath site plan show upgrade_pe::deploy_solaris_packages upgrade_pe::deploy_solaris_packages USAGE: bolt plan run upgrade_pe::deploy_solaris_packages mono_master= solaris_repo_server=
Jira (BOLT-792) Plan usage needs human friendly TargetSpec type string
Title: Message Title Daniel Parks updated an issue Puppet Task Runner / BOLT-792 Plan usage needs human friendly TargetSpec type string Change By: Daniel Parks Labels: customer0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3930) PQL's ~ matches incorrectly on dotted variables
Title: Message Title Daniel Parks updated an issue PuppetDB / PDB-3930 PQL's ~ matches incorrectly on dotted variables Change By: Daniel Parks Priority: Major Normal Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3930) PQL's ~ matches incorrectly on dotted variables
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-3930
PQL's ~ matches incorrectly on dotted variables
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/06/02 11:00 PM
Environment:
2018.2.0-rc2
Labels:
customer0
Priority:
Major
Reporter:
Daniel Parks
The ~ operator treats dotted variables, e.g. parameters.ensure and facts.fqdn, as if their values were wrapped in double quotes. Both of the following return thousands of records:
resources { type = 'File' and parameters.ensure ~ '^"file"$' }
resources { type = 'File' and parameters.ensure = 'file' }
The following returns no records:
resources { type = 'File' and parameters.ensure ~
Jira (BOLT-495) Incorrect known_hosts checking
Title: Message Title Daniel Parks updated an issue Puppet Task Runner / BOLT-495 Incorrect known_hosts checking I just submitted a vulnerability report to another project about this, so I guess I should clarify that it should match on just the passed identifier (hostname or IP). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (BOLT-495) Incorrect known_hosts checking
Title: Message Title Daniel Parks created an issue Puppet Task Runner / BOLT-495 Incorrect known_hosts checking Issue Type: Bug Affects Versions: BOLT 0.19.0 Assignee: Unassigned Created: 2018/04/24 2:44 PM Labels: customer0 Priority: Normal Reporter: Daniel Parks Bolt does not parse known_hosts properly: It treats a comma in the host field as an AND when it should be an OR. It requires an IP address. ❯ host test-host test-host has address 1.1.1.1
Jira (PDB-3902) PQL's is null operator throws error on facts
Title: Message Title Daniel Parks updated an issue PuppetDB / PDB-3902 PQL's is null operator throws error on facts Change By: Daniel Parks Summary: facts.osfamily PQL's is null cause 500 operator throws error on facts Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3903) PQL ~ operator matches empty strings incorrectly
Title: Message Title
Daniel Parks updated an issue
PuppetDB / PDB-3903
PQL ~ operator matches empty strings incorrectly
Change By:
Daniel Parks
It looks like the {{~}} operator treats an empty string as if it were a pair of double quotes ({{""}}).Both of the following return one record:{code}inventory { certname = 'mycert' and facts.a.b = '' }inventory { certname = 'mycert' and facts.a.b ~ '^""$' }{code}The following returns no records:{code}inventory { certname = 'mycert' and facts.a.b ~ '...' }{code} To be clear, the {{mycert}} node has a fact {{a.b}} that contains an empty string.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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.
Jira (PDB-3903) PQL ~ operator matches empty strings incorrectly
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-3903
PQL ~ operator matches empty strings incorrectly
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/04/10 11:12 PM
Environment:
PE 2018.1.0-rc14
Priority:
Normal
Reporter:
Daniel Parks
It looks like the ~ operator treats an empty string as if it were a pair of double quotes (""). Both of the following return one record:
inventory { certname = 'mycert' and facts.a.b = '' }
inventory { certname = 'mycert' and facts.a.b ~ '^""$' }
The following returns no records:
inventory { certname = 'mycert' and facts.a.b ~ '...' }
Jira (PDB-3889) Make it easier to query classes
Title: Message Title Daniel Parks created an issue PuppetDB / PDB-3889 Make it easier to query classes Issue Type: New Feature Assignee: Unassigned Created: 2018/04/02 5:49 PM Priority: Normal Reporter: Daniel Parks I have to uppercase the first letter of every word in the class name. I do this all the time and it's a huge pain. One of my primary uses is to see if a class is still in use. I want to be sure, so I always copy and paste. As a result, I always use dalen/puppetdbquery since I don't have to modify the class name and potentially introduce a typo. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Daniel Parks commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity Awesome! Thanks! Really appreciate it. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Daniel Parks commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity Sorry for the edit and the extra comment: could we bump the priority on this? It's really irritating. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8566) "puppet config print" needs --quiet option to disable new (default) verbosity
Title: Message Title Daniel Parks commented on PUP-8566 Re: "puppet config print" needs --quiet option to disable new (default) verbosity In the case where -section is specified: please make the default behavior to not output this, even when in verbose mode. With -section specified it adds no useful information. This extra output is a particular problem in cron jobs, since the standard behavior is to generate an email when there is output. My jobs are only supposed to output on failure, so this means that failures will be lost in the noise. (Fortunately these emails are not coming into my inbox.) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8592) `puppet config --section main print` writes section info to stderr
Title: Message Title Daniel Parks commented on PUP-8592 Re: `puppet config --section main print` writes section info to stderr I'm running into this in a number of places. For example, I have a script that runs in cron that now is generating mail because of this (cron only sends email if a job generates output). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-8592) `puppet config --section main print` writes section info to stderr
Title: Message Title Daniel Parks created an issue Puppet / PUP-8592 `puppet config --section main print` writes section info to stderr Issue Type: Bug Affects Versions: PUP 5.5.0 Assignee: Unassigned Created: 2018/03/22 11:30 PM Labels: customer0 Priority: Normal Reporter: Daniel Parks ❯ puppet config --section main print confdir >/dev/null Resolving settings from section 'main' in environment 'production' I already know what section it's from; I don't need to have it print it.
Jira (PDB-2635) implicit subquery relationship between facts and resources via certname
Title: Message Title Daniel Parks commented on PDB-2635 Re: implicit subquery relationship between facts and resources via certname I filed a ticket to cover creating all possible implicit subqueries: PDB-3880. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3880) Add all implicit subqueries
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-3880
Add all implicit subqueries
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/03/22 8:57 AM
Priority:
Normal
Reporter:
Daniel Parks
Please add implicit subqueries wherever possible. For example, all of the following should have implicit subqueries based on certname:
inventory { resources { title ~ "rundeck" } }
resources { title ~ "rundeck" and inventory { facts.stage = "prod" } }
reports { resources { title ~ "rundeck" } and inventory { facts.stage = "prod" } }
resources { title ~ "rundeck" and resources { title = "Nginx" } }
I use subqueries all the time, and probably >90% of the time I want a subquery based on certname. I also am never quite sure where they're enabled, so I end up always writing out certname in whatever[certname]. See also PDB-2635 filed by Wyatt Alt.
Jira (PDB-3862) replace facts failing for some nodes
Title: Message Title Daniel Parks commented on PDB-3862 Re: replace facts failing for some nodes Sorry, this became critical. Certain nodes no longer show up in inventory, though they do show up in nodes. This means that they don't show up in our inventory application, which means that important maintenance doesn't happen on them. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3862) replace facts failing for some nodes
Title: Message Title Daniel Parks updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Daniel Parks Priority: Normal Critical Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (FACT-1377) $ecdsakey fact does not represent specific key type
Title: Message Title Daniel Parks commented on FACT-1377 Re: $ecdsakey fact does not represent specific key type Thanks Michael Smith! Now I know how to add release notes in the future. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3862) replace facts failing for some nodes
Title: Message Title Daniel Parks commented on PDB-3862 Re: replace facts failing for some nodes Tiffany Longworth, I don't think so; this error is specific to facts, and doesn't seem to be affecting any of the icinga nodes. Affected nodes Show all ❯ sudo fgrep 'duplicate key value violates unique constraint' /var/log/puppetlabs/puppetdb/puppetdb.log | fgrep 'Retrying after attempt 0 for' | sed -e 's/.*Retrying after attempt 0 for //' -e 's/,.*//' | sort | uniq cla-app1-prod.puppetlabs.com cricket.delivery.puppetlabs.net dagr.delivery.puppetlabs.net debrepo-app1-prod.ops.puppetlabs.net docsreview-aio01-dev.ops.puppetlabs.net freyja.delivery.puppetlabs.net lemon.delivery.puppetlabs.net lion.delivery.puppetlabs.net mozart.delivery.puppetlabs.net
Jira (PDB-3862) replace facts failing for some nodes
Title: Message Title Daniel Parks commented on PDB-3862 Re: replace facts failing for some nodes I've attached the JSON output of the _puppet_inventory_1 fact from a broken node and a working node. No idea if it's actually related. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3862) replace facts failing for some nodes
Title: Message Title Daniel Parks updated an issue PuppetDB / PDB-3862 replace facts failing for some nodes Change By: Daniel Parks Attachment: working_puppet_inventory_1.json Attachment: broken_puppet_inventory_1.json Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 (PDB-3862) replace facts failing for some nodes
Title: Message Title Daniel Parks created an issue PuppetDB / PDB-3862 replace facts failing for some nodes Issue Type: Bug Assignee: Unassigned Created: 2018/03/06 8:33 PM Environment: Puppet Server Version: 2018.1.0-rc11 Puppet Version: 5.5.0 Labels: customer0 Priority: Normal Reporter: Daniel Parks Some nodes are not able to update facts when they run Puppet. The facts are correctly processed by facter, but they are never updated in PuppetDB. The exception below shows up in the PuppetDB log: 2018-03-06 20:30:23,236 ERROR [p.p.command] [8,101,330] [replace facts] Retrying after attempt 0 for dagr.delivery.puppetlabs.net, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "package_hash_key" Detail: Key (hash)=(\xee8fe1767d1d1fc141ed94bb13479d4183b2cce8) already exists. org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "package_hash_key"
Jira (PUP-8394) cache/locales/config.yaml not stable across runs
Title: Message Title Daniel Parks created an issue Puppet / PUP-8394 cache/locales/config.yaml not stable across runs Issue Type: Bug Assignee: Unassigned Created: 2018/01/24 11:35 PM Priority: Normal Reporter: Daniel Parks Puppet Version: 5.3.4 Puppet Server Version: 2018.1.0-rc8 OS Name/Version: various /opt/puppetlabs/puppet/cache/locales/config.yaml often changes despite no code changes being made. It appears to be random. The only changes are the names of the project and package, and that swaps between powershell and mongodb. This has been going on for a while; I think it was present in Hoyt. Desired Behavior: No changes to locales. Actual Behavior: Info: Retrieving locales Debug: Dynamically-bound server lookup failed, falling back to server setting
Jira (PUP-8376) Revert to production when agent-specified environment doesn't exist
Title: Message Title Daniel Parks created an issue Puppet / PUP-8376 Revert to production when agent-specified environment doesn't exist Issue Type: New Feature Assignee: Unassigned Created: 2018/01/21 11:55 AM Priority: Normal Reporter: Daniel Parks Puppet Version: 5.3.4 Please add a setting that causes the agent to switch to a specific environment, e.g. production, when the agent-specified environment does not exist. Our workflow: Deploy a feature branch, e.g. change_ntp_server Switch a node over to the feature branch for development, e.g. sudo puppet config set --section agent environment change_ntp_server Run puppet, update branch, run puppet… Merge the feature branch into production Delete the feature branch Our custom puppet wrapper detects that the change_ntp_server environment no longer exists, and switches the environment back to production I don't particularly care if
Jira (PDB-3806) PQL's "in" operator doesn't work on resource parameters
Title: Message Title Daniel Parks commented on PDB-3806 Re: PQL's "in" operator doesn't work on resource parameters Also, as Ryan Whitehurst noted in the PDB-3285 , is null and is not null are still broken. I haven't made an effort to check other operators; these are just things I'm running into. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8290) Allow auto-conversion to Sensitive data type
Title: Message Title Daniel Parks commented on PUP-8290 Re: Allow auto-conversion to Sensitive data type Oh, sounds like you might be on the hiera team. I suppose the counter argument to making more hiera magic is that people can just use Init[Sensitive]. It's not like many things use Sensitive now. (I ran into this in distelli_agent, which is broken in other ways.) Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8290) Allow auto-conversion to Sensitive data type
Title: Message Title Daniel Parks commented on PUP-8290 Re: Allow auto-conversion to Sensitive data type Cool, thanks. I look forward to trying out Init[T]. For the automatic parameter problem, maybe it would be better to add support in hiera. It already does some magic around types (I think). I'm going to check with the hiera team once I figure out who they are. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8290) Allow auto-conversion to Sensitive data type
Title: Message Title
Daniel Parks created an issue
Puppet / PUP-8290
Allow auto-conversion to Sensitive data type
Issue Type:
Improvement
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Created:
2017/12/21 10:51 PM
Priority:
Normal
Reporter:
Daniel Parks
Puppet Version: 5.3.3 Puppet Server Version: N/A OS Name/Version: N/A
When passing data to a resource that declares a parameter as Sensitive the value must be manually cast to Sensitive. Please allow values matching type T to be automatically cast to values of Sensitive[T].
In particular, this would be helpful for automatic parameters.
Right now Sensitive is too much of a pain. Automatic casts would remove that cost and allow me to start using it everywhere.
Desired Behavior:
❯ puppet apply -e 'define foo ( Sensitive $p ) { } foo { "f": p => "secret" }'
Notice:
Jira (FACT-1377) $ecdsakey fact does not represent specific key type
Title: Message Title Daniel Parks commented on FACT-1377 Re: $ecdsakey fact does not represent specific key type Finally got around to submitting this as PR #1678. I didn't include a comment attribute; it's not really used for host keys. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (FACT-1377) $ecdsakey fact does not represent specific key type
Title: Message Title Daniel Parks assigned an issue to Daniel Parks Facter / FACT-1377 $ecdsakey fact does not represent specific key type Change By: Daniel Parks Assignee: Daniel Parks Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8050) puppet agent -e environment
Title: Message Title Daniel Parks commented on PUP-8050 Re: puppet agent -e environment Awesome! Thanks everybody! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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-8051) puppet agent option to wait for lock
Title: Message Title Daniel Parks created an issue Puppet / PUP-8051 puppet agent option to wait for lock Issue Type: New Feature Assignee: Unassigned Created: 2017/10/13 3:23 PM Priority: Normal Reporter: Daniel Parks Please add an option to make puppet agent wait for the lock to become available and then run. As is I often end up retrying multiple times, or setting up a while loop to check for the presence of the lock file. For example, puppet agent --waitforlock --test or puppet agent -Wt. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-8050) puppet agent -e environment
Title: Message Title
Daniel Parks updated an issue
Puppet / PUP-8050
puppet agent -e environment
Change By:
Daniel Parks
Please add a {{ \ -e}} short option for {{puppet agent}} that corresponds to {{--environment}}. We (and likely many other people) running {{puppet agent -t --environment myenv}} many times per day.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-8050) puppet agent -e environment
Title: Message Title Daniel Parks created an issue Puppet / PUP-8050 puppet agent -e environment Issue Type: Improvement Affects Versions: PUP 5.3.1 Assignee: Unassigned Created: 2017/10/13 3:19 PM Priority: Normal Reporter: Daniel Parks Please add a e short option for puppet agent that corresponds to -environment. We (and likely many other people) running puppet agent -t --environment myenv many times per day. Add Comment
Jira (PUP-7902) Heredoc with hyphen strips extra newlines
Title: Message Title Daniel Parks created an issue Puppet / PUP-7902 Heredoc with hyphen strips extra newlines Issue Type: Bug Assignee: Unassigned Created: 2017/09/03 10:56 PM Environment: Puppet 5.1.0 OS X 10.12.6 Priority: Normal Reporter: Daniel Parks A heredoc set to suppress the final line break also converts double line breaks into single line breaks. Without suppression (END) ❯ cat test.pp notice(@(END))
Jira (FACT-1377) $ecdsakey fact does not represent specific key type
Title: Message Title
Daniel Parks commented on FACT-1377
Re: $ecdsakey fact does not represent specific key type
Actually, it looks like it would be quite easy to add this to the built-in fact.
Proposal: add type and comment attributes to each of the entries in the ssh fact. The type will be the real key type, and the comment will be the comment, if it exists, or null if it doesn't.
Existing, ellipsized
Show all
❯ facter ssh
{
ecdsa => {
fingerprints => { ... },
key => "..."
},
ed25519 => {
fingerprints => { ... },
Jira (FACT-1377) $ecdsakey fact does not represent specific key type
Title: Message Title
Daniel Parks commented on FACT-1377
Re: $ecdsakey fact does not represent specific key type
Here's how that fact can be used:
❯ curl -sSXGET 'http://localhost:8080/pdb/query/v4' -d limit=1 \
-d 'query=inventory[facts] { nodes { deactivated is null and expired is null } }' \
| jq -r '.[].facts
| select(.ssh_host_keys and .networking and .networking.ip and .fqdn)
| . as $facts | .ssh_host_keys | to_entries | .[]
| "\($facts.fqdn),\($facts.networking.ip) \(.key) \(.value.key) \(.value.comment)"'
example.puppet.com,10.1.2.3 ssh-dss AAA... root@debian
example.puppet.com,10.1.2.3 ssh-rsa AAA... root@debian
example.puppet.com,10.1.2.3 ssh-ed25519 AAA... root@debian
example.puppet.com,10.1.2.3 ecdsa-sha2-nistp256 AAA...
Jira (FACT-1377) $ecdsakey fact does not represent specific key type
Title: Message Title
Daniel Parks commented on FACT-1377
Re: $ecdsakey fact does not represent specific key type
This effectively prevents using the built-in fact to populate known_hosts, which is kind of the obvious use for it.
A simple fact that gets you the necessary information to populate a known_hosts file:
lib/facter/ssh_host_keys.rb
Facter.add(:ssh_host_keys) do
setcode do
types = {}
Dir.glob("/etc/ssh/ssh_host_*.pub").each do |path|
type, key, comment = File.read(path).chomp.split(" ", 3)
# Skip the SSH v1 key in /etc/ssh/ssh_host_key.pub
if type =~ /^[a-z]/
Jira (PDB-2642) PQL: Spike/research deactivated node handling
Title: Message Title Daniel Parks commented on PDB-2642 Re: PQL: Spike/research deactivated node handling To be clear, this suggestion from Charlie Sharpsteen would be really helpful: Or go back to implicitly filtering results from deactivated nodes in all entities, but provide command line switches and API headers that can turn this implicit filter off. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-2642) PQL: Spike/research deactivated node handling
Title: Message Title
Daniel Parks commented on PDB-2642
Re: PQL: Spike/research deactivated node handling
Please please please add a way to disable data from deactivated nodes.
I have never ever wanted to get data from a deactivated node, so I have to stick the nodes { deactivated is null and expired is null} somewhere in all my queries. It's really easy to forget, so I end up with results that don't make sense. It's an irritation every time I use PuppetDB.
I can't even fix it programmatically without a silly amount of effort (parse the PQL, add the deactivated subquery to each subquery, etc.).
An HTTP parameter would be wonderful.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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 (PDB-3393) PQL: querying structured facts is awkward
Title: Message Title
Daniel Parks commented on PDB-3393
Re: PQL: querying structured facts is awkward
Also, this is ignoring what I have to do to filter out deactivated nodes:
facts[certname,value] {
name="classification"
and certname in inventory[certname] {
facts.classification.version = 1
and nodes { deactivated is null and expired is null }
}
}
Add Comment
Jira (PDB-3393) PQL: querying structured facts is awkward
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-3393
PQL: querying structured facts is awkward
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2017/04/02 8:43 PM
Environment:
PE 2017.1.1
Priority:
Normal
Reporter:
Daniel Parks
If I want to query based on the content of a structured fact, I have to query the inventory. In order to retrieve just the value of the structured fact, I have to query facts and make a subquery to the inventory.
More generally, the syntax is inconsistent and the inconsistency doesn't make day-to-day tasks easier.
facts[certname,value] { name="classification" and certname in inventory[certname] { facts.classification.version = 1 } }
[{"certname": . . .}]
Jira (PUP-4650) cron resources with the same name but for different users can't be purged
Title: Message Title Daniel Parks commented on PUP-4650 Re: cron resources with the same name but for different users can't be purged Just ran into this in production. When you end up with two cron entries with the same name, the resource isn't declared in puppet, and purge is on, then it will remove one entry on the first run, then the second entry on the second run. This could be a bit of a security vulnerability if you're using Puppet for that sort of thing, since it allows an attacker to "hide" cron jobs. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (PDB-3285) PQL's ~ operator doesn't work on resource parameters
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-3285
PQL's ~ operator doesn't work on resource parameters
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/01/27 4:35 PM
Environment:
CentOS Linux release 7.3.1611 (Core) pe-puppetdb-4.2.5-1.el7.noarch
Priority:
Normal
Reporter:
Daniel Parks
The ~ operator doesn't work on resource parameters, even when = does (see PDB-3284 for caveat).
❯ curl -sSXGET 'http://localhost:8080/pdb/query/v4' \
-d 'query=resources { parameters.content = "a"}'
[]
Jira (PDB-3284) PQL operators sometimes whitespace sensitive
Title: Message Title
Daniel Parks created an issue
PuppetDB / PDB-3284
PQL operators sometimes whitespace sensitive
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/01/27 4:28 PM
Environment:
CentOS Linux release 7.3.1611 (Core) pe-puppetdb-4.2.5-1.el7.noarch
Priority:
Normal
Reporter:
Daniel Parks
When querying resources whitespace is required before the comparison operator on parameters. This is not true when using the comparison operator on, say, type.
❯ curl -sSXGET 'http://localhost:8080/pdb/query/v4' \
-d 'query=resources { parameters.content = "a"}'
[]
Jira (PDB-3178) Create/Deploy EC2 "zombie killer"
Title: Message Title Daniel Parks commented on PDB-3178 Re: Create/Deploy EC2 "zombie killer" Ops is actually writing a general zombie killer in the near future, see OPS-11419. Sorry you weren't in the loop on that. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1537) Dpkg package provider misbehaving for held package with specific version
Title: Message Title Daniel Parks commented on PUP-1537 Re: Dpkg package provider misbehaving for held package with specific version newer pull request (also closed): https://github.com/puppetlabs/puppet/pull/2770 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Daniel Parks commented on PUP-3483 Re: Systemd provider doesn't scan for changed units This should be built into puppet. The exec thing is a giant pain and a horrible kludge for all the reasons listed above. It's only going to get worse as time goes on. Running daemon-reload every time Puppet restarts a service is not very heavy: if Puppet runs avery 30 minutes and restarts at least one service, that's only daemon-reloading twice an hour. If avoiding unnecessary daemon-reloads is really important, then puppet can scan for changed unit files easily enough. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-5849) Newline is not sufficient to avoid parsing as a function call
Title: Message Title Daniel Parks commented on PUP-5849 Re: Newline is not sufficient to avoid parsing as a function call Yes! Hooray! Thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PDB-2729) REST API ignores data after AST query
Title: Message Title Daniel Parks commented on PDB-2729 Re: REST API ignores data after AST query Yeah, something like that. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 (PDB-2729) REST API ignores data after AST query
Title: Message Title Daniel Parks created an issue PuppetDB / PDB-2729 REST API ignores data after AST query Issue Type: Bug Affects Versions: PDB 4.0.1 Assignee: Unassigned Created: 2016/05/20 1:47 PM Environment: CentOS Linux release 7.2.1511 (Core) PE 2016.1 with separate compile nodes Priority: Normal Reporter: Daniel Parks Query Result Expected ["=", "title", "dp"] found
Jira (PUP-6296) Computing checksum slow on big files
Title: Message Title Daniel Parks commented on PUP-6296 Re: Computing checksum slow on big files Probably relevant: backup was not disabled on the file resource. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-6274) include undef doesn't fail
Title: Message Title
Daniel Parks updated an issue
Puppet / PUP-6274
include undef doesn't fail
Change By:
Daniel Parks
{code}❯ puppet apply -e "include undef"Notice: Compiled catalog for zhora.local in environment production in 0.04 secondsNotice: Applied catalog in 0.03 seconds{code}Expected results: compilation failureSimilarly, {{include ''}} doesn't fail, though {{include nosuchclass}} does.Example scenario: {{include $::some::class::tyypo}} (in my case, I accidentally grabbed the dollar sign while copying and pasting)
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6274) include undef doesn't fail
Title: Message Title
Daniel Parks updated an issue
Puppet / PUP-6274
include undef doesn't fail
Change By:
Daniel Parks
{code}❯ puppet apply -e "include undef"Notice: Compiled catalog for zhora.local in environment production in 0.04 secondsNotice: Applied catalog in 0.03 seconds{code}Expected results: compilation failureSimilarly, {{include ''}} doesn't fail, though {{include nosuchclass}} does. Failure on undef would be particularly valuable when including a variable (especially accidently). Example scenario: {{include $::some::class::tyypo}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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-6274) include undef doesn't fail
Title: Message Title Daniel Parks created an issue Puppet / PUP-6274 include undef doesn't fail Issue Type: Bug Affects Versions: PUP 4.4.2 Assignee: Unassigned Created: 2016/05/06 2:18 PM Priority: Normal Reporter: Daniel Parks ❯ puppet apply -e "include undef" Notice: Compiled catalog for zhora.local in environment production in 0.04 seconds Notice: Applied catalog in 0.03 seconds
Jira (FACT-866) pe-facter missing dependency on package providing lsb_release command
Title: Message Title Daniel Parks commented on FACT-866 Re: pe-facter missing dependency on package providing lsb_release command At least on Debian jessie, it should be apt-get install lsb-release (hyphen instead of underscore). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-4480) Jira *very* slow to work with
Title: Message Title Daniel Parks commented on PUP-4480 Re: Jira *very* slow to work with Wow, sorry. I just realized nobody had commented publicly on this since its creation… almost a year ago. I've filed a ticket in our internal JIRA project (JIRA-1156), though I doubt we'll have the time to get to this soon. Sorry. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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.
