On Mon, Sep 22, 2014 at 3:28 PM, Akila Ravihansa Perera
wrote:
> Best approach would be to blockingly wait until
> CompleteTopologyEvent and CompleteTenantEvent are received
>
This seems to be the best option for now.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code
Hi Chamila,
Complete events are meant to be used in a recovery or initialization
process. It should build up the information model using the
CompleteTopologyEvent or CompleteTenantEvent and then only listen to
individual events. Best approach would be to blockingly wait until
CompleteTopologyEvent
CompleteTenantEvent has the list of tenants, however is the order in which
the events are fired reliable? As I understand from the code, a
CompleteTenantEvent is scheduled to fire with a delay, when any one of the
other tenant events could be received before a CompleteTenantEvent.
Regards,
Chamil
Hi Chamila,
Metadata service not yet provide tenant information, it provides properties
of a cluster if an application.
Touched, not typed. Erroneous words are a feature, not a typo.
Hi Lakmal,
Does the metadata service currently provide an endpoint to get the tenant
details?
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Sun, Sep 21, 2014 at 6:44 AM, Lakmal Warusawithana
wrote:
>
>
> On Sat, Sep 20, 2014 at 11:19 PM,
On Sat, Sep 20, 2014 at 11:19 PM, Chamila De Alwis
wrote:
> Hi,
>
> I'm in the process of writing the cartridge agent in Python. When
> executing the extensions on tenant event listeners, specifically
> SubscriptionDomainAddedEvent and SubscriptionDomainRemovedEvent, tenant
> domain name should b
Hi,
I'm in the process of writing the cartridge agent in Python. When executing
the extensions on tenant event listeners, specifically
SubscriptionDomainAddedEvent and SubscriptionDomainRemovedEvent, tenant
domain name should be passed as parameters. Currently CartridgeAgent gets
the tenant inform
