ug: offline-update: Use aklite CLI instead of aklite-offline#887
Merged
kprosise merged 1 commit intofoundriesio:mainfrom Feb 12, 2026
Merged
ug: offline-update: Use aklite CLI instead of aklite-offline#887kprosise merged 1 commit intofoundriesio:mainfrom
kprosise merged 1 commit intofoundriesio:mainfrom
Conversation
5200bdc to
4e44e9f
Compare
kprosise
approved these changes
Feb 11, 2026
Contributor
kprosise
left a comment
There was a problem hiding this comment.
minor suggestions. All vale warnings checked, and can be ignored.
Since v95, aklite CLI has full support for offline updates, and is the preferred method for doing so. It provides better compatibility with online updates behavior, especially in regards to exit codes, and does not require a feature to be enabled in the meta-subscriber-overrides. Signed-off-by: Andre Detsch <andre.detsch@foundries.io>
4e44e9f to
1df134f
Compare
Member
Author
Thanks, applied both suggestions |
Member
Author
|
@kprosise feel free to merge when appropriate. |
angolini
reviewed
Feb 12, 2026
| Make sure to check the :ref:`Offline Update Considerations`. | ||
|
|
||
| .. note:: | ||
| Since LmP v95, offline updates can be applied using the ``aktualizr-lite`` command-line interface, instead of the ``aklite-offline`` utility. |
Collaborator
There was a problem hiding this comment.
@kprosise we have a standard on lmp release, let's at least use bold here
I'm not sure we have this rule in the linter, but would be good to have. Can you, please, handle this?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since v95, aklite CLI has full support for offline updates, and is the preferred method for doing so. It provides better compatibility with online updates behavior, especially in regards to exit codes, and does not require a feature to be enabled in the meta-subscriber-overrides.
PR Template and Checklist
Please complete as much as possible to speed up the reviewing process.
You may delete items that are not relevant to your contribution.
Readiness and adding reviewers as appropriate is required.
All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.
Readiness
Checklist
make linkcheck, and add redirects for any moved or deleted pages.-s, --signoff).-S, --gpg-sign).Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.