From my understanding AYON ash worker uses docker images to get the code to run the services.
This is very convenience for deployment. However, it make it a bit difficult to put in some custom code for ASH managed services.
For example, if we want to put additional filter into ayon-ftrack\services\leecher\leecher\listener.py to reduce the workload of the processor, we would have to use the docker container without ASH.
However, one drawback to this method is we can’t manage it via the slick AYON website .
Please advise on any methods that we can customize the code being run by ASH.
As far as I know, ASH has nothing to do about it. it just pulls & runs the docker image we tell it about in the package.py e.g. ayon-ftrack’s services these links are pointing to our images on the docker hub registry. e.g. ftrack leecher.
I think you are looking for developing addon services.
The doc is still in progress but I hope it gives you a starting point.
When developing service, you may run them live from source. and when you are happy about your code, you can then build the docker file, deploy it on the ASH machine, create and upload a new addon and finally create a new service on AYON with the new version of your addon.