+1 for validating it in the service deployment as well. Do we have a
validation against the alias for startupOrder which defined in the service
group when deploying application?
Thanks,
Reka
On Mon, May 11, 2015 at 4:45 PM, Isuru Haththotuwa
wrote:
> Fixed in commit b0ef0ccf3491610cf5fbec10b40e
Fixed in commit b0ef0ccf3491610cf5fbec10b40e955fa31823d3.
On Mon, May 11, 2015 at 2:33 PM, Udara Liyanage wrote:
> +1
>
> On Mon, May 11, 2015 at 2:05 PM, Isuru Haththotuwa
> wrote:
>
>> Hi Devs,
>>
>> In [1, 2], we have code explicitly depending on two prefixes used for
>> startup order and sc
+1
On Mon, May 11, 2015 at 2:05 PM, Isuru Haththotuwa
wrote:
> Hi Devs,
>
> In [1, 2], we have code explicitly depending on two prefixes used for
> startup order and scaling order, *'cartridge.*' and '*group.'* .IMHO we
> should validate this at Service Group deployment time, since otherwise
> s
Hi Devs,
In [1, 2], we have code explicitly depending on two prefixes used for
startup order and scaling order, *'cartridge.*' and '*group.'* .IMHO we
should validate this at Service Group deployment time, since otherwise
startup order / scaling will not work as expected. Currently its possible
to
