Codefresh Cron Triggers (#127)

Author: osterman

content/documentation/getting-started.md

@@ -17,7 +17,7 @@ Check out our [terraform-root-modules](https://github.com/cloudposse/terraform-r
 
 # Local Development
 
-1. Get your [local environment](/local-dev-environments/) setup
+1. Get your [local environment]({{< relref "local-dev-environments/_index.md" >}}) setup
 2. Make sure you're familiar with [`make`](/tools/make/) and [`Makefiles`]({{< relref "tools/make/makefile-examples.md" >}}) because we use them extensively for "executable documentation".
 3. Review Docker compose
 4. Docker composition monorepo strategy
@@ -67,11 +67,11 @@ Our standard [CI/CD pipeline]({{< relref "release-engineering/cicd-process/_inde
 
 Codefresh runs docker containers for each build step. We provide a dockerized [build-harness]({{< relref "release-engineering/build-harness.md">}}) to distribute common build tools that we use as part of the build steps in the `codefresh.yml`.
 
-Learn how [codefresh]({{< relref "release-engineering/codefresh-kubernetes-integration.md" >}}) is integrated with kubernetes.
+Learn how [Codefresh]({{< relref "release-engineering/codefresh/kubernetes-integration.md" >}}) is integrated with kubernetes. This is also the same process used to add integrations for multiple clusters.
 
+We use some terraform modules to provision resources for codefresh like a [chamber user](https://github.com/cloudposse/terraform-aws-iam-chamber-user).
 
-* We use some terraform modules to provision resources for codefresh like a chamber user
-* Deploy [apps with secrets]({{< relref "secrets-management/cicd.md" >}})
+Securely deploy [apps with secrets]({{< relref "secrets-management/cicd.md" >}}).
 
 ## Backing Services (*Coming Soon*)
 

content/faq/how-to-perform-rollbacks.md

@@ -14,7 +14,7 @@ How to rollback application to previous version?
 
 # Answer
 
-[Helm]({{< relref "tools/helm.md" >}}) handles rollbacks out-of-the-box. Everytime a helm replease is performed, it creates a new revision. By pinpointing a specific helm revision and performing a rollback, the previous version will be redeployed. 
+[Helm]({{< relref "tools/helm.md" >}}) handles rollbacks out-of-the-box. Everytime a helm release is performed, it creates a new revision. By pinpointing a specific helm revision and performing a rollback, the previous version will be redeployed.
 
 There are a couple ways we recommend performing rollbacks.
 
@@ -60,7 +60,7 @@ sh-3.2 $ helm rollback $RELEASE_NAME $REVISION_NUMBER
 
 The other option is to use the Codefresh UI to perfom the rollback. The benefit with this is no console access is required.
 
-[Codefresh]({{< relref "release-engineering/codefresh.md" >}}) provides native integration
+[Codefresh]({{< relref "release-engineering/codefresh/_index.md" >}}) provides native integration
 with Kubernetes and Helm. Here's an example of how you can use their UI to perform a rollback.
 
 1. Open the [Helm Releases](https://g.codefresh.io/helm/releases/releases/) page

content/glossary/init-terraform.md

@@ -0,0 +1,13 @@
+---
+title: "init-terraform"
+description: 'The `init-terraform` script is a helper for configuring and then initializing terraform remote state in combination with the terraform-aws-tfstate-backend module.'
+terms:
+- init-terraform
+tags:
+- tfstate
+---
+
+{{% dialog type="info" icon="fa fa-book" title="Read More" %}}
+- This [`init-terraform`](https://github.com/cloudposse/geodesic/blob/master/rootfs/usr/local/bin/init-terraform) script is provided as part of geodesic.
+- The [terraform-aws-tfstate-backend]({{< relref "terraform-modules/supported/terraform-aws-tfstate-backend.md" >}}) module provides an encrypted S3 bucket for persisting state and a DynamoDB table for state locking.
+{{% /dialog %}}

content/kubernetes-platform-services/dashboard/cluster-portal.md

@@ -43,7 +43,7 @@ in the GitHub `organization` and in the `team` belonging to it.
 For more details read [Creating organization](https://help.github.com/articles/creating-a-new-organization-from-scratch/)
 and [Organizing members into teams](https://help.github.com/articles/organizing-members-into-teams/)
 
-In our example we will use `example-org` as the organization and `staging-team` as the team.
+In our example we will use `example-com` as the organization and `staging-team` as the team.
 
 ## Installing on Kubernetes
 

content/kubernetes-platform-services/dashboard/examples/portal-helmfile-sync.txt

@@ -2,7 +2,7 @@ chamber write kops PORTAL_HOSTNAME portal.us-west-2.staging.example.com
 chamber write kops PORTAL_INGRESS ingress.us-west-2.staging.example.com
 chamber write kops PORTAL_OAUTH2_PROXY_GITHUB_CLIENT_ID e76XXXXXXXXXXXXXX9a0
 chamber write kops PORTAL_OAUTH2_PROXY_GITHUB_CLIENT_SECRET b24XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXa1c
-chamber write kops PORTAL_OAUTH2_PROXY_GITHUB_ORGANIZATION example-org
+chamber write kops PORTAL_OAUTH2_PROXY_GITHUB_ORGANIZATION example-com
 chamber write kops PORTAL_OAUTH2_PROXY_GITHUB_TEAM staging-team
 chamber write kops PORTAL_OAUTH2_PROXY_COOKIE_NAME $(uuidgen)
 chamber write kops PORTAL_OAUTH2_PROXY_COOKIE_SECRET $(uuidgen)

content/release-engineering/codefresh.md renamed to content/release-engineering/codefresh/_index.md

@@ -0,0 +1,44 @@
+---
+title: "Codefresh Cron Triggers"
+description: "Cron triggers allow you to schedule jobs to run periodically using a cron-style time specifier."
+tags:
+- Codefresh
+- crontab
+- cronjob
+- pipeline
+---
+
+Codefresh supports [triggers](https://codefresh.io/docs/docs/pipeline-triggers/introduction-triggers/) which can execute a pipeline based on external webooks or cronjobs.
+
+# Configuration
+
+1. First setup a pipeline the way you would for any other kind of build.
+
+2. Navigate to the "Configuration" and select "Add Trigger"
+{{< img src="/assets/cron-trigger-7ac0cd4f.png" title="Pipeline Configuration" >}}
+
+3. Select "CRON" as the type and click "Next"
+{{< img src="/assets/cron-trigger-ad77ad30.png" title="Cronjob" >}})
+
+4. Pick a schedule
+{{< img src="/assets/cron-trigger-4d99f7d0.png" title="Pick Schedule" >}}
+
+{{% dialog type="important" icon="fa fa-exclamation-triangle" title="Important" %}}
+If rebuilding docker images, you may need to [disable docker caching](https://codefresh.io/docs/docs/troubleshooting/common-issues/disabling-codefresh-caching-mechanisms/) by adding `no_cache: true` to the `type: build` step in the pipeline.
+
+```
+build_image:
+  title: Build image
+  type: build
+  description: Build Postgres image with dataset for local development
+  image_name: dataset
+  dockerfile: Dockerfile
+  no_cache: true
+```
+
+{{% /dialog %}}
+
+# References
+
+- https://codefresh.io/docs/docs/pipeline-triggers/configure-cron-trigger/
+- https://github.com/codefresh-io/cronus/blob/master/docs/expression.md

content/release-engineering/codefresh/cron-trigger.md

@@ -1,6 +1,9 @@
 ---
 title: "Codefresh Kubernetes Integration"
 description: "Easily add Kubernetes Clusters in Codefresh"
+tags:
+- Codefresh
+- kubernetes
 ---
 
 # Setup
@@ -29,6 +32,10 @@ https://github.com/cloudposse/geodesic/blob/master/rootfs/usr/local/bin/codefres
 
 Enter the outputs of the script into the form and click save.
 
+{{% dialog type="info" icon="fa fa-info-circle" title="Note" %}}
+We recommend naming the configuration after the cluster name (e.g. `us-west-2-staging-example-com`).
+{{% /dialog %}}
+
 ## Enter Kubernetes Credentials
 
 ![Enter Kubernetes API Details](/assets/c5273c7-Screen_Shot_2018-04-16_at_5.20.30_PM.png)
@@ -48,7 +55,7 @@ create_namespace:
   title: Create an Example Namespace
   image: cloudposse/build-harness:0.5.4
   environment:
-    - KUBE_CONTEXT=us-west-2-staging-example-org
+    - KUBE_CONTEXT=us-west-2-staging-example-com
   commands:
     - "kubectl create namespace example"
 ```

content/release-engineering/codefresh-kubernetes-integration.md renamed to content/release-engineering/codefresh/kubernetes-integration.md

@@ -44,7 +44,7 @@ Helmfile depends on the following `cli` tools.
 
 Prior to using `helmfile`, you'll need a valid [`kubectl` context]({{< relref "geodesic/module/with-kops.md#export-kubecfg" >}}).
 
-Alternatively, set the [`KUBE_CONTEXT`]({{< relref "release-engineering/codefresh-kubernetes-integration.md#usage" >}}) when using `helmfile` with a Codefresh pipeline.
+Alternatively, set the [`KUBE_CONTEXT`]({{< relref "release-engineering/codefresh/kubernetes-integration.md#usage" >}}) when using `helmfile` with a Codefresh pipeline.
 
 # Configuration File