Thank you. We will give it a try. Regards
śr., 16 mar 2022 o 11:53 Jean-Baptiste Onofré <[email protected]> napisał(a): > Hi Daniel, > > Most of the time, especially with docker/kubernetes/cloud, people create a > complete full runtime with all features ready to go. Updating one feature > means updating the runtime. > > Personally, I used the update approach quite a lot, and as soon as your > features are "clean" (no circular dep, etc), it works fine (resolver). > > Regards > JB > > On Wed, Mar 16, 2022 at 8:21 AM Daniel Las <[email protected]> wrote: > >> Hi, >> >> Thank you for the quick response. Yes, it is possible, we already tested >> it but I'm curious if somebody else has tried this approach. I'm worried if >> this will impact the resolver in any way like long upgrade time due to the >> larger set of features for dependencies analysis. >> >> Regards >> śr., 16 mar 2022 o 08:12 Jean-Baptiste Onofré <[email protected]> >> napisał(a): >> >>> Hi Daniel >>> >>> Yes that’s possible. You can use feature:install -u (for update) that >>> upgrade a feature from one version to another. >>> >>> Regards >>> JB >>> >>> Le mer. 16 mars 2022 à 06:41, Daniel Las <[email protected]> a >>> écrit : >>> >>>> Hi, >>>> >>>> We are testing provisioning via features. In our case, we are going >>>> to install new custom features version by adding new features repository >>>> into running Karaf instance quite frequently and upgrade selected features. >>>> There will be many versions of the same feature after some time. >>>> >>>> I wonder if this approach is fine or it might cause some problems. >>>> >>>> Regards >>>> -- >>>> Daniel Łaś >>>> >>> >> >> -- >> Daniel Łaś >> > -- Daniel Łaś
