+1 for the idea! There is a good discussion on this topic in StackOverflow:
http://stackoverflow.com/questions/932069/building-a-minimal-plugin-architecture-in-python
On Thu, Nov 27, 2014 at 3:19 PM, Chamila De Alwis wrote:
> +1
>
> I too think we can make the artifact handler plug-gable, aside
+1
I too think we can make the artifact handler plug-gable, aside from the
health stat collector. The common operations can be easily derived from the
existing Git based artifact handler code.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On T
IMO if we are move with the plugin framework , we can use our agent
components (eg health checker, source control handler) as plugins. We can
ship the default cartridge agent with our default plugin set.If the end
user needs they can use their own plugin with their requirement.
AFAIR we may need
+1 for adding plugging framework and extension mechanism to the cartridge
agent. With my little finding, I think Yapsy may good for our requirement.
Also, can we make health checker also pluggable? Please see Shaheed
comments in [1]
[1]Hangout (01) to discuss the Python Agent
On Thu, Nov 27, 201
Hi,
As you may know, Stratos 4.1.0 Alpha release will be shipped with a Python
based cartridge agent. AFAIU, there were two main reasons to move to a
Python based agent.
1. Make it light weight to minimize the memory/CPU footprint. This was
important especially in the Docker scenario.
2. Allow D
