Jira (PUP-9560) Class references in Hiera data: parsing error?
Title: Message Title Henrik Lindberg commented on PUP-9560 Re: Class references in Hiera data: parsing error? Stephen Kenny To be sure - do you see the problem with my example when running it with puppet apply ? I want the code I showed to be the only code you execute, not embedded into something else. This to assert you have a puppet version that does this fundamental thing correctly. Secondly, if a puppet apply does NOT show the error, then put my example as the only logic executed for a node asking for a catalog. Did that work or not? This to assert if there is a difference between apply (which is all Ruby code, and skips one step compared to a server based compilation), and a request to the server (multiple projects, a slightly different code path). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300184.1552566093000.16087.1558508340274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1297) Bolt should raise a nice error if the private key file doesn't exist
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1297 Bolt should raise a nice error if the private key file doesn't exist Change By: Cas Donoghue Fix Version/s: BOLT Next 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307991.1557409042000.15994.1558484880598%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1297) Bolt should raise a nice error if the private key file doesn't exist
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-1297
Bolt should raise a nice error if the private key file doesn't exist
Change By:
Cas Donoghue
Release Notes Summary:
A warning is surfaced when a ssh {{private-key}} specified in config cannot be read.
Release Notes:
Enhancement
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307991.1557409042000.15991.1558484880458%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1324) Add OMI server to docker compose TravisCI specs to test Linux PowerShell
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1324 Add OMI server to docker compose TravisCI specs to test Linux PowerShell Change By: Cas Donoghue Release Notes: Not Needed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309473.1558376887000.15970.1558484340584%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1324) Add OMI server to docker compose TravisCI specs to test Linux PowerShell
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1324 Add OMI server to docker compose TravisCI specs to test Linux PowerShell Change By: Cas Donoghue Fix Version/s: BOLT Next 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309473.1558376887000.15972.1558484340681%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4374) Remove testing workaround for PDB-4373
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4374 Remove testing workaround for PDB-4373 Change By: Zachary Kent Summary: Remove testing work around workaround for PDB-4373 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309645.1558477521000.15727.1558477620846%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4374) Remove testing workaround for PDB-4373
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4374 Remove testing workaround for PDB-4373 Change By: Zachary Kent We added a workaround to our acceptance tests for an issue explained in [PDB-4373|https://tickets.puppetlabs.com/browse/PDB-4373]. Once we've fixed the issue described in that ticket remove this work around workaround . 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309645.1558477521000.15734.1558477621310%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9714) Add support for nested hiera interpolation
Title: Message Title
Nick Bertrand created an issue
Puppet / PUP-9714
Add support for nested hiera interpolation
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2019/05/21 3:26 PM
Priority:
Normal
Reporter:
Nick Bertrand
This commit adds support for two levels of nested hiera interpolations. For example, given a fact called hostgroup with value group1, the following hiera data would have local_users::add::users.root.password set to $6$
---
group1_root_password: $6$
local_users::add::users:
root:
password: '%{lookup("%{facts.hostgroup}_root_password")}'
If this is useful for merging, I would be glad to update any necessary documentation.
Jira (PDB-4374) Remove testing workaround for PDB-4373
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4374 Remove testing workaround for PDB-4373 Change By: Zachary Kent We added a work around workaround to our acceptance tests for an issue explained in [PDB-4373|https://tickets.puppetlabs.com/browse/PDB-4373]. Once we've fixed the issue described in that ticket remove this work around. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309645.1558477521000.15730.1558477620985%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4374) Remove testing work around for PDB-4373
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4374 Remove testing work around for PDB-4373 Issue Type: Bug Assignee: Unassigned Created: 2019/05/21 3:25 PM Priority: Normal Reporter: Zachary Kent We added a work around to our acceptance tests for an issue explained in PDB-4373. Once we've fixed the issue described in that ticket remove this work around. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-1325 Send Puppet logging functions to the outputter Change By: Nick Lewis Assignee: Nick Lewis 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.15384.1558473540359%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1329) Delete task wrapper script before running the task
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-1329 Delete task wrapper script before running the task Issue Type: Improvement Assignee: Unassigned Created: 2019/05/21 12:08 PM Priority: Normal Reporter: Nick Lewis When running a task over SSH with run-as and using the stdin input method, we write a wrapper script to the target that passes the stdin via a heredoc. That means that if the task invocation has sensitive parameters, they are persisted on disk (albeit in a secured temporary file) for the duration of the task run and only cleaned up after it's finished. We should instead make the script self-deleting by making its first line a call to rm /path/to/the/wrapper/script. Since the script will already have been loaded by the shell, we can safely delete it and continue executing. That will significantly reduce the amount of time that parameters exist on disk, as it will only be between the time we write the script and the time we run the script. Add Comment
Jira (BOLT-1270) Bolt should have an encrypted data store
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1270 Bolt should have an encrypted data store Change By: Alex Dreyer Assignee: Nick Maludy Alex Dreyer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306226.1556137243000.14943.1558464000382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-939) Bolt from Homebrew throws errors on command run when using ed25519
Title: Message Title Rosalind Benoit commented on BOLT-939 Re: Bolt from Homebrew throws errors on command run when using ed25519 Cool, will do. Thanks so much for your quick response on this and for directing me on where to go in future!! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281146.1539817138000.14695.1558460101028%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-939) Bolt from Homebrew throws errors on command run when using ed25519
Title: Message Title Cas Donoghue commented on BOLT-939 Re: Bolt from Homebrew throws errors on command run when using ed25519 Unfortunately the only way to use a password protected key with bolt is by adding it to the ssh-agent. The error that is surfaced is horrible. Will see if we can figure out a better message to surface. Thanks so much for the details. Feel free ask questions in #bolt in either the internal puppet slack instance or the public one. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281146.1539817138000.14682.1558459980417%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-939) Bolt from Homebrew throws errors on command run when using ed25519
Title: Message Title Rosalind Benoit commented on BOLT-939 Re: Bolt from Homebrew throws errors on command run when using ed25519 Cas Donoghue NO like an idiot I did not. Added it and it worked...thanks for that. Not that the plan itself worked but that is another realm to troubleshoot altogether. In case it's still helpful, here are my answers: It's RSA. Output: 2048 SHA256:Ez8Psu8ZHBY2mkcZ7/e61NDFyiYm92epT7HZB23HFoY rosalind.benoit@rosalind.benoit-C02LJQ7SFD57 (RSA) Yes I'm using a passphrase on the key. I was wondering if that can create problems for Bolt? 10.14.4 1.18.0 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281146.1539817138000.14666.1558459620394%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1327
Expose r10k proxy configuration option
Change By:
Alex Dreyer
r10k supports a configuration options for proxying connections when downloading moduls. This should be exposed in the bolt configuration as {{ module_proxy noformat }} ? --- puppetfile: http_proxy: "." https_proxy: ".."{{noformat}} questions:What should the configuration option be called?* There should be a new {{puppetfile}} section in config, and this should be called {{proxy}} under that config.
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.
To view this discussion on the w
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1327
Expose r10k proxy configuration option
Change By:
Lucy Wyman
r10k supports a configuration options for proxying connections when downloading moduls. This should be exposed in the bolt configuration as {{module_proxy}}?questions:What should the configuration option be called? * There should be a new {{puppetfile}} section in config, and this should be called {{proxy}} under that config.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309580.1558449511000.14533.1558
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1316 The plan language should have a catch_errors functions Change By: Lucy Wyman 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309066.155804176.14517.1558457820434%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Change By: Lucy Wyman Sprint: Bolt Ready for Grooming 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309580.1558449511000.14519.1558457820527%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Lucy Wyman
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. {{catch_errors}} functions accept a list of types of errors to catch and then a block of code to run where if it errors the plan will continue executing. You cannot specify what to do when an error is raised. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.* If the result was an error then that is raised in the block it will be returned from the block or , otherwise the result will be returned from the block .* A `return` or `break` statement in a catch_errors block should break/return from the block not from the plan. Note: We should have a consistent way of catching returns in lambdas in Puppet - Alex will talk to Henrik about it.* We should document using this with {{case}} to create more reasonable error-handling, where case looks at the result and acts on different types of errors. {noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query()}{noformat}
Add Comment
This message was sent by Atlassian
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Lucy Wyman
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. {{catch_errors}} functions accept a list of types of errors to catch and then a block of code to run where if it errors the plan will continue executing. You cannot specify what to do when an error is raised. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.* If an error is raised in the block it will be returned from the block, otherwise the result will be returned.* A ` {{ return ` }} or ` {{ break ` }} statement in a catch_errors block should break/return from the block not from the plan. Note: We should have a consistent way of catching returns in lambdas in Puppet - Alex will talk to Henrik about it.* We should document using this with {{case}} to create more reasonable error-handling, where case looks at the result and acts on different types of errors. {noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query()}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca9
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Lucy Wyman
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. {{catch_errors}} functions accept a list of types of errors to catch and then a block of code to run where if it errors the plan will continue executing. You cannot specify what to do when an error is raised. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.* If the result was an error then that will be returned from the block or the result will be returned from the block. * A `return` or `break` statement in a catch_errors block should break/return from the block not from the plan. Note: We should have a consistent way of catching returns in lambdas in Puppet - Alex will talk to Henrik about it.* We should document using this with {{case}} to create more reasonable error-handling, where case looks at the result and acts on different types of errors. {noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query()}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Lucy Wyman
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. {{catch_errors}} functions accept a list of types of errors to catch and then a block of code to run where if it errors the plan will continue executing. You cannot specify what to do when an error is raised. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.* If the result was an error then that will be returned from the block* A `return` or `break` statement in a catch_errors block should break/return from the block not from the plan. Note: We should have a consistent way of catching returns in lambdas in Puppet - Alex will talk to Henrik about it. * We should document using this with {{case}} to create more reasonable error-handling, where case looks at the result and acts on different types of errors. {noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query()}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Lucy Wyman
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable.{{catch_errors}} functions accept a list of types of errors to catch and then a block of code to run where if it errors the plan will continue executing. You cannot specify what to do when an error is raised. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.* A `return` or `break` statement in a catch_errors block should break/return from the block not from the plan. Note: We should have a consistent way of catching returns in lambdas in Puppet - Alex will talk to Henrik about it.{noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query()}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Lucy Wyman
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown. * A `return` or `break` statement in a catch_errors block should break/return from the block not from the plan. Note: We should have a consistent way of catching returns in lambdas in Puppet - Alex will talk to Henrik about it. {noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query()}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Alex Dreyer
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.{noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)} query_result_or_error = catch(errors) || { }{ noformat}
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 p
Jira (BOLT-1316) The plan language should have a catch_errors functions
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1316
The plan language should have a catch_errors functions
Change By:
Alex Dreyer
Sometimes a plan wants to execute a series of steps until one step fails then move on to some finalization or clean up actions. This can be handled by writing a subplan and calling {{run_plan}} with {{_catch_errors => true}} but sometimes this is less readable. Proposed solution:A catch_errors function that executes a block of code returning the final value or an Error if one was thrown.{noformat}$result_or_error = catch_errors([kind1, kind2]) ||{ run_task(task1) run_task(task2) run_task(task3)}query_result_or_error = catch(errors) || { puppetdb_query() }{noformat}
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...@g
Jira (BOLT-1325) Send Puppet logging functions to the outputter
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1325 Send Puppet logging functions to the outputter Change By: Lucy Wyman Sprint: Bolt Ready for Grooming 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309516.1558393815000.14457.1558457100165%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1328) AWS inventory discovery integration
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1328 AWS inventory discovery integration Change By: Lucy Wyman Summary: AWS dynamic inventory plugin discovery integration 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309594.1558455992000.14449.1558456920104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1328) AWS inventory discovery integration
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1328 AWS inventory discovery integration Change By: Lucy Wyman Sprint: Bolt Kanban 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309594.1558455992000.14450.1558456920150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1328) AWS dynamic inventory plugin
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-1328
AWS dynamic inventory plugin
Change By:
Lucy Wyman
foo As a user I want to be able to run bolt commands on my EC2 instances without manually adding them to my inventory.We should have an inventory discovery integration that gets targets from AWS.It should only get targets that are EC2 instances.Users should have the ability to filter instances based on:* Tags{code}{code}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309594.1558455992000.14427.1558456740163%40Atl
Jira (BOLT-1328) AWS dynamic inventory plugin
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1328 AWS dynamic inventory plugin Issue Type: Task Assignee: Unassigned Created: 2019/05/21 9:26 AM Priority: Normal Reporter: Lucy Wyman foo Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9566) Allow to send extra headers when requesting a catalog compilation
Title: Message Title Jorie Tappa commented on PUP-9566 Re: Allow to send extra headers when requesting a catalog compilation Hi Nacho Barrientos, this does mean for now we won't be accepting the patch. I'll close the PR and this ticket, and in the case that this gets prioritized and scoped out at some point, we can always reopen the ticket. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300606.1552923936000.14281.1558454822137%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1327) Expose r10k proxy configuration option
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1327 Expose r10k proxy configuration option Issue Type: New Feature Assignee: Unassigned Created: 2019/05/21 7:38 AM Priority: Normal Reporter: Alex Dreyer r10k supports a configuration options for proxying connections when downloading moduls. This should be exposed in the bolt configuration as module_proxy? questions: What should the configuration option be called? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9560) Class references in Hiera data: parsing error?
Title: Message Title Stephen Kenny commented on PUP-9560 Re: Class references in Hiera data: parsing error? Sorry, didn't quote the code snippets properly ... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300184.1552566093000.13917.1558448700949%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-939) Bolt from Homebrew throws errors on command run when using ed25519
Title: Message Title Cas Donoghue commented on BOLT-939 Re: Bolt from Homebrew throws errors on command run when using ed25519 Rosalind Benoit Did you try adding the key to your ssh agent? ssh-add /path/to/key. I am curious some of the other details. 1. Do you know the key type? ssh-keygen -l -f /path/to/key 2. Is the key password protected? 3. What version of macOS? 4. What version of Bolt? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281146.1539817138000.13914.1558448700810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9560) Class references in Hiera data: parsing error?
Title: Message Title
Stephen Kenny commented on PUP-9560
Re: Class references in Hiera data: parsing error?
Finally getting back to this - big apologies for taking so long. First of all, I have to contradict an assertion I made in my original post. I said then that the problem occurred only when I had the file resource data specified in my Hiera data, and that everything was ok if the resource was explicitly defined in the node's manifest (i.e., that in the latter case all was good and it didn't matter if the class name was capitalized or not in the "before =>" attribute). Now, for whatever reason (server & agent updates, or I was simply wrong earlier), I find this is not a correct assertion. I now see behaviour that exactly mirrors my Hiera scenario. That is, in the main manifest, "before => Class[Nfs]" works, but "before => Class[nfs]" fails, with the same error as before: Invalid relationship: File[/primary] { before => Class[nfs] }, because Class[nfs] doesn't seem to be in the catalog I am seeing exactly the same behaviour with your test example: "before => 'Class[Test]" results in a successful agent run; "before => 'Class[test]" fails (with the same kind of error message). My Puppet server and agent versions are 6.3.0 and 6.4.2, respectively. The OS for both server and agent is Debian 9.9. Here are the (failing) code blocks from the node's manifest: file { '/primary': ensure => 'directory', owner => 'root', group => 'root', mode => '0644', before => 'Class[nfs]', } include nfs notify { "goes first": before => 'Class[test]' } include test Thomas Hallgren mentioned producing a stack trace. Attached is the latter part of the output of "puppet agent --test --debug" - if this isn't enough, let me know what would be better - agent-run.debug
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9560) Class references in Hiera data: parsing error?
Title: Message Title Stephen Kenny updated an issue Puppet / PUP-9560 Class references in Hiera data: parsing error? Change By: Stephen Kenny Attachment: agent-run.debug 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300184.1552566093000.13904.1558448580511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
