sap_swpm: Argument list can be too long when setting file permissions about community.sap_install HOT 4 CLOSED

We could just skip all the *extracted* directories when setting file permissions and ownership. At the time when the file and directory permissions are set by the role, permissions and ownership only of files which are not already extracted will have to be modified.

from community.sap_install.

@berndfinger I would suggest different approach. It is easier to create batches of 100 files and run them in loop.

This is short example I made for test, which splits into batches of 3:

  vars:
    file_input: "fileA fileB fileC fileD fileE fileF fileG fileX"
  tasks:
    - name: Assign file_input into file_list
      ansible.builtin.set_fact:
        file_list: "{{ file_input.split(' ') }}"

    - name: Show file_list in loop per batch
      ansible.builtin.debug:
        msg: "{{ item | join(' ') }}"
      loop: "{{ file_list | batch(3) }}"
      loop_control:
        label: "Batch {{ (file_list.index(item[0]) // 3) + 1 }}"

TASK [Show file_list in loop per batch] *********************************************************************************************************************
ok: [localhost] => (item=Batch 1) => {
    "msg": "fileA fileB fileC"
}
ok: [localhost] => (item=Batch 2) => {
    "msg": "fileD fileE fileF"
}
ok: [localhost] => (item=Batch 3) => {
    "msg": "fileG fileX"
}

from community.sap_install.

@marcelmamula Nice idea, thanks! I tested with a batch size of 100, a directory name of length 100, and several 1000 files with a 22 character file name. I would still skip the extracted directories, as there should never be any need to change owners and permissions of extracted files.

from community.sap_install.

Solved in #735.

from community.sap_install.