Details
-
Task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.8.0
Description
With management packs and stacks being moved out of Ambari's source control, framework components such as upgrade checks and upgrade configuration actions will be to be delivered as part of the 3rd party stack and no long checked into Apache.
However, Ambari does not expose any kind of API/SPI/library for consumers to use when creating their own custom classes. A new maven-compatible project should be created as a home for classes which we expect our 3rd party consumers to use when creating custom plugins to be delivered in their stacks.
They can then compile their code against this API/SPI and deliver a JAR which can be discovered and loaded by Ambari.
Attachments
Issue Links
- links to