Status: Closed - No Change
Fix Version/s: 4.1
Sprint:Cloudify 4.0 - Sprint 15, Cloudify 4.0 - Sprint RC, Cloudify 4.0 - Sprint GA, Cloudify 4.1 Sprint 1
The main path for using Cloudify plugins is by uploading them as wagons to the manager (cfy plugins upload...).
The current behavior is that on deployment creation, if the required plugins are not available on the manager, plugins with a source URL will be installed from source.
Installation from source may require system dependencies (e.g. gcc, python-devel) which are not installed on the manager's machine.
The error message in such cases is only available by getting the "create_deployment_environment" execution logs which is not straightforward.
In order to provide a better user experience, the create deployment API should accept a "allow-plugins-installation-from-source" which will be set to "false" by default.
The user experience will be as follows:
- On deployment creation, if a required plugin is not installed on the manager, the user will get an error message saying the user should either upload the required plugin or use the "allow-plugins-installation-from-source" flag.
- On deployment creation with the flag set to "true", print a message saying that plugin installation from source result can be viewed by getting the "create_deployment_environment" logs.