[
https://issues.apache.org/jira/browse/STRATOS-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327131#comment-14327131
]
ASF GitHub Bot commented on STRATOS-1180:
-----------------------------------------
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/234#issuecomment-75016467
Thanks for the pull request @chamilad! It looks good! IMO it would be
better to introduce a packaging model for plugins using zip to make it easier
to distribute and deploy.
> Modify extension execution structure in Python Cartridge Agent
> --------------------------------------------------------------
>
> Key: STRATOS-1180
> URL: https://issues.apache.org/jira/browse/STRATOS-1180
> Project: Stratos
> Issue Type: Task
> Components: Cartridge Agent
> Reporter: Chamila de Alwis
> Fix For: 4.1.0 RC1
>
>
> Currently we have bash scripts as extensions however if we could introduce a
> python extension layer in between that would make it much easier to implement
> extension logic.
> The current extension setup is as follows. A set of bash scripts are
> available in the <PCA_HOME>/extensions. The file name of the extension that
> should be executed for each event is defined in the agent configuration
> (agent.conf in PCA, stratos.sh in JCA). The event handler executes these bash
> scripts as new shell commands when the respective events are received.
> We can introduce a layer between the bash scripts and the python code that
> calls them. The names of the python scripts corresponding to each event can
> be defined as before.
> Additionally we can extend this behavior to the Git artifact management
> component of the PCA. The contract that the artifact management component
> should adhere to is "checkout" and "push". We can separate the current python
> code relating to these two operations in to two extension scripts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
