My colleagues and I have been biting our tongues trying to get the partitioning right with the slim-packaging-toolkit.
We manage to package the technical add-on from the source code into the tar.gz file and then execute the command to get the packages for the specified workloads, but they don't differ. We have been trying several things regarding the "tasks" and "inputGroups" specification in the app.manifest file, but we can't manage to split the app so that all the python stuff is only in the forwarder partition and none of it is in the searchhead partition to install it via self-service in splunkcloud.
Any kind of help and all materials and resources, apart from the standard documentation, which unfortunately doesn't help much, is very welcome and appreciated.
