Hi Nirmal,
Sorry for the late response.
Shall we keep the application alias, but remove the alias validation (we
check if the alias is provided, and if not throw an error) for now, so that
we can deploy applications without it? We can bring back the check once we
generate all aliases based on the
Hi,
In Application json we have application id and alias. Can someone please
explain the rationale behind having two application specific values (AFAIU
both of these are unique for an application?)?
Thanks.
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Seni
Hi Nirmal,
The idea was to generate unique aliases for all subscribables (cartridges +
groups) using the single application alias. However, still the users define
aliases explicitly in the application definition, hence this is not used.
On Wed, Dec 3, 2014 at 2:08 PM, Nirmal Fernando
wrote:
> H
Hi Isuru,
Thanks for the quick response. So, we do not need to define this right? Can
we get rid of this?
On Wed, Dec 3, 2014 at 2:10 PM, Isuru Haththotuwa wrote:
> Hi Nirmal,
>
> The idea was to generate unique aliases for all subscribables (cartridges
> + groups) using the single application
