Jira (PUP-10542) Generate AST for apply blocks with 0 statements
Title: Message Title Lucy Wyman created an issue Puppet / PUP-10542 Generate AST for apply blocks with 0 statements Issue Type: Task Assignee: Unassigned Created: 2020/06/11 9:06 AM Priority: Normal Reporter: Lucy Wyman Generating the AST for Bolt plan apply blocks currently only handles cases where there's at least one statement in the block. We should create a Model::BlockExpression for apply blocks with zero statements to avoid empty blocks raising an error. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-5073) shellquote() function incorrectly escaping exclamation marks for bash argument usage
Title: Message Title Josh Cooper commented on PUP-5073 Re: shellquote() function incorrectly escaping exclamation marks for bash argument usage Seems like we should be using Shellwords.escape instead of implementing it ourselves. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.94961.1440522495000.84990.1591889220135%40Atlassian.JIRA.
Jira (PUP-5302) composite namevars not taken into account in prefetch
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5302 composite namevars not taken into account in prefetch Change By: Josh Cooper Labels: composite-namevars Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.100302.1443716824000.84979.1591888680036%40Atlassian.JIRA.
Jira (PUP-6770) Method #uniqueness_key computes different results for the same resource.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6770 Method #uniqueness_key computes different results for the same resource. Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.154858.1475584735000.84980.1591888680079%40Atlassian.JIRA.
Jira (PUP-8260) Using eval_generate with a compound name_vars without a name appears to not work
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8260 Using eval_generate with a compound name_vars without a name appears to not work Change By: Josh Cooper Labels: composite-namevars Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.227033.1513578517000.84978.1591888620243%40Atlassian.JIRA.
Jira (PUP-9370) Could not evaluate: ADSI connection error: failed to parse display name
Title: Message Title Aaron Gilbert commented on PUP-9370 Re: Could not evaluate: ADSI connection error: failed to parse display name I ran into the same issue in my environment. I didn't even realize I had an account in Active Directory that had the same name as the local accounts I've been using until I attempted to manage that account on a new system with Puppet. That aside, I see the same error as stated by Paul: ADSI connection error: failed to parse display name of moniker `WinNT://./srvradmin,user' HRESULT error code:0x800708ad The user name could not be found. Wrapped exception: failed to parse display name of moniker `WinNT://./srvradmin,user' HRESULT error code:0x800708ad The user name could not be found. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (PUP-9370) Could not evaluate: ADSI connection error: failed to parse display name
Title: Message Title Aaron Gilbert commented on PUP-9370 Re: Could not evaluate: ADSI connection error: failed to parse display name I ran into the same issue in my environment. I didn't even realize I had an account in Active Directory that had the same name as the local accounts I've been using until I attempted to manage that account on a new system with Puppet. That aside, I see the same error as stated by Paul: ADSI connection error: failed to parse display name of moniker `WinNT://./srvradmin,user' HRESULT error code:0x800708ad The user name could not be found. Wrapped exception: failed to parse display name of moniker `WinNT://./srvradmin,user' HRESULT error code:0x800708ad The user name could not be found. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (PUP-8110) Certificate signing request using sha384, sha512 spec test fail
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8110 Certificate signing request using sha384, sha512 spec test fail Change By: Josh Cooper Epic Link: PUP-9341 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.219777.1509482382000.84976.1591888620155%40Atlassian.JIRA.
Jira (PUP-9370) Could not evaluate: ADSI connection error: failed to parse display name
Title: Message Title Aaron Gilbert updated an issue Puppet / PUP-9370 Could not evaluate: ADSI connection error: failed to parse display name Change By: Aaron Gilbert Comment: I ran into the same issue in my environment. I didn't even realize I had an account in Active Directory that had the same name as the local accounts I've been using until I attempted to manage that account on a new system with Puppet. That aside, I see the same error as stated by Paul:|ADSI connection error: failed to parse display name of moniker `WinNT://./srvradmin,user'HRESULT error code:0x800708adThe user name could not be found.Wrapped exception:failed to parse display name of moniker `WinNT://./srvradmin,user'HRESULT error code:0x800708adThe user name could not be found.| Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.289482.154525563.84977.1591888620199%40Atlassian.JIRA.
Jira (PUP-5302) composite namevars not taken into account in prefetch
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5302 composite namevars not taken into account in prefetch Change By: Josh Cooper Summary: composite namevar namevars not taker taken into account in prefetch . Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.100302.1443716824000.84971.1591888380132%40Atlassian.JIRA.
Jira (FACT-2662) Fix test that mock subject
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2662 Fix test that mock subject Change By: Oana Tanasoiu Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362569.1591885291000.84961.1591887000120%40Atlassian.JIRA.
Jira (FACT-2662) Fix test that mock subject
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2662 Fix test that mock subject Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362569.1591885291000.84960.159188765%40Atlassian.JIRA.
Jira (FACT-2662) Fix test that mock subject
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2662
Fix test that mock subject
Change By:
Bogdan Irimie
{code}spec/custom_facts/core/execution/fact_manager_spec.rb:83:7: C: RSpec/SubjectStub: Do not stub methods of the object under test. [12|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:12] expect(executor).to receive(:with_env).with('LC_ALL' => 'C', 'LANG' => 'C') [13|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:13] ^^^ [14|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:14]spec/custom_facts/core/execution/fact_manager_spec.rb:89:7: C: RSpec/SubjectStub: Do not stub methods of the object under test. [15|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:15] expect(executor).to receive(:expand_command).with('foo').and_return '/bin/foo' [16|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:16] ^^ [17|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:17]spec/custom_facts/core/execution/fact_manager_spec.rb:152:9: C: RSpec/SubjectStub: Do not stub methods of the object under test. [18|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:18] allow(executor).to receive(:expand_command).with('foo').and_return(nil) [19|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:19] ^^^ [20|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:20]spec/custom_facts/core/execution/fact_manager_spec.rb:157:9: C: RSpec/SubjectStub: Do not stub methods of the object under test. [21|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:21] allow(executor).to receive(:expand_command).with('foo').and_return(nil) [22|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:22] ^^^ [23|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:23]spec/custom_facts/core/execution/fact_manager_spec.rb:165:9: C: RSpec/SubjectStub: Do not stub methods of the object under test. [24|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:24] allow(executor).to receive(:expand_command).with('foo').and_return('/bin/foo') [25|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:25] ^^ [26|https://github.com/puppetlabs/facter-ng/pull/549/checks?check_run_id=761883097#step:5:26]spec/custom_facts/core/execution/fact_manager_spec.rb:179:7: C: RSpec/SubjectStub: Do not stub methods of the
Jira (FACT-2662) Fix test that mock subject
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2662 Fix test that mock subject Issue Type: Task Assignee: Unassigned Created: 2020/06/11 7:21 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2658) Migrate facter-ng to facter repo
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2658 Migrate facter-ng to facter repo Change By: Gheorghe Popescu We should migrate [facter-ng|https://github.com/puppetlabs/facter-ng] repo to [facter|https://github.com/puppetlabs/facter] on a new branch (e.g 4.x) - create git orphan branch: create a git orphan branch: https://gist.github.com/jaredhowland/f20564a0a875a278f67d25117f055342 - push facter 4 to the new branch [~ciprian.badescu] might help us on this Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362553.1591869876000.84874.1591876680025%40Atlassian.JIRA.
Jira (FACT-2659) Create next branch on puppet agent
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2659 Create next branch on puppet agent Change By: Gheorghe Popescu In order to prepare for Puppet 7, we should create a new branch (next) that will use Facter 4 as default and remove Facter 3 and facter-ng.- create a git orphan puppet-agent next branch : https://gist.github.com/jaredhowland/f20564a0a875a278f67d25117f055342 form puppet-agent master - move facter-ng build process to facter- remove facter-ng component [~ciprian.badescu] and [~gabriel.nagy] might help us on this Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362554.1591870066000.84873.1591876620032%40Atlassian.JIRA.
Jira (FACT-2659) Create next branch on puppet agent
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2659 Create next branch on puppet agent Change By: Gheorghe Popescu In order to prepare for Puppet 7, we should create a new branch (next) that will use Facter 4 as default and remove Facter 3 and facter-ng. - create a git orphan branch: https://gist.github.com/jaredhowland/f20564a0a875a278f67d25117f055342- move facter-ng build process to facter- remove facter-ng component [~ciprian.badescu] and [~gabriel.nagy] might help us on this Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362554.1591870066000.84872.1591876560151%40Atlassian.JIRA.
Jira (FACT-2661) Add puppet-agent next to puppet-agent pipelines
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2661 Add puppet-agent next to puppet-agent pipelines Change By: Gheorghe Popescu Create a new pipeline for puppet-agent next similar to: https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/puppet-agent.yaml#L412-L429 that has:* PE promotions disabled* p_release_stream: puppet-next(?)* puppet-runtime-master needs to be promoted also on this branchCreate a puppet-agent component pipeline for the new Facter 4 branch:https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/puppet-agent.yaml#L677-L700TBD: - will we ship nightly packages? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2661) Add puppet-agent next to puppet-agent pipelines
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2661 Add puppet-agent next to puppet-agent pipelines Change By: Gheorghe Popescu Create a new config pipeline for puppet ` -agent next ` branch similar to: https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/puppet-agent.yaml#L412-L429 that should has : * disable promotion to PE promotions disabled * disable promotions p_release_stream: puppet-next (?) * remove Facter 3 and facter-ng from puppet- agent runtime-master needs to be promoted also on this branch * add Facter 4 as Create a replacement puppet-agent component pipeline for the new Facter 3 4 branch: [ https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/puppet-agent.yaml ] #L677-L700TBD: - will we ship nightly packages? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (FACT-2661) Add puppet-agent next to puppet-agent pipelines
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2661 Add puppet-agent next to puppet-agent pipelines Change By: Gheorghe Popescu Summary: Create ci-job-config for Add puppet -agent next to puppet-agent pipelines Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362557.1591870805000.84865.1591875420032%40Atlassian.JIRA.
Jira (FACT-2661) Create ci-job-config for puppet next
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2661 Create ci-job-config for puppet next Change By: Bogdan Irimie Create a new config for puppet `next` branch that should: * disable promotion to PE * disable promotions (?) * remove Facter 3 and facter-ng from puppet-agent * add Facter 4 as a replacement for Facter 3 [https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/projects/puppet-agent.yaml] Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.362557.1591870805000.84851.1591871220162%40Atlassian.JIRA.
Jira (FACT-2661) Create ci-job-config for puppet next
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2661 Create ci-job-config for puppet next Issue Type: Task Assignee: Unassigned Created: 2020/06/11 3:20 AM Priority: Normal Reporter: Bogdan Irimie Create a new config for puppet `next` branch that should: disable promotion to PE disable promotions remove Facter 3 and facter-ng from puppet-agent add Facter 4 as a replacement for Facter 3 Add Comment
Jira (FACT-2660) Add acceptance test to Facter 4.x branch
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2660 Add acceptance test to Facter 4.x branch Issue Type: Task Assignee: Unassigned Created: 2020/06/11 3:09 AM Priority: Normal Reporter: Bogdan Irimie Add existent acceptance test from Facter 3 to Facter 4.x branch (once facter-ng is moved to facter repo) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2659) Create next branch on puppet agent
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2659 Create next branch on puppet agent Issue Type: Task Assignee: Unassigned Created: 2020/06/11 3:07 AM Priority: Normal Reporter: Bogdan Irimie In order to prepare for Puppet 7, we should create a new branch (next) that will use Facter 4 as default and remove Facter 3 and facter-ng. Ciprian Badescu and Gabriel Nagy might help us on this Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2658) Migrate facter-ng to facter repo
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2658 Migrate facter-ng to facter repo Issue Type: Task Assignee: Unassigned Created: 2020/06/11 3:04 AM Priority: Normal Reporter: Bogdan Irimie We should migrate facter-ng repo to facter on a new branch (e.g 4.x) Ciprian Badescu might help us on this Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-4548) Extend tests/reports/finalized_on_cycle.rb to Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4548 Extend tests/reports/finalized_on_cycle.rb to Windows Change By: Josh Cooper Epic Link: PUP-9341 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.79339.1431109115000.84785.1591859280061%40Atlassian.JIRA.
Jira (PUP-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6040 "puppet facts" outputs indirector object instead of simple fact list Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.120497.1457515964000.84779.1591858920031%40Atlassian.JIRA.
Jira (PUP-9820) managing a File user or group or mode breaks require on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9820 managing a File user or group or mode breaks require on Windows Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.316149.1562868793000.84778.1591858740025%40Atlassian.JIRA.
Jira (PUP-9304) Puppet::Util::Execution.execute does not have binary-safe stdinfile support
Title: Message Title Josh Cooper commented on PUP-9304 Re: Puppet::Util::Execution.execute does not have binary-safe stdinfile support This is related to PUP-9559 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.284259.1541616996000.84776.1591858260025%40Atlassian.JIRA.
Jira (PUP-4406) Corrupt /etc/shadow entry when password hash contains newline
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4406 Corrupt /etc/shadow entry when password hash contains newline Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.75834.1428999528000.84775.1591858200028%40Atlassian.JIRA.
Jira (PUP-10019) file resource checks source even if the file exists and replace is false
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10019 file resource checks source even if the file exists and replace is false Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.324690.1568400128000.84774.1591858020026%40Atlassian.JIRA.
Jira (PUP-3381) directoryservice provider creates users with low ids
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3381 directoryservice provider creates users with low ids Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.53405.1412273812000.84773.1591857960095%40Atlassian.JIRA.
Jira (PUP-3381) directoryservice provider creates users with low ids
Title: Message Title Josh Cooper commented on PUP-3381 Re: directoryservice provider creates users with low ids Next steps, the provider should use the system parameter to determine whether to create the first available uid, or the first available uid greater than or equal to 500. See https://github.com/puppetlabs/puppet/pull/1944#issuecomment-28415314. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.53405.1412273812000.84772.1591857960039%40Atlassian.JIRA.
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4045 Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.69478.1424944721000.84771.1591857480031%40Atlassian.JIRA.
Jira (PUP-3380) OpenBSD package method function "get_version" does not work with source parameter
Title: Message Title Josh Cooper commented on PUP-3380 Re: OpenBSD package method function "get_version" does not work with source parameter I'm going to close this due to lack of activity. Feel free to reopen if you want to look into what it would take to solve this issue. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.53244.1412237765000.84769.1591857060028%40Atlassian.JIRA.
Jira (PUP-1534) Puppet classes should be able to declare that they are internal
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1534 Puppet classes should be able to declare that they are internal Change By: Josh Cooper Epic Link: PUP-523 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.24845.1390980091000.84768.1591856940030%40Atlassian.JIRA.
Jira (PUP-6591) Recurse option on nested directories silently omits files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6591 Recurse option on nested directories silently omits files Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.145806.1470683287000.84767.1591856880027%40Atlassian.JIRA.
Jira (PUP-1043) Remove ability to specify file checksum in `content` property
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1043 Remove ability to specify file checksum in `content` property Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.21361.1387191736000.84766.1591856820032%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Josh Cooper Epic Link: PUP-7803 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.252196.1527017522000.84763.1591856760055%40Atlassian.JIRA.
Jira (PUP-9140) File resource checksum => mtime fails with empty mtime
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9140 File resource checksum => mtime fails with empty mtime Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.275714.1536928866000.84765.1591856760155%40Atlassian.JIRA.
Jira (PUP-8770) Puppet resource service status should be more than binary
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8770 Puppet resource service status should be more than binary Change By: Josh Cooper Team: Coremunity Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.252196.1527017522000.84764.1591856760111%40Atlassian.JIRA.
Jira (PUP-8346) File type content attribute accepts non-strings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8346 File type content attribute accepts non-strings Change By: Josh Cooper Epic Link: PUP-7548 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.230166.1515705131000.84762.1591856640029%40Atlassian.JIRA.
Jira (PUP-9559) Puppet's Uniquefile doesn't open files in binary mode
Title: Message Title Josh Cooper commented on PUP-9559 Re: Puppet's Uniquefile doesn't open files in binary mode File::BINARY is defined to be 0, so adding the constant above does nothing. The real problem is that Uniquefile defaults to mode w+, so calling replace_file containing windows line endings will cause \n to be replaced with \r\n. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.300170.1552553148000.84761.1591856220022%40Atlassian.JIRA.
