https://github.com/bircher/drupal-deploy_hook
proof of concept drupal module to address workflow issues needing https://www.drupal.org/project/drupal/issues/2901418
https://github.com/bircher/drupal-deploy_hook
Last synced: over 1 year ago
JSON representation
proof of concept drupal module to address workflow issues needing https://www.drupal.org/project/drupal/issues/2901418
- Host: GitHub
- URL: https://github.com/bircher/drupal-deploy_hook
- Owner: bircher
- Created: 2020-03-17T17:36:11.000Z (over 6 years ago)
- Default Branch: 8.x-1.x
- Last Pushed: 2020-03-18T10:34:52.000Z (over 6 years ago)
- Last Synced: 2025-02-10T11:09:32.859Z (over 1 year ago)
- Language: PHP
- Size: 2.93 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# deploy_hook
proof of concept drupal module to address workflow issues needing https://www.drupal.org/project/drupal/issues/2901418
@todo: update readme!
### tldr:
Create `hook_deploy_NAME` update hooks in `mymodule.deploy.php` the same way you do with post_update hooks.
Then run `drush deploy-hook:run` to run all deploy hooks that have not been run yet.
ie the sequence becomes
```
drush updb -y
drush cim -y
drush deploy-hook:run -y # it currently doesn't ask for confirmation yet
```
All aspects of this including module name and drush command names are up for debate, feedback welcome!