Jira (PUP-8939) Administrators are not able to run puppet agent when installed as SYSTEM in some cases
Title: Message Title Glenn Sarti commented on PUP-8939 Re: Administrators are not able to run puppet agent when installed as SYSTEM in some cases Note that the MSI for Puppet 5.5.2+, 5.3.7+ and 1.10.13+ no longer manage file permissions in the settings and rely on the operating system. https://github.com/puppetlabs/puppet-agent/commit/b22df1ae474be73eb936eb563fcecb1e02b5c1ba So for those MSIs this will no longer be an issue. 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-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Glenn Sarti assigned an issue to Unassigned Puppet / PUP-6729 NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Change By: Glenn Sarti Assignee: Glenn Sarti 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-8966) Windows security integration tests fail when the user does not have elevated rights
Title: Message Title Glenn Sarti commented on PUP-8966 Re: Windows security integration tests fail when the user does not have elevated rights This is expected behaviour. Closing won't do. 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-640) Sync code for catalog execution
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-640
Sync code for catalog execution
Change By:
Michael Smith
Before executing a catalog bolt should create a tarball with modules directory structure containing all the lib/ and files/ directories from modules required to In Scope:- Create a plugins tarball with files/ and lib/ directories of modules in autoloader format- Update run_task transport API for winrm and ssh to support uploading extra files. - Update catalog_executor to untar plugins and configure modulepath to use themOut of Scope- Orchestrator transport support- optimizations around saving files- optimizations around persisting plugins for more than one apply- references - such as {{puppet:///tasks/...}} ( - to other mount points. plugins, locales, and pluginfacts are other default mount points, and more can be configured ) - to other mount points .
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you ar
Jira (BOLT-640) Sync code for catalog execution
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-640
Sync code for catalog execution
Change By:
Michael Smith
Before executing a catalog bolt should create a tarball with modules directory structure containing all the lib/ and files/ directories from modules required to In Scope:- Create a plugins tarball with files/ and lib/ directories of modules in autoloader format- Update run_task transport API for winrm and ssh to support uploading extra files. - Update catalog_executor to untar plugins and configure modulepath to use themOut of Scope- Orchestrator transport support- optimizations around saving files- optimizations around persisting plugins for more than one apply- references - such as {{puppet:///tasks/...}} (plugins, locales, and pluginfacts are other default mount points, and more can be configured) - to other mount points.
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
Jira (BOLT-640) Sync code for catalog execution
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-640
Sync code for catalog execution
Change By:
Michael Smith
Before executing a catalog bolt should create a tarball with modules directory structure containing all the lib/ and files/ directories from modules required to In Scope:- Create a plugins tarball with files/ and lib/ directories of modules in autoloader format- Update run_task transport API for winrm and ssh to support uploading extra files. - Update catalog_executor to untar plugins and configure modulepath to use themOut of Scop Scope - Orchestrator transport support- optimizations around saving files- optimizations around persisting plugins for more than one apply - references - such {{puppet:///tasks/...}} to other mount points.
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 (BOLT-581) Evaluate top 100 modules
Title: Message Title Michael Smith commented on BOLT-581 Re: Evaluate top 100 modules Modules using custom facts KyleAnderson-consul-3.3.0 camptocamp-systemd-1.1.1 ec2tagfacts elastic-elasticsearch-6.3.0 elasticsearch-elasticsearch-0.16.2 example42-puppi-2.2.6 ghoneycutt-ssh-3.57.0 jfryman-nginx-999.999.999 locp-cassandra-999.999.999 maestrodev-maven-1.4.0 nanliu-staging-1.0.3 pcfens-filebeat-3.1.0 puppet-archive-3.1.0 puppet-collectd-9.1.0
Jira (PUP-8975) Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-8975
Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data
Change By:
Eric Thompson
rich data has a long tail and possible problems for enabling in platform 6. not the least of which include possibly breaking custom types and providers. issues in puppetdb reports storage. possible facts storage issues (if customers have e.g. facts called {{_ptype}}see if we can do this without rich data and the associated costs until we can get feedback from users.
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.g
Jira (PUP-8975) Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-8975 Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data Change By: Eric Thompson Acceptance Criteria: * Design proposal (or reasons not) for Deferred puppet language type implemented without rich data enabled 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-649) Support run_as as an apply option
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-649 Support run_as as an apply option Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 4:00 PM Priority: Normal Reporter: Alex Dreyer When _run_as => foo is specified as a plan option the plan should be executed as user foo. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-648) Support _catch_errors as an apply option
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-648 Support _catch_errors as an apply option Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 4:00 PM Priority: Normal Reporter: Alex Dreyer Block manifest application should fail the plan unless _catch_errors => true is supplied as an option in which case it should return a failing ResultSet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-647) Support _noop for apply statements
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-647 Support _noop for apply statements Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:58 PM Priority: Normal Reporter: Alex Dreyer When a plan is run in noop mode all block manifest application should be done with noop Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8975) Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data
Title: Message Title Eric Thompson created an issue Puppet / PUP-8975 Agent Functions - Spike: determine if Deferred type can be implemented w/o Rich Data Issue Type: Task Assignee: Unassigned Created: 2018/06/28 3:58 PM Priority: Normal Reporter: Eric Thompson 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.co
Jira (BOLT-641) Update facts plan to support custom facts
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-641 Update facts plan to support custom facts Change By: Alex Dreyer Since the apply statement runs with code from bolts modulepath the facts task should support custom facts on bolts modulepath.In Scope:The facts plan should by default create a tarball of custom facts from bolts modulepath and copy them to the target before running facter.The facts plan should collect puppet agent facts is the puppet agent is present.The facts plan should have a parameter to not copy custom facts to the target.The facts plan does not need to support custom facts over pcp but it should not error by default when targeting pcp nodes.Out of scope:pcp support with multiple file tasks . if it's complicated 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 emai
Jira (BOLT-641) Update facts plan to support custom facts
Title: Message Title Alex Dreyer commented on BOLT-641 Re: Update facts plan to support custom facts the latter 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-646) Migrate bolt_catalog to use PAL
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-646 Migrate bolt_catalog to use PAL Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:55 PM Priority: Normal Reporter: Alex Dreyer Use the work from PUP-8973 to migrate bolt_catalog to use a stable PAL interface In Scope use the stable PAL interface and stop subclassing the compiler Don't break $environment behavior unit tests for bolt_catalog Add Comment
Jira (BOLT-645) Spike: use puppet device modules in a manifest block
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-645 Spike: use puppet device modules in a manifest block Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:52 PM Priority: Normal Reporter: Alex Dreyer Experiment with how a device module could be used from the manifest block How do we replace device.conf with inventory information How do we collect facts How do we apply the catalog Add Comment
Jira (BOLT-644) Collect analytics on catalogs applied with bolt.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-644 Collect analytics on catalogs applied with bolt. Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:50 PM Priority: Normal Reporter: Alex Dreyer We should collect some statistics on what type of catalogs people are applying with bolt 1. How large is the AST? 2. How big is the catalog? 3. How many different non-core types are in the catalog? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-643) Add apply functionality to bolt_shim
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-643 Add apply functionality to bolt_shim Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:49 PM Priority: Normal Reporter: Alex Dreyer the bolt_shim should work with the apply workflow albeit with some confusion around where code comes from compared to tasks. When running tasks over pcp the task on the MoM is used, when running an apply types and providers come from bolts code directory instead. In Scope: Copy providers and files to the target Execute the catalog using copied types and providers. Support custom fact collection over pcp Out of Scope Scalable solution Multiple applies appearing as a single job Using types/providers and facts from the master Allowing tasks to run from bolt
Jira (BOLT-642) Support inventory function during plan compilation
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-642 Support inventory function during plan compilation Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:44 PM Priority: Normal Reporter: Alex Dreyer In order to enable exported resource and puppetdb_query like functionality bolt_catalog should support inspecting other targets in the inventory. In scope: Serialize information about other targets in the inventory and pass it to bolt_catalog Load the inventory into puppet so get_targets, target.facts and target.vars works in plands Do not allow users to set facts or vars on any target from bolt_catalog Add Comment
Jira (BOLT-641) Update facts plan to support custom facts
Title: Message Title Michael Smith commented on BOLT-641 Re: Update facts plan to support custom facts pcp support actually seems pretty straightforward. Are we specifically trying to disable it, or just making it optional if it gets complicated? 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-57) Download a file
Title: Message Title Randell Pelak commented on BOLT-57 Re: Download a file Charlie Sharpsteen yeah, that would be plan A. But if we have a fancy download feature. We aren't at the point we are implementing that part just yet. Our first rev will probably just assume it hasn't changed since we put it there. But it isn't too far out now that we will want to verify that assumption... 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-57) Download a file
Title: Message Title Charlie Sharpsteen commented on BOLT-57 Re: Download a file Randell Pelak For a small text file like pe.conf you could probably execute a task that just echoes the file content to stdout. Then swap it for a download function when that gets created. 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-8807) Package module into puppet-agent
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8807 Package module into puppet-agent Change By: Josh Cooper Assignee: Josh Cooper 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-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-630
PowerShell based tasks throw an error about a non-existant parameter
Change By:
Michael Smith
A user on Slack reported that they were unable to use the WSUS Client tasks because they were getting the following error; {code} Started on localhost...Failed on localhost: The task failed with exit code 1: $private:taskArgs = Get-ContentAsJson ( : System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name '_task'. at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception) at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException { }Failed on 1 node: winrm://localhost{code} I know that those tasks worked fine in Bolt 0.20.5 as that's when I authored them. That error is not within the task itself but within Bolt and is probable related to [ https://github.com/puppetlabs/bolt/commit/9bc85d7a18fdb7d1e7e844c376bb5f42a59cdced ] I have marked this as major as I very strongly suspect all PowerShell based tasks, using cmdlet binding (Which is recommended), will now be failing. Update the PowerShell wrapper that prepares arguments to exclude any that aren't known. This will effectively make parameters that are specified in the metadata but not in the script "ignored", which will be consistent with other input methods (particular environment).Add integration tests that ensure PowerShell scripts with parameters work.
Add Comment
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-630
PowerShell based tasks throw an error about a non-existant parameter
Change By:
Michael Smith
Update the PowerShell wrapper that prepares arguments to exclude any that aren't known. This will effectively make parameters that are specified in the metadata but not in the script "ignored", which will be consistent with other input methods (particular environment).Add integration tests that ensure PowerShell scripts with parameters work. A user on Slack reported that they were unable to use the WSUS Client tasks because they were getting the following error;{code}Started on localhost...Failed on localhost: The task failed with exit code 1: $private:taskArgs = Get-ContentAsJson ( : System.Management.Automation.ParameterBindingException: A parameter cannot be found that matches parameter name '_task'. at System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception) at System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException { }Failed on 1 node: winrm://localhost{code}I know that those tasks worked fine in Bolt 0.20.5 as that's when I authored them. That error is not within the task itself but within Bolt and is probable related to [https://github.com/puppetlabs/bolt/commit/9bc85d7a18fdb7d1e7e844c376bb5f42a59cdced]I have marked this as major as I very strongly suspect all PowerShell based tasks, using cmdlet binding (Which is recommended), will now be failing. Update the PowerShell wrapper that prepares arguments to exclude any that aren't known. This will effectively make parameters that are specified in the metadata but not in the script "ignored", which will be consistent with other input methods (particular environment).Add integration tests that ensure PowerShell scripts with parameters work.
Jira (PUP-8805) Create the CI pipeline
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8805 Create the CI pipeline Change By: Josh Cooper Assignee: Josh Cooper 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-641) Update facts plan to support custom facts
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-641 Update facts plan to support custom facts Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:33 PM Priority: Normal Reporter: Alex Dreyer Since the apply statement runs with code from bolts modulepath the facts task should support custom facts on bolts modulepath. In Scope: The facts plan should by default create a tarball of custom facts from bolts modulepath and copy them to the target before running facter. The facts plan should collect puppet agent facts is the puppet agent is present. The facts plan should have a parameter to not copy custom facts to the target. The facts plan does not need to support custom facts over pcp but it should not error by default when targeting pcp nodes. Out of scope: pcp support with multiple file tasks. Add Comment
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Michael Smith commented on BOLT-633 Re: Configure modulepath for bolt_catalog I'd be tempted to make sure puppetdb_query works with this ticket. Mostly because I already did part of the work. 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-640) Sync code for catalog execution
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-640 Sync code for catalog execution Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:29 PM Priority: Normal Reporter: Alex Dreyer Before executing a catalog bolt should create a tarball with modules directory structure containing all the lib/ and files/ directories from modules required to In Scope: Create a plugins tarball with files/ and lib/ directories of modules in autoloader format Update run_task transport API for winrm and ssh to support uploading extra files. Update catalog_executor to untar plugins and configure modulepath to use them Out of Scop Orchestrator transport support optimizations around saving files optimizations around persisting plugins for more than one apply Add Comment
Jira (BOLT-639) Collect analytics on the usage of the apply statement
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-639 Collect analytics on the usage of the apply statement Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:16 PM Priority: Normal Reporter: Alex Dreyer Bolt should send analytics infromation equivalent to the run_* functions when a manifest block is applied from a plan. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-637) Finalize apply statement
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-637
Finalize apply statement
Change By:
Alex Dreyer
Update Finalize the apply statement to match the decisions made keyword and get it merged into master of puppet. Finalize grammar It should always require {{()}} . Is this a change? It should always require a target Write unit tests
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-637) Finalize apply statement
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-637 Finalize apply statement Change By: Alex Dreyer Summary: Update syntax of Finalize apply statement 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-638) Add apply statement syntax to puppet-specifications
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-638 Add apply statement syntax to puppet-specifications Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:08 PM Priority: Normal Reporter: Alex Dreyer There should be a formal description of the apply statement syntax in puppet-specifications. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-637) Update syntax of apply statement
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-637 Update syntax of apply statement Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 3:07 PM Priority: Normal Reporter: Alex Dreyer Update the apply statement to match the decisions made It should always require () . Is this a change? It should always require a target Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-57) Download a file
Title: Message Title Randell Pelak commented on BOLT-57 Re: Download a file was asked to put my use case in here. For ref arch setup, we expect to be running on a neutral box and setting up a ref arch. But we need to allow it to be done in stages for various reasons. Once we have uploaded the pe.conf to the master in the early stages, if the user stops, and then later runs the later stages, we need to get the pe.conf from the master so that we are sure we are using the latest copy. We may have to modify it and send it back as well, so we need the full contents of the file to avoid losing any helpful comments that anyone/anything may have added. 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-8804) Extract the code & verify the module
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8804 Extract the code & verify the module Change By: Josh Cooper Assignee: Josh Cooper 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-636) Handle logging from catalog compilation
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-636 Handle logging from catalog compilation Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 2:56 PM Priority: Normal Reporter: Alex Dreyer Logging from catalog compilation should be capture in bolts log. This may be acheived by setting up a special logger in bolt_catalog and setting it's log level, parsing log level from it, or by trying to trick puppet into doing structured logging Requirements: It should match bolts log format(ie no log cruft to the console) It should match bolts log level Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-635) Refactor the executor to parallelize multi-target applies
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-635 Refactor the executor to parallelize multi-target applies Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 2:48 PM Priority: Normal Reporter: Alex Dreyer When there are multiple targets for an apply the executor should compile catalogs and execute them in parallel. This will probably require some refactor of the executor. The specifics of this will require some investigation Requirements: hard coded limit on concurrent catalog compilations separate from general concurrency executing the catalog should not use a compilation concurrency slot Feel free to rescope break this up if needed. Add Comment
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Alex Dreyer Sprint: Bolt Ready for Grooming 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-633) Configure modulepath for bolt_catalog
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog Change By: Alex Dreyer Sprint: Bolt Ready for Grooming 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-634) Integration tests for apply functionality
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-634 Integration tests for apply functionality Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 2:41 PM Priority: Normal Reporter: Alex Dreyer There should be a handful of simple integration tests for apply functionality. The install_puppet module can be used to install agent code for these tests. Once this is done new feature work is expected to add integration tests for functionality it adds. In Scope: testing an apply with file resources with content testing an apply with a hiera lookup testing an apply with a class and hiera databinding Out of Scope: testing an apply with a non-core type or provider testing an apply with a puppet:// file source Add Comment
Jira (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Branan Riley commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 Looks like the removal of the word "release" from the file is what broke us: https://github.com/puppetlabs/facter/blob/master/lib/src/facts/linux/os_linux.cc#L290 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-632) Scope for bolt_compile should be set up
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Change By: Alex Dreyer The scope for manifest block compilation should be properly initialized with:From highest to lowest precedence:- facts hash (reserved, so will error if anything attempts to override it)- vars from the plan scope(excluding ephemeral variables like regex matches)- vars from the target- facts from the target$environment should be set if it is present in the plan scope or the target scope otherwise it should be unset.trusted facts should be set so that:- - use host section of target for certname/hostname/domain- - set authenticated: local Objects in the plan scope should be serialized and deserialized with pcore. The following values should not be set:Do not set $servername or other master variables.(maybe settings later)Do not set $server_facts(maybe version is useful? but wait for feature requests )Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-633) Configure modulepath for bolt_catalog
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-633 Configure modulepath for bolt_catalog Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 2:36 PM Priority: Normal Reporter: Alex Dreyer Bolt should pass it's module path to bolt_catalog so functions and types used in both are available In Scope: All modules availabe during plan compilation should be available during catalog compilation The TargetSpec type alias should be set up as well Forbidden functions should error cleanly if called Add Comment
Jira (BOLT-632) Scope for bolt_compile should be set up
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-632 Scope for bolt_compile should be set up Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 2:33 PM Priority: Normal Reporter: Alex Dreyer The scope for manifest block compilation should be properly initialized with: From highest to lowest precedence: facts hash (reserved, so will error if anything attempts to override it) vars from the plan scope(excluding ephemeral variables like regex matches) vars from the target facts from the target $environment should be set if it is present in the plan scope or the target scope otherwise it should be unset. trusted facts should be set so that: - use host section of target for certname/hostname/domain - set authenticated: local The following values should not be set: Do not set $servername or other master variables.(maybe settings later) Do not set $server_facts(maybe version is useful? but wait for feature requests ) Do not set agent facts leave that up to the fact collection step. If we need these we'll have to update the fact collection workflow.
Jira (BOLT-631) Bolt should support hiera configuration and use it when compiling catalogs
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-631 Bolt should support hiera configuration and use it when compiling catalogs Issue Type: New Feature Assignee: Unassigned Created: 2018/06/28 2:27 PM Priority: Normal Reporter: Alex Dreyer When compiling catalogs for apply bolt should configure and use hiera. This data should by default come from the boltdir not the global or user specific puppet path. Requirements: Bolt should allow the hiera config file to be specified with the hiera_config setting If no hiera_config is set the defaults should be $BOLTDIR/hiera.yaml If no datadir is specified in hierconfig the default should be $BOLTDIR/hieradata In Scope reading config values and passing them too bolt catalog successfully using explicit lookups and databindings from a manifest block in configured data using databindings from data in modules Out of scope: using hiera during plan execution hiera_config in inventory
Jira (PUP-8973) PAL API for compiling serialized AST to a catalog
Title: Message Title
Michael Smith created an issue
Puppet / PUP-8973
PAL API for compiling serialized AST to a catalog
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2018/06/28 1:49 PM
Priority:
Normal
Reporter:
Michael Smith
It should generate a whole catalog from the AST, rather then allow interaction with a catalog object. We expect to apply the catalog directly with a custom Ruby script invoking Puppet. Need to be able to
inject variables and facts
specify the modulepath
specify or unset $environment
supply other Puppet overrides, like bolt_pdb_client
Our datatypes need to be exposed. Believe this should work if they're in modules in the modulepath. An initial effort exists at https://github.com/puppetlabs/bolt/blob/8d15b7120c58ecbdbcc6acc55e011b390f57f02d/lib/bolt/catalog.rb. It expects a request formatted as
{ "code_ast": "JSON serialized Puppet AST",
"code_string": "String of code, ignored if AST is provided,
"modulepath": "Array of directories to use as the modulepath for catalog compilation.
Jira (PUP-8972) Update PE to 2018.1.2
Title: Message Title Laura Macchi created an issue Puppet / PUP-8972 Update PE to 2018.1.2 Issue Type: Task Assignee: Unassigned Created: 2018/06/28 12:35 PM Priority: Normal Reporter: Laura Macchi Puppet 2018.1.2 extends the functionality of the code-manager status API. This feature should allow us to troubleshoot code manager issues. Docs: https://puppet.com/docs/pe/2018.1/release_notes/new_features.html#new-features Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Mate Farkas commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 The Docker container image is affected too: amazonlinux:2, amazonlinux:latest The VirtualBox image linked from https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-2-virtual-machine.html#amazon-linux-2-virtual-machine-download is still reporting Amazon Linux release 2 (2017.12) LTS Release Candidate and unaffected. 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title Mate Farkas commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 My estimation was way off, I don't have better things to do at home. /etc/os-release on the affected node: NAME="Amazon Linux" VERSION="2" ID="amzn" ID_LIKE="centos rhel fedora" VERSION_ID="2" PRETTY_NAME="Amazon Linux 2" ANSI_COLOR="0;33" CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2" HOME_URL="https://amazonlinux.com/" The working one, RC for comparison:
Jira (PUP-8947) Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
Title: Message Title Reid Vandewiele commented on PUP-8947 Re: Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters Updated the title and description to reflect that. I don't know of any use cases for Sensitive values that aren't Strings, but if we support it, consistency is appropriate. 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-8947) Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-8947
Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
Change By:
Reid Vandewiele
h2. When Puppet does an Automatic Class Parameter lookup for a class parameter that is of type Sensitive [T] , a String T value being returned should automatically be cast to Sensitive [T] .The use case here is that I store sensitive data in hiera encrypted in eyaml. I have corresponding profiles that have class parameters defined like so:{code:java}class profile::some_profile ( Sensitive[String[1]] $some_sensitive_value,) { # puppet code here}{code}It is currently a significant amount of extra work to mark each hiera entry that is already encrypted as Sensitive; it actually quadruples the number of lines of data in a given yaml file for the first entry and triples it for all subsequent entries because, as of now, you must do this to mark the value as Sensitive:{code:java}---lookup_options: profile::some_profile::some_sensitive_value:convert_to: "Sensitive"profile::some_profile::some_sensitive_value: ENC[PKCS7,encrypted_value_here]{code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8947) Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-8947 Automatically cast ACPL results to Sensitive for Sensitive-typed class parameters Change By: Reid Vandewiele Summary: Automatically cast ACPL String results to Sensitive for Sensitive-typed class parameters 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title Mate Farkas commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 Sorry Branan Riley, I can only do that in the morning. They are closing the office on me. Will share after 10 AM BST. 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-1866) Summer 2018 Facter Bufxixes
Title: Message Title Branan Riley updated an issue Facter / FACT-1866 Summer 2018 Facter Bufxixes Change By: Branan Riley Summary: July Summer 2018 Facter Bufxixes 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-8947) Automatically cast ACPL String results to Sensitive for Sensitive-typed class parameters
Title: Message Title Gene Liverman commented on PUP-8947 Re: Automatically cast ACPL String results to Sensitive for Sensitive-typed class parameters Reid Vandewiele I noticed some changes in title... this isn't limited to strings but also to wrapping the other types too. I believe this includes arrays, hashes, and integers. 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-1866) July 2018 Facter Bufxixes
Title: Message Title Branan Riley created an issue Facter / FACT-1866 July 2018 Facter Bufxixes Issue Type: Epic Assignee: Unassigned Created: 2018/06/28 10:54 AM Fix Versions: FACT 3.11.3 Priority: Normal Reporter: Branan Riley 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
Jira (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Branan Riley commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 A lot of this horribly logic in facter should be replaced by checking for /etc/os-release first whenever possible. Our distro detection logic dates back to well before that was a standard, and it's not pretty. 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title Branan Riley commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 I've been able to reproduce this locally, more or less, on a centos 7.2 machine by messing with various release files. First, I removed /etc/redhat-release, Facter stopped being able to detect it as a CentOS node, and actually called it Amazon linux (our heuristic for Amazon linux is "has a system-release file but not a redhat-release file"). It was still able to pull the correct os release from /etc/system-release, calling this "Amazon 7.2" Next, I removed /etc/system-release, Facter completely gives up and reports the os as "Linux", with the kernel version. Finallyl, I created an empty /etc/system-release. This reproduced the behavior you've reported. Do you mind sharing the contents of /etc/system-release from an affected node? 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title
Mate Farkas commented on FACT-1865
Re: Amazon Linux 2 is reported as 4
Confirmed, AWS changed something between the RC and the final release which broke the version recognition. All AMI ids are from the eu-west-1 (Ireland) region: ami-921423eb amzn2-ami-hvm-2017.12.0.20180509-x86_64-gp2 released on May 10, 2018 at 1:16:51 AM UTC+1 Full release is not 2.0 as expected, but works (systemd is used as default service provider).
"operatingsystem": "Amazon",
"operatingsystemmajrelease": "2",
"operatingsystemrelease": "2",
"os": {
"architecture": "x86_64",
"family": "RedHat",
"hardware": "x86_64",
"name": "Amazon",
"release": {
"full": "2",
"major": "2"
},
"selinux": {
Jira (PDB-3942) Add travis testing for newer jdk to see what happens...
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-3942 Add travis testing for newer jdk to see what happens... Change By: Austin Blatt Assignee: Austin Blatt 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-8947) Automatically cast ACPL String results to Sensitive for Sensitive-typed class parameters
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-8947 Automatically cast ACPL String results to Sensitive for Sensitive-typed class parameters Change By: Reid Vandewiele Summary: Automatically cast ACPL String results to Sensitive (when appropriate) for Sensitive-typed class parameters 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-1865) Amazon Linux 2 is reported as 4
Title: Message Title
Branan Riley created an issue
Facter / FACT-1865
Amazon Linux 2 is reported as 4
Issue Type:
Bug
Affects Versions:
FACT 3.11.2
Assignee:
Unassigned
Created:
2018/06/28 10:11 AM
Fix Versions:
FACT 3.11.3
Labels:
amazon amazon_linux aws
Priority:
Normal
Reporter:
Branan Riley
Facter 3.11.2 shipped with puppet-agent-5.5.3-1.el7 is reporting the following facts:
"operatingsystem": "Amazon",
"operatingsystemmajrelease": "4", <- Note this
"operatingsystemrelease": "4.14.47-64.38.amzn2.x86_64",
"os": {
Jira (FACT-1865) Amazon Linux 2 is reported as 4
Title: Message Title Branan Riley commented on FACT-1865 Re: Amazon Linux 2 is reported as 4 Originally reported by Mate Farkas in PA-2103 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-581) Evaluate top 100 modules
Title: Message Title Michael Smith commented on BOLT-581 Re: Evaluate top 100 modules Followup question: if we don't sync over custom facts and providers, how many modules would still work? 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-581) Evaluate top 100 modules
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-581 Evaluate top 100 modules Change By: David Kramer Assignee: Michael Smith 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-8971) Agent Functions - Add encrypt/decrypt functions
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-8971
Agent Functions - Add encrypt/decrypt functions
Issue Type:
New Feature
Assignee:
Henrik Lindberg
Created:
2018/06/28 10:03 AM
Fix Versions:
PUP 5.5.z
Priority:
Normal
Reporter:
Henrik Lindberg
For users that do not use a separate secrets server (yet) but want to improve the security of their puppet installation it is of value to provide the ability to encrypt data so it can only be read by the node the catalog is compiled for. The pattern is to call encrypt when compiling a catalog, and to call decrypt using a Deferred. Example usage:
some_class(Sensitive $password) {
some_resource { 'example':
password => Deferred('decrypt', encrypt($password))
}
}
Jira (PUP-8947) Automatically cast ACPL String results to Sensitive (when appropriate)
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-8947 Automatically cast ACPL String results to Sensitive (when appropriate) Change By: Reid Vandewiele Summary: Automatically cast ACPL String results to Sensitive ( when appropriate ) 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-8947) Automatically cast ACPL String results to Sensitive when appropriate
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-8947 Automatically cast ACPL String results to Sensitive when appropriate Change By: Reid Vandewiele Summary: Automatically cast ACPL String results to Sensitive when appropriate 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-8947) Automatically cast ACPL String results to Sensitive
Title: Message Title
Reid Vandewiele updated an issue
Puppet / PUP-8947
Automatically cast ACPL String results to Sensitive
Change By:
Reid Vandewiele
h2. When Puppet does an Automatic Class Parameter lookup for a class parameter that is of type Sensitive, a String value being returned should automatically be cast to Sensitive.The use case here is that I store sensitive data in hiera encrypted in eyaml. I have corresponding profiles that have class parameters defined like so:{code:java}class profile::some_profile ( Sensitive[String[1]] $some_sensitive_value,) { # puppet code here}{code}It is currently a significant amount of extra work to mark each hiera entry that is already encrypted as Sensitive; it actually quadruples the number of lines of data in a given yaml file for the first entry and triples it for all subsequent entries because, as of now, you must do this to mark the value as Sensitive:{code:java}---lookup_options: profile::some_profile::some_sensitive_value:convert_to: "Sensitive"profile::some_profile::some_sensitive_value: ENC[PKCS7,encrypted_value_here]{code} As a bonus, I think it would be ideal if all eyaml encrypted values were returned as Sensitive automatically, regardless of how they were looked up. I have proposed this idea in PUP-8946. That ticket does not negate this one as someone may have unencrypted values in hiera that they still want use for Sensitive class parameters and the like.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8947) Automatically cast ACPL String results to Sensitive
Title: Message Title Reid Vandewiele updated an issue Puppet / PUP-8947 Automatically cast ACPL String results to Sensitive Change By: Reid Vandewiele Summary: Automatically cast ACPL String results to Sensitive when returning a string to a lookup for a Sensitive type 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-8373) Lookup CLI should use RBAC token if available for PuppetDB
Title: Message Title Michael Smith commented on PUP-8373 Re: Lookup CLI should use RBAC token if available for PuppetDB Also, Bolt has implemented the PuppetDB client at https://github.com/puppetlabs/bolt/tree/master/lib/bolt/puppetdb. Seems like an opportunity for a new gem. 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-8373) Lookup CLI should use RBAC token if available for PuppetDB
Title: Message Title Sean Millichamp commented on PUP-8373 Re: Lookup CLI should use RBAC token if available for PuppetDB In my implementation I'm reading the global puppet-query configuration file as well as the per-user configuration file (/.puppetlabs/client-tools/puppetdb.conf) and I'm currently only using the per-user token file in /.puppetlabs/token, though I can't rule out that I might want to use something in, say, a CI job where I'd want to pass a token path somehow. But I'm not tackling that for this first version I'm working on. 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-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Michael Smith commented on BOLT-630 Re: PowerShell based tasks throw an error about a non-existant parameter It could make sense to make _task and other new meta-parameters an opt-in behavior. That's currently true for the other example, _noop. 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-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-630 PowerShell based tasks throw an error about a non-existant parameter Change By: Michael Smith Affects Version/s: BOLT 0.21.0 Affects Version/s: BOLT 0.20.7 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-8031) Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass
Title: Message Title Henrik Lindberg assigned an issue to Thomas Speigner Puppet / PUP-8031 Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass Change By: Henrik Lindberg Assignee: Thomas Speigner 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-8031) Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass
Title: Message Title Henrik Lindberg commented on PUP-8031 Re: Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass This is expected behavior. A module only has access to the modules it depends on, and that all dependencies are met. The bad dependency here is impossible to satisfy. The error message is not nice though. I would like to see the stack trace for the error "Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass" that is in the title. Thomas Speigner can you paste that into a comment here? 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-8373) Lookup CLI should use RBAC token if available for PuppetDB
Title: Message Title Michael Smith commented on PUP-8373 Re: Lookup CLI should use RBAC token if available for PuppetDB On a PE master, the puppet-query configuration (pe-client-tools) lives at /etc/puppetlabs/client-tools/puppetdb.conf. Is there a problem with using that location for each user? If you want the login token to be shared by all users on the system (potentially a larger security concern, as that token may have more than just PuppetDB permissions) you would need to set the token-file location and make that file readable by all users. Otherwise, each user can use the shared config but will need to separately login via puppet-access, and their token file will be stored in a user directory. 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-8031) Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass
Title: Message Title
Henrik Lindberg commented on PUP-8031
Re: Evaluation Error: Error while evaluating a Function Call, undefined method `include?' for nil:NilClass
init.pp
class mymodule {
notice('help me with this problem') # Function that it will fail on
}
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 a
Jira (PDB-3954) Test PR looking at upgrade testing
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3954 Test PR looking at upgrade testing Issue Type: Bug Assignee: Unassigned Created: 2018/06/28 9:09 AM Priority: Normal Reporter: gepetto-bot 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/grou
Jira (BOLT-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Michael Smith commented on BOLT-630 Re: PowerShell based tasks throw an error about a non-existant parameter The powershell-specific testing seems to be lacking in general, something should've used parameters and caught both this and the previous ticket around default input method. 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-630) PowerShell based tasks throw an error about a non-existant parameter
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-630 PowerShell based tasks throw an error about a non-existant parameter Change By: Michael Smith Sprint: Bolt Kanban 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-8373) Lookup CLI should use RBAC token if available for PuppetDB
Title: Message Title Sean Millichamp commented on PUP-8373 Re: Lookup CLI should use RBAC token if available for PuppetDB I am in the process of implementing a custom internal facts indirector for PuppetDB with RBAC along with a custom version of "lookup" to basically solve this for our site and as part of this there are a couple of more aspects to it that I hadn't considered originally. My overarching outcome from getting this ticket implemented as I originally outlined was so that any non-root user could invoke "puppet lookup" with a RBAC token granting them access to PuppetDB (which as a non-root user they of course otherwise wouldn't have even on a Puppetmaster due to lack of permissions on the node's private key), pointed to an environment with a hiera configuration they could read so that the values would be correctly interpolated and resolved as they would during a root-based "puppet lookup". However, in addition to the token I found that I needed a PuppetDB configuration as well. As a non-root user it was trying to read my configurations from ~/.puppetlabs/etc/puppet. In my setup I have ended up looking for and reading the same configuration files that the pe-client-tools uses. Setting configuration per-user in ~/.puppetlabs/etc/puppet and leveraging the normal Puppet PuppetDB indirector configuration was a non-starter, the command needed to just work for an arbitrary user on the system with a token. While just implementing support for the PE RBAC token would be a step in the right direction, I'm not sure how it would be useful without also providing support for more of the whole end-to-end I've described. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
