... | ... | @@ -90,8 +90,8 @@ By default, entities should provide only admin UI components. But, being built o |
|
|
* Operations combine Tasks into user-facing actions (e.g., InstallCmsSiteOperation).
|
|
|
* Tasks are re-usable within other Operations.
|
|
|
|
|
|
* Distribution
|
|
|
* Platform
|
|
|
* Distribution (entity type?)
|
|
|
* Platform (Distribution bundle?)
|
|
|
* Site
|
|
|
* CmsSite (fieldable entity, that embedding of task entities)
|
|
|
- Drupal7Site
|
... | ... | @@ -99,9 +99,11 @@ By default, entities should provide only admin UI components. But, being built o |
|
|
- Drupal8Site
|
|
|
- WorpPress4Site
|
|
|
- CiviCrmWordPress4Site
|
|
|
* Task
|
|
|
* AnsibleTask
|
|
|
* Task (defines `log` and `result` fields, provides a URL to which to post log output)
|
|
|
* AnsibleTask (parses log output for return code, to update `result` field).
|
|
|
* AnsiblePlatformTask
|
|
|
* AnsibleDeployDrupalPlatformFromGitTask
|
|
|
* AnsibleDeployDrupalPlatformFromDrushMakefileTask
|
|
|
* AnsibleSiteTask
|
|
|
* AnsibleWriteNginxVhostTask
|
|
|
* AnsibleGenerateDrupalSiteBackupTask (implements AcceptsFeedbackTrait, contains a `backup_path` field)
|
... | ... | |