Slack Notify with Drush Site Audit on Deploy #77
Conversation
This file contains hidden or 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
…jis display as well.
* @todo: Duplicate to HipChat * This is implemented as a separate script, didn't want to assume everyone would ALWAYS want to run the site audit. Also this report is quite verbose, so I think people should opt-in if they want to pollute their Slack channel. * This is grouped under /slack_notification example, but could be arguably moved to it's own example as drush_site_audit or something similar. Concern there is duplicating Slack notification markup further. Makes me think a slack_helper.php would be easier to include basic functionality across multiple scripts/quicksilver workflow tasks.
…c-pro Update New Relic Deploy Logs
Also pretty things up a little bit.
Site and Multidev Creation
…w-hooks Add new hooks to Slack example README
- Nested DOCROOT (web_root) - protected_web_paths - php_version New Quicksilver Hooks: * Site creation (deploy_product) * Multidev creation (create_cloud_development_environment) Hold for release
…-site-configuration-new-quicksilver-hooks Add new features to example.pantheon.yml
typo fix Updating yml example title fix
…eon-systems#87) * Add Solr Power indexing on multidev creation example * Repost schema before indexing * Clarify WordPress for this example * Remove duplicate directory
…elly-patch-1 Update slack_notification.php
…rsion Add drush_version to example.pantheon.yml
…pdex * Set Apdex T values on multidev creation * Closes pantheon-systems#86
Fix spelling of "snippet" in new_relic_deploy
fixing a minor typo in description
Specifying a channel can mean the default one from the webhook isn't used. Also link to some spiffy new docs they have.
…jis display as well.
* @todo: Duplicate to HipChat * This is implemented as a separate script, didn't want to assume everyone would ALWAYS want to run the site audit. Also this report is quite verbose, so I think people should opt-in if they want to pollute their Slack channel. * This is grouped under /slack_notification example, but could be arguably moved to it's own example as drush_site_audit or something similar. Concern there is duplicating Slack notification markup further. Makes me think a slack_helper.php would be easier to include basic functionality across multiple scripts/quicksilver workflow tasks.
…silver-examples into site-audit-on-deploy * 'site-audit-on-deploy' of github.com:jordan8037310/quicksilver-examples: Drush Site Audit on deploy. Slack Attachments Title should really be set per-case 'Title' uses better formatting than pretext in Slack Attachments. Emojis display as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Drush Site Audit on deploy.
PS - Thanks to conversation with @JessiFischer this week at DrupalCon—this seemed worthwhile to implement & make sure no mistakes were made post-deploy for some of our sites.