The community.sap_libs collection looks unmaintained / abandoned, it has:
On the other hand, there has been a reaction on Validate compatibility with ansible-core 2.19.
But considering everything, this collection doesn’t look healthy or really alive to me.
There’s also GitHub · Where software is built it looks like pyrfc, one of its requirements, is no longer maintained (GitHub - SAP-archive/PyRFC: Asynchronous, non-blocking SAP NW RFC SDK bindings for Python). That only affects slightly over half of the modules though, everything else might be unaffected.
@rainer pinging you since you’ve been involved with the collection. (I’m not sure whether marcelmamula (Marcel Mamula) · GitHub is on the forum as well.)
Additionally, they don’t test with ansible-core 2.19. This is a violation of our requirements.
I’ve opened a PR about this.
@mariolenz @felixfontein I just signed up here.
I have merged all open PRs and closed those not applicable. Also did some cleanup with dev/main branches with mergeback.
CI action is now enabled and I am working on fixing errors. Sanity tests are fixed but I am having issue resolving units tests because ansible-community/ansible-test-gh-action@release/v1 loads all pythons for given ansible-core version, which does not make sense to load 3.8 for 2.19.
Is there parameter to force specific version like for Integration tests with target-python-version?
Thanks for improving the collection!
Why doesn’t it make sense? Ansible-core 2.19 supports Python 3.8 on targets.
@felixfontein @mariolenz Release 1.5.0 was completed now. Thank you for your patience and let me know if you need more from us to cancel your abandonment process.
FYI I have reworked CI to add more combinations and non-EOL vs EOL split to give us more information.