Replies

• 

  ronnyronny@metalhead.club

  Nov 10, 2026, 12:42 PM

  @ascherbaum good part is that you can create venv or rollback quite easily.. but I would suggest to have some test env :)

  💬 1🔄 0⭐ 0
• 

  jon@allmende.io

  Nov 10, 2026, 1:07 PM

  @ronny
  We made good experiences with pinning python and pipx in mise-en-place and then installing ansible-lint and a matching ansible-core version with the pipx: plugin.
  
  Also supports installing additional dependencies for roles or collections from Pypi.
  
  Pinning versions in requirements.yml also renders this much more deterministic.
  
  But I guess there are other side-effects involved, speaking of production.
  @ascherbaum

  💬 0🔄 0⭐ 0
• 

  Andreas Scherbaumascherbaum@mastodon.social

  Nov 10, 2026, 1:13 PM

  @jon @ronny At some point one has to upgrade, or everything gets stuck in a very old #Ansible version. It's still always a game of finding new issues and fix deprecated features.

  💬 1🔄 0⭐ 0
• 

  jon@allmende.io

  Nov 10, 2026, 1:26 PM

  @ascherbaum
  Yes, this migration path is hard in the Ansible model of declarative configuration for imperatively written modules.
  @ronny

  💬 0🔄 0⭐ 0
• 

  Andreas Scherbaumascherbaum@mastodon.social

  Nov 10, 2026, 1:33 PM

  @jon @ronny I just wish that Ansible would not deprecate so many features left and right.

  💬 0🔄 0⭐ 0