Hi Isuru,
Are you asking about the user providing a prefix for the group that can be used
to generate subscription aliases on a per cartridge basis? If so, why not just
use the group name as the prefix if there can be only one Application? If you
want to allow for more, then include the app name too:
/app/grp/cartridge/subscription
Or similar. Or did I misunderstand?
Thanks, Shaheed
From: Martin Eppel (meppel)
Sent: 07 July 2014 08:16
To: Isuru Haththotuwa; dev
Subject: RE: Composite Application Deployment and Subscription - Single Alias
for a Group
HI Isuru,
I agree, what about using the cartridge type ?
If we have a single alias for each group do you mean for each cartridge type or
for all cartridges, independently of the cartridge type of them (The question
then would be how would we define our dependencies) ?
Thanks
Martin
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Isuru
Haththotuwa
Sent: Thursday, July 03, 2014 8:58 PM
To: dev
Cc: Martin Eppel (meppel)
Subject: Composite Application Deployment and Subscription - Single Alias for a
Group
Hi Devs,
Currently, in the proposed Composite Application Definition, a unique alias
must be specified by the user for all cartridges. This can be quite cumbersome.
To simplify this, can we have a single alias for each Group? Stratos can
generate aliases for individual cartridges in the Group using that unique alias
provided, and track them. WDYT?
--
Thanks and Regards,
Isuru H.
