[Puppet Users] Bolt 2.31.0 is now available

[Puppet Product Updates]

VERSION 2.31.0

*in this release*
📝 *Help the Bolt team improve our documentation!*

   - The UX team at Puppet has put together an interactive survey designed
   to test our documentation structure. The survey consists of 8 questions and
   should take just a few minutes to complete. If you would like to
help out, take
   the survey . Your feedback will help us
   improve our docs!


✨  *new features*

   - You can now easily check if a target is in an inventory file with the
   bolt inventory show and Get-BoltInventory commands. These commands now
   indicate which targets could not be found in the inventory, shows which
   inventory file was loaded, and lists the number of inventory targets and
   adhoc targets. To see how to use these commands, see *nix shell commands
   

and PowerShell cmdlets
   

   .
   - The bolt module add and Add-BoltModule commands now show the changes
   adding a module will make to the generated Puppetfile, including any
   modules that were added, removed, upgraded, or downgraded. To learn more
   about managing modules in Bolt, see Managing modules in Bolt projects
   .
   - Several modules that ship with Bolt packages have been updated to
   their latest versions.
  - facts 1.1.0 
  - augeas_core 1.1.1 
  - scheduled_task 2.2.1
  
  - sshkeys_core 2.1.0
  
  - zfs_core 1.1.0 
  - cron_core 1.0.4 
  - yumrepo_core 1.0.7
  
  - package 1.3.0 
  - stdlib 6.5.0 


🔧  *bug fixes*

   - Bolt now logs when it tried but failed to load the default inventory
   file for the project. Previously, Bolt would log that it had loaded the
   default inventory file, even when the file does not exist.
   - Puppetfiles generated with bolt module install and
   Install-BoltModule commands now include the moduledir directive.
   Previously, only the bolt module add and Add-BoltModule commands would
   generate a Puppetfile with this directive.


📗  *documentation*

   - The Using plugins
    and Writing
   plugins  pages
   have been revamped, and a new Supported plugins
    page has
   been added that lists all of Bolt's supported modules.
   - A new PowerShell cmdlets
    reference
   page has been added.


VIEW FULL RELEASE NOTES


*in the works*

   - Work continues on adding parallelism to plans. Our next step is to
   refine the proof of concept and test against expected use cases.
   - Work continues on adding Git module support to the new module
   management feature.
   - Work continues on updating the *Getting started with Bolt* guide to
   simplify the setup process and make clarifications based on user feedback.

*nuts and bolts*

Each month, we'll highlight a different Bolt feature and cover the details
of what it is, why you might want to use it, and how it can be used in your
workflows.

October's highlighted feature is: *module management*!

*What is the module management feature?*

Starting with Bolt 2.30.0, Bolt can manage your project's module
dependencies for you. By adding your project's direct dependencies to the
project configuration file, Bolt will be able to resolve all transitive
dependencies and version requirements, generate a Puppetfile, and install
the modules.


*Why should I have Bolt manage my project's modules?*

Using the module management feature greatly simplifies the process of
installing and adding new modules to your project. Instead of needing to
locate all of a module's dependencies, find compatible versions for each
module, and manually updating your Puppetfile, you can offload this work to
Bolt. All you need to do is list the modules you care about in your project
configuration file and Bolt will take care of the rest!


*How do I start managing my project's modules with Bolt?*

To have Bolt manage your project's module dependencies, you'll need to
enable the feature by updating your project. We've made this process easy
by updating the bolt project migrate command and
Update-BoltProject Powershell cmdlet, whic

[Puppet Users] Puppet errors on Fedora 33 RC1

[Michael Watters]

There appears to be an issue with the puppet agent on Fedora 33 RC1.  
Running the agent against a test environment results in errors as follows.  
Does anybody know how to resolve this?  

Info: Using configured environment 'dev27_f33'
Info: Retrieving pluginfacts
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not 
retrieve information from environment f33_test source(s) 
puppet:///pluginfacts
ce: /File[/var/lib/puppet/facts.d/puppet_vendor.sh]: Dependency 
File[/var/lib/puppet/facts.d] has failures: true
Warning: /File[/var/lib/puppet/facts.d/puppet_vendor.sh]: Skipping because 
of failed dependencies
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve 
information from environment dev27_f33 source(s) puppet:///plugins
ce: /File[/var/lib/puppet/lib/facter]: Dependency File[/var/lib/puppet/lib] 
has failures: true
Warning: /File[/var/lib/puppet/lib/facter]: Skipping because of failed 
dependencies

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a5cb13e2-e148-48a3-a2cf-93c884c3f068n%40googlegroups.com.