Provide task to install AEM service pack

[kwin]

Unfortunately using aem_cms_quickstart_install_fileglob isn't sufficient as you can only install the recent service packs once AEM is fully up and running (and in the best case at least once restarted after installation from scratch).
This is described in https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/release-notes.html?lang=en#install:

Place the package into ../crx-quickstart/install folder when the server is available online
...
Experience Manager 6.5.17.0 does not support Bootstrap installation.

Is there any tasks available which allows to defer placing JARs into the install folder until AEM is fully up and running?

[tobias-richter]

@kwin thanks for your patience :) I am afraid that there is at the moment no task available that will place the JARs into the install folder until AEM is fully up.

But from my point of view it should be no problem to write a small role that will do that after you have applied the wcm_io_devops.aem_cms role.

We are normally using wcm.io.devops CONGA and the wcm_io_devops.conga_aem_cms role (https://github.com/wcm-io-devops/ansible-conga-aem-cms) and wcm_io_devops.conga_aem_packages (https://github.com/wcm-io-devops/ansible-conga-aem-packages) role for installing AEM with all packages + service packs.