Skip to content

ug: offline-update: Use aklite CLI instead of aklite-offline#887

Merged
kprosise merged 1 commit intofoundriesio:mainfrom
detsch:detsch-cli-for-offline
Feb 12, 2026
Merged

ug: offline-update: Use aklite CLI instead of aklite-offline#887
kprosise merged 1 commit intofoundriesio:mainfrom
detsch:detsch-cli-for-offline

Conversation

@detsch
Copy link
Member

@detsch detsch commented Feb 9, 2026

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

  • Merge (pending reviews)
  • Merge after date or event
  • Draft

Checklist

  • Run spelling and grammar check, preferably with linter.
  • Step through instructions (or ask someone to do so).
  • Review for wordiness
  • Match tone and style of page/section.
  • Run make linkcheck, and add redirects for any moved or deleted pages.
  • View HTML in a browser to check rendering.
  • Use semantic newlines.
  • follow best practices for commits.
    • Descriptive title written in the imperative.
    • Include brief overview of QA steps taken.
    • Mention any related issues numbers.
    • End message with sign off/DCO line (-s, --signoff).
    • Sign commit with your gpg key (-S, --gpg-sign).
    • Squash commits if needed.
  • Request PR review by a technical writer and at least one peer.

Comments

Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

@detsch detsch force-pushed the detsch-cli-for-offline branch 2 times, most recently from 5200bdc to 4e44e9f Compare February 10, 2026 14:31
@detsch detsch marked this pull request as ready for review February 10, 2026 19:24
@detsch detsch requested a review from vanmaegima February 10, 2026 19:24
Copy link
Contributor

@kprosise kprosise left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
@detsch detsch force-pushed the detsch-cli-for-offline branch from 4e44e9f to 1df134f Compare February 11, 2026 13:21
@detsch
Copy link
Member Author

detsch commented Feb 11, 2026

minor suggestions. All vale warnings checked, and can be ignored.

Thanks, applied both suggestions

Copy link
Member

@vanmaegima vanmaegima left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@detsch
Copy link
Member Author

detsch commented Feb 11, 2026

@kprosise feel free to merge when appropriate.

@kprosise kprosise merged commit 9872170 into foundriesio:main Feb 12, 2026
2 of 3 checks passed
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.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants