Bolt is a Ruby command-line tool for executing commands, scripts, and tasks on
remote systems using SSH and WinRM.
- Executes commands on remote *nix and Windows systems.
- Distributes and execute scripts, such as Bash, PowerShell, Python.
- Scales to more than 1000 concurrent connections.
- Supports industry standard protocols (SSH/SCP, WinRM/PSRP) and
authentication methods (password, publickey).
===> The following configuration options are available for rubygem-bolt-4.0.0:
====> Options available for the single PUPPET: you have to select exactly one of them
PUPPET7=off: Depend on sysutils/puppet7
PUPPET8=on: Depend on sysutils/puppet8
===> Use 'make config' to modify these settings
This port depends on security/rubygem-net-ssh which has stricter defaults that
OpenSSH: when using strict host key checking, security/rubygem-net-ssh will
refuse the connexion if both the remote host name and IP address are not on the
same line of a known_host file.
security/rubygem-net-ssh added support for disabling strict host key checking
in version 5.2.0, however this setting is still enabled by default because
upstream OpenSSH has it enabled by default. However, FreeBSD ships with a
modified version of OpenSSH where strict host key checking is disabled by
default. As a result:
- When adding an entry for a new host, only the host name is added in the
known_host file;
- The absence of CheckHostIP in the SSH configuration means the feature is
disabled while such absence is generally the indication of the feature
being enabled.
As a consequence, host key verification may need additional work:
- When using security/rubygem-net-ssh < 5.2.0, either:
- Disable host key checking totally (--no-host-key-check parameter of the
bolt command);
- Update your remote host entries in the known_hosts file to use the
format:
<host-name>,<IP address> <key-type> <key>
- When using security/rubygem-net-ssh >= 5.2.0
- Add "CheckHostIP no" to your SSH client configuration file
(/etc/ssh/ssh_config or ~/.ssh/config).
Some future version of security/rubygem-net-ssh should drop strict host key
checking entirely, for more details, see:
https://github.com/net-ssh/net-ssh/pull/663
*/*: Deprecate discontinued OSS Puppet components
As announced in the [2025Q4] status report, the legacy ports for Open
Source Puppet (which were abandonned by Perforce following the
aquisition of Puppetlabs), are now deprecated and scheduled for removal
in a few months.
Switching from Puppet to OpenVox is relatively straightforward: when
installing the replacement for a deprecated component, pkg(8) will
detect a conflict between the legacy component and the new one and will
prompt you to remove the deprecated package, which is the right course
of action.
For more details, refer to the [2025Q4] status report.
[2025Q4]: https://www.freebsd.org/status/report-2025-10-2025-12/#_openvox_puppet
With hat: puppet
sysutils/rubygem-openbolt: New port
OpenBolt is an open source orchestration tool that automates the manual work it
takes to maintain your infrastructure. Use OpenBolt to automate tasks that you
perform on an as-needed basis or as part of a greater orchestration workflow.
For example, you can use OpenBolt to patch and update systems, troubleshoot
servers, deploy applications, or stop and restart services. OpenBolt can be
installed on your local workstation and connects directly to remote targets
with SSH or WinRM, so you are not required to install any agent software.
OpenBolt is a community implementation of Puppet Bolt.
With hat: puppet
filesystems: add new category for file systems and related utilities
The filesystems category houses file systems and file system utilities.
It is added mainly to turn the sysutils/fusefs-* pseudo-category into
a proper one, but is also useful for the sundry of other file systems
related ports found in the tree.
Ports that seem like they belong there are moved to the new category.
Two ports, sysutils/fusefs-funionfs and sysutils/fusefs-fusepak are
not moved as they currently don't fetch and don't have TIMESTAMP set
in their distinfo, but that is required to be able to push a rename
of the port by the pre-receive hook.
Approved by: portmgr (rene)
Reviewed by: mat
Pull Request: https://github.com/freebsd/freebsd-ports/pull/302
PR: 281988
sysutils/rubygem-bolt: Add one more patch to fix runtime
The error was only triggered when running plan, and was not experienced
when fixing the port a few hours ago.
With hat: puppet
devel/ruby-gems: Update to 3.5.6
While here, mark textproc/rubygem-nokogumbo as BROKEN because build
fails with clean latest ports tree and all supported ruby versions.
ChangeLog: https://github.com/rubygems/rubygems/blob/v3.5.6/CHANGELOG.md
PR: 276884
Approved by: sunpoet (ruby@, maintainer)
Exp-run by: antoine
Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby
Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk
Notable changes are.
- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.
This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863
I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D37925
sysutils/rubygem-bolt: Relax dependencies
Some dependencies have been updated to versions not in acceptable
ranges. Relax these ranges since Blot seems to work as expected with
these new versions.
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
devel/ruby-gems: Update to 3.3.7
These are fixes Ruby 3.0
Changes were compiled against all dependencies of devel/ruby-gems and
they all built cleanly.
There are five known build failures, all prexisting:
* devel/rubygem-xdg5: requires Ruby 3.0
* devel/rubygem-xdg: requires Ruby 3.1
* graphics/rubygem-objectdetect: port explicitly marked broken
* mail/rubygem-tmail: port explicitly marked broken
* science/cdcl: marked broken, unfetchable
Plus, science/rubygem-ruby-dcl gets skipped because of science/cdcl
PR: 258108
Approved by: ruby (zi@)
Change RUN_DEPENDS from rubygem-terminal-table to rubygem-terminal-table1
- While I'm here, update version requirement of RUN_DEPENDS
- Bump PORTREVISION for dependency change
