From f69bdc4bb6c4706f871f0c88504bd8645b3da60e Mon Sep 17 00:00:00 2001
From: Brian Cain <bcain@hashicorp.com>
Date: Thu, 26 Sep 2019 12:54:53 -0700
Subject: [PATCH] Docs: Add note about running bash with the `run` option for
 triggers

---
 website/source/docs/triggers/configuration.html.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/website/source/docs/triggers/configuration.html.md b/website/source/docs/triggers/configuration.html.md
index 9156774dd..cef5435ac 100644
--- a/website/source/docs/triggers/configuration.html.md
+++ b/website/source/docs/triggers/configuration.html.md
@@ -74,6 +74,18 @@ The trigger class takes various options.
   + `inline`
   + `path`
 
+    **Note:** The `run` option with `inline` is not entirely like a shell provisioner that runs bash.
+    It executes binaries on your machine rather than a bash script. If you wish you use
+    bash to pipe some text to a file in your `run` option with `inline`, wrap
+    your inline script with _`bash -c "<script goes here>"`_. For example:
+
+    ```ruby
+    config.trigger.after :up do |trigger|
+      trigger.info = "More information"
+      trigger.run = {inline: "bash -c 'echo \"hey there!!\" > file.txt'"}
+    end
+    ```
+
 * `warn` (string) - A warning message that will be printed at the beginning of a trigger.
 
 * `exit_codes` (integer, array) - A set of acceptable exit codes to continue on. Defaults to `0` if option is absent. For now only valid with the `run` option.