From 743c7e90806a2eaa8e73b08026bb12207050b5a6 Mon Sep 17 00:00:00 2001 From: tkokev Date: Thu, 7 Jun 2018 11:48:38 -0400 Subject: [PATCH 01/16] Update SLACK.md --- slack/SLACK.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 1470410..63fb771 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -4,4 +4,7 @@ This demo builds on the "Versioning Demo" in README.md of this repo. If you have WORK IN PROGRESS. CHECK BACK LATER. -https://api.slack.com/internal-integrations +* Type of integration + * [Internal Integration](https://api.slack.com/internal-integrations) +* Method + * [Webhooks](https://api.slack.com/incoming-webhooks#sending_messages) From 6c9df8dd986a6b11a59786be91b4071038cf1635 Mon Sep 17 00:00:00 2001 From: tkokev Date: Thu, 7 Jun 2018 15:40:57 -0400 Subject: [PATCH 02/16] Update SLACK.md --- slack/SLACK.md | 1 + 1 file changed, 1 insertion(+) diff --git a/slack/SLACK.md b/slack/SLACK.md index 63fb771..4d62c2a 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -8,3 +8,4 @@ WORK IN PROGRESS. CHECK BACK LATER. * [Internal Integration](https://api.slack.com/internal-integrations) * Method * [Webhooks](https://api.slack.com/incoming-webhooks#sending_messages) + * curl -X POST -H 'Content-type: application/json' --data @slack/message.json https://hooks.slack.com/services/ From 5feaca26ffab1cdcf9c92cc29c11a5d640d14b5d Mon Sep 17 00:00:00 2001 From: tkokev Date: Thu, 7 Jun 2018 17:05:05 -0400 Subject: [PATCH 03/16] Update SLACK.md --- slack/SLACK.md | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 4d62c2a..f2209fc 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -1,6 +1,8 @@ # CodePipeline Slack Integration Demo -This demo builds on the "Versioning Demo" in README.md of this repo. If you haven't already performed the steps captured in README.md, do so now. They must be completed prior to continuing on with this demo. +NOTE: This demo builds on the "Versioning Demo" in README.md of this repo. If you haven't already performed the steps captured in README.md, do so now. They must be completed prior to continuing on with this demo. + +App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. WORK IN PROGRESS. CHECK BACK LATER. @@ -9,3 +11,22 @@ WORK IN PROGRESS. CHECK BACK LATER. * Method * [Webhooks](https://api.slack.com/incoming-webhooks#sending_messages) * curl -X POST -H 'Content-type: application/json' --data @slack/message.json https://hooks.slack.com/services/ + +1. Using a web browser, log in to a Slack workspace where your pipeline will send messages +2. Browse to https://api.slack.com +3. Select the option to create a New App + 1. Name = pipeline +1. Select `Incoming Webhooks` and enable it +1. Select `Add new webhook to workspace` +1. Choose a channel and select `Authorize` +1. Take down your webhook URL +1. Test your webhook using the message.json file in this repo by issuing the command below from a development workstation +``` +curl -X POST -H 'Content-type: application/json' --data @message.json https://hooks.slack.com/services/ +``` + +You should see the contents of `message.json` show up within in your Slack channel! + +Now lets update the Appspec file from this repo to include a new `AfterInstall` step that will send build specific information into your teams slack channel for alerting when new deploys have rolled out. + +WORK IN PROGRESS. CHECK BACK LATER. From 3aa679c03ef248530003316edcd027d84d32f769 Mon Sep 17 00:00:00 2001 From: tkokev Date: Thu, 7 Jun 2018 17:06:07 -0400 Subject: [PATCH 04/16] Update SLACK.md --- slack/SLACK.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index f2209fc..185c6a0 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -6,11 +6,11 @@ App Developers & Testers can benefit from gettings a "heads up" notification tha WORK IN PROGRESS. CHECK BACK LATER. +Some facts about how we'll be interacting with Slack. * Type of integration * [Internal Integration](https://api.slack.com/internal-integrations) * Method * [Webhooks](https://api.slack.com/incoming-webhooks#sending_messages) - * curl -X POST -H 'Content-type: application/json' --data @slack/message.json https://hooks.slack.com/services/ 1. Using a web browser, log in to a Slack workspace where your pipeline will send messages 2. Browse to https://api.slack.com From 9c8779d830ab54a01b362e4a37e71c09ae832d85 Mon Sep 17 00:00:00 2001 From: tkokev Date: Fri, 8 Jun 2018 07:41:03 -0400 Subject: [PATCH 05/16] Update SLACK.md --- slack/SLACK.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 185c6a0..c2d8072 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -4,23 +4,23 @@ NOTE: This demo builds on the "Versioning Demo" in README.md of this repo. If yo App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. -WORK IN PROGRESS. CHECK BACK LATER. - Some facts about how we'll be interacting with Slack. * Type of integration * [Internal Integration](https://api.slack.com/internal-integrations) * Method * [Webhooks](https://api.slack.com/incoming-webhooks#sending_messages) +* Tool + * [curl](https://curl.haxx.se/) -1. Using a web browser, log in to a Slack workspace where your pipeline will send messages -2. Browse to https://api.slack.com -3. Select the option to create a New App - 1. Name = pipeline +1. Using a web browser, log into the [Slack workspace](https://slack.com/signin) where you want AWS CodePipeline to send notifications +1. Browse to https://api.slack.com +1. Select the option to create a New App + 1. Name = `pipeline` 1. Select `Incoming Webhooks` and enable it 1. Select `Add new webhook to workspace` 1. Choose a channel and select `Authorize` 1. Take down your webhook URL -1. Test your webhook using the message.json file in this repo by issuing the command below from a development workstation +1. Test your webhook using the [message.json](slack/message.json) file in this repo by issuing the command below from your development workstation ``` curl -X POST -H 'Content-type: application/json' --data @message.json https://hooks.slack.com/services/ ``` From 66901bc66f44fa8fff87c6b4c4eff41110e65146 Mon Sep 17 00:00:00 2001 From: tkokev Date: Fri, 8 Jun 2018 08:11:23 -0400 Subject: [PATCH 06/16] Update SLACK.md --- slack/SLACK.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/slack/SLACK.md b/slack/SLACK.md index c2d8072..be8feaa 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -29,4 +29,6 @@ You should see the contents of `message.json` show up within in your Slack chann Now lets update the Appspec file from this repo to include a new `AfterInstall` step that will send build specific information into your teams slack channel for alerting when new deploys have rolled out. +For developers, the most helpful details to see in Slack would be their last git commit comment. Here is a [conversation](https://forums.aws.amazon.com/thread.jspa?threadID=226646) about ways to grab git repo metadata. + WORK IN PROGRESS. CHECK BACK LATER. From 78f98e761d85706052bc5e037f4814369edd6eae Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:19:37 -0400 Subject: [PATCH 07/16] Update SLACK.md --- slack/SLACK.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index be8feaa..740c40c 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -1,6 +1,6 @@ # CodePipeline Slack Integration Demo -NOTE: This demo builds on the "Versioning Demo" in README.md of this repo. If you haven't already performed the steps captured in README.md, do so now. They must be completed prior to continuing on with this demo. +NOTE: This demo builds on the "Versioning Demo" covered in the [README](README.md) of this repo. If you haven't already performed the steps captured in README.md, do so now. They must be completed prior to continuing on with this demo. App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. From 7ba701a71d2f0027954f536f940299cd0bd6c271 Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:20:27 -0400 Subject: [PATCH 08/16] Update SLACK.md --- slack/SLACK.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 740c40c..e7efd82 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -1,6 +1,6 @@ # CodePipeline Slack Integration Demo -NOTE: This demo builds on the "Versioning Demo" covered in the [README](README.md) of this repo. If you haven't already performed the steps captured in README.md, do so now. They must be completed prior to continuing on with this demo. +NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. From 0bb79a099ba7bc07ad6c8782027412048f8b6aac Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:21:15 -0400 Subject: [PATCH 09/16] Update SLACK.md --- slack/SLACK.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index e7efd82..f444b36 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -1,6 +1,6 @@ # CodePipeline Slack Integration Demo -NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. +NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](../README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. From 35ef17606f1cacb1b1c43d05adeb52de2bcce983 Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:22:21 -0400 Subject: [PATCH 10/16] Update SLACK.md --- slack/SLACK.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/slack/SLACK.md b/slack/SLACK.md index f444b36..9d2b1e9 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -2,6 +2,8 @@ NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](../README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. +# Background + App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. Some facts about how we'll be interacting with Slack. @@ -12,6 +14,8 @@ Some facts about how we'll be interacting with Slack. * Tool * [curl](https://curl.haxx.se/) +# Procedures + 1. Using a web browser, log into the [Slack workspace](https://slack.com/signin) where you want AWS CodePipeline to send notifications 1. Browse to https://api.slack.com 1. Select the option to create a New App From 8942f8fe6f5e3ab73637f190660ff299906e3f90 Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:28:14 -0400 Subject: [PATCH 11/16] Update SLACK.md --- slack/SLACK.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 9d2b1e9..00f9b16 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -1,6 +1,6 @@ # CodePipeline Slack Integration Demo -NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](../README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. +NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](../README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. You must also already have a Slack account and be the Owner of a Workspace. Otherwise, they are free and easy to setup. # Background From ced8d92ab87e4c2cacc5a1221f7ff686ee9b2fb5 Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:28:38 -0400 Subject: [PATCH 12/16] Update SLACK.md --- slack/SLACK.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 00f9b16..09fee96 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -2,7 +2,7 @@ NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](../README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. You must also already have a Slack account and be the Owner of a Workspace. Otherwise, they are free and easy to setup. -# Background +## Background App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. @@ -14,7 +14,7 @@ Some facts about how we'll be interacting with Slack. * Tool * [curl](https://curl.haxx.se/) -# Procedures +## Procedures 1. Using a web browser, log into the [Slack workspace](https://slack.com/signin) where you want AWS CodePipeline to send notifications 1. Browse to https://api.slack.com From 87df198fa74a2ecc526742ebe7af69755a03ff21 Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:33:52 -0400 Subject: [PATCH 13/16] Update SLACK.md --- slack/SLACK.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 09fee96..26b734f 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -6,13 +6,14 @@ NOTE: This demo builds on the "Versioning Demo" covered in the top level [README App Developers & Testers can benefit from gettings a "heads up" notification that a new App version has been deployed/released to a specific environment (Test, Stage, Prod,...). This can trigger them to perform a manual validation of a new feature before promoting the change all the way to the production version of the Application. Or it can just be a way to quickly figure out what version is on what stage of the pipeline. -Some facts about how we'll be interacting with Slack. +Here are some facts about how we'll be interacting with Slack. In depth understanding of each is not required but check out the links if you are unfamiliar with any. * Type of integration - * [Internal Integration](https://api.slack.com/internal-integrations) -* Method - * [Webhooks](https://api.slack.com/incoming-webhooks#sending_messages) -* Tool - * [curl](https://curl.haxx.se/) + * [Slack Internal Integration](https://api.slack.com/internal-integrations) +* Method of integration + * [Slack Webhooks](https://api.slack.com/incoming-webhooks#sending_messages) + * More [webhook](https://en.wikipedia.org/wiki/Webhook) details +* Integration tool + * [curl](https://curl.haxx.se/) details ## Procedures From 5f3585d0d6b09c0debaaa48f6f616c23385b4d35 Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:38:58 -0400 Subject: [PATCH 14/16] Update SLACK.md --- slack/SLACK.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 26b734f..0055a85 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -1,6 +1,6 @@ # CodePipeline Slack Integration Demo -NOTE: This demo builds on the "Versioning Demo" covered in the top level [README](../README.md) of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. You must also already have a Slack account and be the Owner of a Workspace. Otherwise, they are free and easy to setup. +NOTE: This demo builds on the [CodePipeline Versioning Demo](../README.md) covered in the top level README of this repo. If you haven't already performed those steps, please do so now. They must be completed prior to continuing on with this demo. You must also already have a Slack account and be the Owner of a Workspace. Otherwise, they are free and easy to setup. ## Background From c2288cb8aba15c3c46faf1ace116e65f102eadc1 Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:41:05 -0400 Subject: [PATCH 15/16] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 36fdbc7..c7d1613 100644 --- a/README.md +++ b/README.md @@ -249,6 +249,6 @@ By now, your pipeline should be performing its initial deploy of your applicatio # More demo topics coming soon... * Deploy the above AWS CodePipeline "demo-app" using Hashicorps [TERRAFORM](terraform/TERRAFORM.md) [Infrastructure as Code tool](https://www.terraform.io/#writ) and its [AWS Provider](https://www.terraform.io/docs/providers/aws/) -* To see how to add Slack notifications, follow [SLACK](slack/SLACK.md). +* To see how to add Slack notifications, see [SLACK](slack/SLACK.md) * For auto merging dev to master after passing tests, see [MERGE](merge/MERGE.md) * Integrate with [AWS Config](awsconfig/AWSCONFIG.md) From 88fba3381ed6c3261992ddafc3044b41b6435d7e Mon Sep 17 00:00:00 2001 From: tkokev Date: Sat, 9 Jun 2018 09:44:15 -0400 Subject: [PATCH 16/16] Update SLACK.md --- slack/SLACK.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/slack/SLACK.md b/slack/SLACK.md index 0055a85..407b281 100644 --- a/slack/SLACK.md +++ b/slack/SLACK.md @@ -29,8 +29,7 @@ Here are some facts about how we'll be interacting with Slack. In depth understa ``` curl -X POST -H 'Content-type: application/json' --data @message.json https://hooks.slack.com/services/ ``` - -You should see the contents of `message.json` show up within in your Slack channel! + * You should see the contents of `message.json` show up within in your Slack channel! Now lets update the Appspec file from this repo to include a new `AfterInstall` step that will send build specific information into your teams slack channel for alerting when new deploys have rolled out.