When building a MicrocksContainersEnsemble including the async features (withAsyncFeatures()), the async minion container image is automatically deduced from the main container image name. As of today, the microcks-uber part of image is replace by microcks-uber-async-minion, leaving the tag unchanged.
This way of doing things is broker when you use the -native suffix tagged image as there is no microcks-uber-async-minion:nightly-native, for example. Just a microcks-uber-async-minion:nightly.
Description
While we don't have a -native image for async minion, we should also take care of removing the specific -native suffix from image tag.
Reason/Context
When building a
MicrocksContainersEnsembleincluding the async features (withAsyncFeatures()), the async minion container image is automatically deduced from the main container image name. As of today, themicrocks-uberpart of image is replace bymicrocks-uber-async-minion, leaving the tag unchanged.This way of doing things is broker when you use the
-nativesuffix tagged image as there is nomicrocks-uber-async-minion:nightly-native, for example. Just amicrocks-uber-async-minion:nightly.Description
While we don't have a
-nativeimage for async minion, we should also take care of removing the specific-nativesuffix from image tag.Implementation ideas
No response