As it looks like we have taken this long path to send repository
information to the instance because we needed to send the encrypted
password and secret separately.

I think we need to preserve this and fix Instance Status listener logic.

On Fri, Jan 2, 2015 at 9:52 PM, Imesh Gunaratne <im...@apache.org> wrote:

> Hi Devs,
>
> This is regarding $subject. In the latest codebase git clone does not work
> in agent.
>
> I did some investigations on this logic and found that it has worked
> earlier when cartridge subscriptions were managed by Stratos Manager (SM).
> When an Instance Started event is received by SM, it query the
> subscriptions connected to the given cluster and send Artifact Updated
> event for each subscription.
>
> Now with service grouping, subscriptions are no longer managed by SM. As a
> result this flow does not work.
>
> The question is do we need to take a such a long path to execute the Git
> clone operation? Agent could execute it as soon after sending the Instance
> Started event. WDYT?
>
> Thanks
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>



-- 
Imesh Gunaratne

Technical Lead, WSO2
Committer & PMC Member, Apache Stratos

Reply via email to