This repository has been archived by the owner on Jul 11, 2022. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[BZ 1069547] Support for API-based bundle handlers
This is to support new type of dedicated bundle handlers able to do more than just file-system modifications. In order to enable them to e.g. connect to some remote endpoint, a more complex configuration data needs to be passed over. This creates coupling between the bundle destination definition and the handler that is able to deploy to such destinations (because it needs to be able to use the configuration offered by the destination definition) but that is unavoidable given the specific things the handlers would be doing. * The resource types can use the new "destination-definition" tag under bundle target to define new type of destinations that can use a "connection string" expression + can pass all or parts of resource or plugin configs or traits to the bundle handler. * The agent-side bundle handlers have access to the bundle deployment configuration even in the purge scenario. This is to support the more complex bundle handlers needing the config to better identify the bundle deployment. * The deploy directory is no longer a required argument when creating a bundle destination. This is because for the API based bundle handlers, such configuration property might not make any sense and would only create confusion on the user side. * It is no longer required for the server bundle plugins to come up with the full list of the required files upon reading the recipe alone. The bundle plugins can therefore choose whether they support piece-wise upload of the bundle version or only support uploading a full bundle distribution file.
- Loading branch information
Showing
19 changed files
with
1,729 additions
and
292 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.