Hi and thanks for your response.
Maybe it give another way to deploy my use case.
I try to explain it:
We have a hosted webappikation for each customer with different release version and
then we have for each customer a iot-device in his network. the iot device is for printing, sharing, medical devices, scanning. The iot-device has an connection to the hosted wepapplikation througt a WAF.
On the iot-device runs a exchange service (samba and mounts), a print service( CUPS ), a controller service ( ansible project with cronjob each 5min ) and a wildfly service.
So the samba, print and controller service is for each customer the same. But the wildfly service is custom to the release of the webapplikation. that mean, the release of the webapplikation must be the same as the iot-device.
At this time my solution is, i deploy a empty wildfly service without the applikation (war file).
Then the controller with the ansible project get the config for the device and download the war file
from a webshare. then i use the balenaEngine to deploy the war file in the wildfly service. This works like a charm, but, in future it could be, that we have a wildfly release change and the i must create a new application with a new wildfly release for a certain release.
It would be saver, when i can deploy the hole wildfly container with the war file which fits together.
It would be very cool, when i can controll just one container ( wildfly ) from a device variable and deploy the full application with his specified release version.
At this time this is also possible, when i do not deploy the wildfly application.
The the controller with his ansible project perfom a balena-engine run … my_app:12.03
Works also, but, then i do not see the service in balena and when i deploy a new release, balena will not controll it.
i know, it is possible to pin a releases to a device, but then i must first releasing for each wildfly application and handle each dive with a pin. also when i perform a new release of the other services, i must recreate for each other releases.
maybe you have a good solution for my problem.
it is really important, that we have all automated.
we wont click to much on the balenacloud interface
Thanks a lot