<div class="container">
<h1>Recommended update for aws-cli-cmd, flake-pilot</h1>
<table class="table table-striped table-bordered">
<tbody>
<tr>
<th>Announcement ID:</th>
<td>SUSE-RU-2026:20630-1</td>
</tr>
<tr>
<th>Release Date:</th>
<td>2026-03-04T09:00:03Z</td>
</tr>
<tr>
<th>Rating:</th>
<td>moderate</td>
</tr>
<tr>
<th>References:</th>
<td>
<ul>
</ul>
</td>
</tr>
<tr>
<th>Affected Products:</th>
<td>
<ul class="list-group">
<li class="list-group-item">SUSE Linux Enterprise Server 16.0</li>
<li class="list-group-item">SUSE Linux Enterprise Server for SAP Applications 16.0</li>
</ul>
</td>
</tr>
</tbody>
</table>
<p>An update that can now be installed.</p>
<h2>Description:</h2>
<p>This update for aws-cli-cmd, flake-pilot fixes the following issues:</p>
<p>Changes in aws-cli-cmd:</p>
<ul>
<li>Fix install/upgrade/removal:
* With the release of flake-pilot 3.1.27 a force option
for registration and deregistration has been added.
* This allows for a simpler registration processing in the spec file of the -cmd package.
* This commit adds registration and deregistration helper scripts and calls them as part
of the spec pre/post processing macros.
* The macro setup makes sure:
1. The flake gets registered as %post install action
2. The flake gets deregistered as %preun uninstall (no upgrade) action
* With regards to the already released package and the
existing macro code the following applies:
* The %postun code from the old package runs after the %post code
of the new package and only in upgrade mode. This would harm the
registration which is the reason why we again call register_aws
in %posttrans which is the last action of the entire transaction
and ensures the registration will be effective.</li>
</ul>
<p>Changes in flake-pilot:</p>
<ul>
<li>Bump version: from 3.1.26 to 3.1.27:<ul>
<li>Add support for --force option for remove:
Add support for podman remove --force mode. In this mode the referenced application
will be force removed and no sanity checks if this is pointing to a flake registration will be done.</li>
<li>Fix spec file:
Allow to build for Fedora, fix packager e-mail</li>
</ul>
</li>
<li>Bump version: from 3.1.25 to 3.1.26:<ul>
<li>Allow force registration with arbitrary data
When using --force also register even if the eventually
conflicting file does not belong to a flake registration</li>
<li>Add --force option for register command
Allow to force writing the registration even if a registration
of the same name already exists. Also update the man pages.</li>
</ul>
</li>
<li>Bump version: from 3.1.24 to 3.1.25:<ul>
<li>Improve command debug log:
Make sure the command called is part of the log message and not only the arguments</li>
<li>drop obsolete permission settings:
With the proper user vs. system wide setup there is no need for the hacky permission adaptions.</li>
<li>Fixup flake lookup:
system wide first, then user specific</li>
<li>Fix podman remove for both workloads:
Make sure podman remove functions properly when called in system and/or user mode.
Sanity checks must be performed before any file/directory removal starts.</li>
<li>Add flake-ctl podman --user ... option</li>
<li>Update documentation:
Add information how to setup for rootless mode</li>
<li>Allow user specific podman storage location</li>
<li>Allow user specific flake config file:
By default and if the calling user is root the setup
of the flakes directory and other settings are read fromb/etc/flakes.yml.</li>
<li>Fix typo in storage conf</li>
<li>Update README:
Fix repo names and update use case list</li>
<li>Fix image prune for local containers</li>
</ul>
</li>
<li>Bump version: from 3.1.23 to 3.1.24:<ul>
<li>Clippy fixes:
Avoid unneeded unwrap</li>
<li>Use pull policy set to: newer</li>
</ul>
</li>
<li>Bump version: from 3.1.22 to 3.1.23:<ul>
<li>Improve error handling</li>
<li>Better error handling for config_from_str()</li>
<li>Use derive statement for Writeback</li>
<li>Add information about potential firewall conflicts</li>
</ul>
</li>
</ul>
<h2>Patch Instructions:</h2>
<p>
To install this SUSE update use the SUSE recommended
installation methods like YaST online_update or "zypper patch".<br/>
Alternatively you can run the command listed for your product:
</p>
<ul class="list-group">
<li class="list-group-item">
SUSE Linux Enterprise Server 16.0
<br/>
<code>zypper in -t patch SUSE-SLES-16.0-348=1</code>
</li>
<li class="list-group-item">
SUSE Linux Enterprise Server for SAP Applications 16.0
<br/>
<code>zypper in -t patch SUSE-SLES-16.0-348=1</code>
</li>
</ul>
<h2>Package List:</h2>
<ul>
<li>
SUSE Linux Enterprise Server 16.0 (noarch)
<ul>
<li>aws-cli-cmd-1.36.2-160000.4.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server 16.0 (aarch64 ppc64le s390x x86_64)
<ul>
<li>flake-pilot-podman-3.1.27-160000.1.1</li>
<li>flake-pilot-3.1.27-160000.1.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server 16.0 (aarch64 s390x x86_64)
<ul>
<li>flake-pilot-debuginfo-3.1.27-160000.1.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server for SAP Applications 16.0 (noarch)
<ul>
<li>aws-cli-cmd-1.36.2-160000.4.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server for SAP Applications 16.0 (ppc64le x86_64)
<ul>
<li>flake-pilot-podman-3.1.27-160000.1.1</li>
<li>flake-pilot-3.1.27-160000.1.1</li>
</ul>
</li>
<li>
SUSE Linux Enterprise Server for SAP Applications 16.0 (x86_64)
<ul>
<li>flake-pilot-debuginfo-3.1.27-160000.1.1</li>
</ul>
</li>
</ul>
</div>