Marking cross account deployments module as draft

Author: ferdingler

workshop/content/buildpipe/launch/_index.en.md

@@ -3,6 +3,8 @@ title = "Cross Account Deployments"
 date = 2019-10-02T16:10:44-07:00
 weight = 40
 chapter = true
+draft = true
+hidden = true
 pre = "<b>6. </b>"
 +++
 # Cross Account Deployments

workshop/content/crossaccount/_index.en.md

@@ -2,6 +2,8 @@
 title = "Creating a KMS Key"
 date = 2019-11-11T14:46:02-08:00
 weight = 30
+draft = true
+hidden = true
 +++
 
 The first thing we are going to do is modify the pipeline [created on Chapter 4](/buildpipe/pipeline.html), to use a symmetric Customer Master Key (CMK) to encrypt artifacts in the bucket. The easiest way to do this is by adding the following CloudFormation snippet at the end of our `pipeline.yml` file: 

workshop/content/crossaccount/artifactstore/_index.en.md

@@ -2,6 +2,8 @@
 title = "How does it work"
 date = 2019-11-11T14:46:02-08:00
 weight = 20
+draft = true
+hidden = true
 +++
 
 Before jumping to the implementation, we need to understand the different pieces that allow Code Pipeline to deploy across a different account. The following diagram shows a zoomed-in view of the services and roles involved in this process. 

workshop/content/crossaccount/howitworks/_index.en.md

@@ -2,6 +2,8 @@
 title = "Introduction"
 date = 2019-11-11T14:46:02-08:00
 weight = 15
+draft = true
+hidden = true
 +++
 
 ### Environment separation