Incorrect behaviour in case of nonexisting SAR file

[machacekondra]

Summary

When you pass nonexisting sar file the module should exit with reasonable error message, rather then "already unpacked".

Issue Type

Bug Report

Component Name

sapcar_extract

Ansible Version

$ ansible --version
2.12

Community.sap Version

$ ansible-galaxy collection list community.sap

latest

Configuration

$ ansible-config dump --only-changed

OS / Environment

No response

Steps to Reproduce

- name: Unpack SAR files
  community.sap.sapcar_extract:
    path: "dontexists.sar"
    dest: "dontexists-extracted"

Expected Results

Return code, so I know the file can't be extracted

Actual Results

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[rainerleber]

Hi @machacekondra thank you for opening this issue.
At first:
This collection is deprecated, not maintained anymore and superseded by the collection community.sap_libs

Could you please open the issue at the new place ? I will take care of it in the "new" collection.