in this release |
✨ new features |
- Tasks can now return a _sensitive key in their output, which can contain any arbitrary value. Any value under this key will be treated sensitively by Bolt, preventing it from being printed to the console or logged at any log level. Sensitive task output can be accessed from a Result object in a plan using the sensitive() function. To learn more about the _sensitive key, see Writing tasks.
- Log files can now be disabled in configuration by setting a log's value to disable. This can be used to disable logs that are configured at the user- or system-wide levels, or to disable the default bolt-debug.log file. To learn more about configuring log files in Bolt, see bolt-project.yaml options or bolt-defaults.yaml options.
- Bolt packages are now available for Fedora 32.
|
| VIEW FULL RELEASE NOTES |
|
|
in the works |
- Work continues on understanding the source of performance issues when running Bolt on Windows and macOS, and the different solutions we can implement to help improve performance.
- Work continues on reworking our documentation to be clearer and more detailed.
- Work continues on reducing the amount of time Bolt takes to install on Windows using the Bolt MSI.
- Bolt will soon be able to handle cases where a project directory does not exist more gracefully.
- Bolt will soon ship with a task for making HTTP requests.
|
|
|
nuts and bolts |
Each month, we'll highlight a different Bolt feature and cover the details on what it is, why you might want to use it, and how it can be used in your workflows.
August's highlighted feature is: Bolt projects! | What is a Bolt project? A Bolt project is a directory that serves as the launching point for Bolt and allows you to create a shareable orchestration application that members of your team can quickly start using. Bolt projects contain all of the configuration and content relevant to your project, including the inventory file and content such as tasks and plans.
Why should I use a Bolt project?
Bolt projects make it easier to manage your Bolt project and can be utilized by other tools that use Bolt content. Additionally, Bolt projects enable several features that benefit both project authors and project consumers. - Content allowlists
Project authors can specify an allowlist for both tasks and plans in their project's configuration, limiting which tasks and plans appear in the user interface.
- Project-level content
Project authors can quickly develop Bolt and Puppet content in the project directory without the need to create a module, speeding up the process of writing new tasks, plans, and manifests.
- Generate new plans
Projects enable the bolt plan new command, which will create a new plan in the project's plans directory.
How do I create a Bolt project?
To create a new Bolt project, all you need to do is create a file named
bolt-project.yaml in your project directory and give your project a name by setting the name key in the file.
You can also have Bolt create a Bolt project for you by running the
bolt project init command in Unix shells or the New-BoltProject command in PowerShell. |
|
| VIEW THE DOCUMENTATION |
|
|
|
|
|
