[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Dynamic pluggability of touchpoints to the provisionig process ?
- From: "Yousouf, Shenol" <s.yousouf@xxxxxxx>
- Date: Wed, 19 Oct 2011 18:53:45 +0200
- Accept-language: en-US, de-DE
- Acceptlanguage: en-US, de-DE
- Delivered-to: email@example.com
- Thread-index: AcyOf6odaBX6hV1oRlGkWtYh1eAaTQ==
- Thread-topic: Dynamic pluggability of touchpoints to the provisionig process ?
In my scenario, I have a p2 installation tool (p2 director of the sort) which provisions another system. Assume that I have a repository with my own custom touchpoint and bundles, published with actions, recognized by it. Is it possible
to plug dynamically the touchpoint to the provisioning process and execute the custom actions for the bundles, that go to the remote system, with one installation ?
To clarify a little bit more: Our use cases rely heavily on p2 provisioning and we would like to clear the possible security holes. If such scenario is possible for, say, specially constructed update sites, this could lead to some
unexpected results. Imagine that you install a feature, which turns out to contain a touchpoint + some bundles with actions, intended for it. If the new touchpoint can plug into the provisioning process at an early stage, it will execute the actions for the
other bundles, which, on turn, can execute malicious code or do other nasty things.
I have some vague memories that p2 supports some kind of “self-provisioning of the provisioning process” itself, which motivated me to direct this question to the mailing list, but it could be just my imagination. J
Thanks and regards,
SAP Labs Bulgaria