update runbook attachment documentation, prepare for 0.3.5 (#135)

Co-authored-by: Jeff Zellner <jz@FH-M759DWVH4J.local>
firehydrant · Sep 5, 2023 · 7401e33 · 7401e33
1 parent f3529f7
commit 7401e33
Show file tree

Hide file tree

Showing 3 changed files with 12 additions and 11 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,6 +1,9 @@
-## 0.3.5 (Unreleased)
+## 0.3.6 (Unreleased)
+
+## 0.3.5
 
 * Use timestamps for data source IDs
+* Better document how to have runbooks automatically attach
 
 ## 0.3.4
 

diff --git a/docs/guides/runbooks_conditional_logic.md b/docs/guides/runbooks_conditional_logic.md
@@ -19,6 +19,14 @@ attachment attributes endpoint.
 https://api.firehydrant.io/v1/fh-attributes/data_bags/system-runbook-attachment-attributes
 ```
 
+To have a runbook automatically attach, set `attachment_rule` to an empty JSON chunk.
+
+```
+attachment_rule = jsonencode({})
+```
+
+Explicitly null values will assume the provider default, which is manual attachment.
+
 In the example payload below you can see that we have a list of attributes that can be selected and we can see
 the `opcode` or operators that can be used for these attributes. Given these operators, we can infer that we can
 either have a condition where the Slack channel does or does not exist.

diff --git a/docs/guides/runbooks_steps.md b/docs/guides/runbooks_steps.md
@@ -12,16 +12,6 @@ a Jira ticket. These actions are defined as steps in runbooks and each type of s
 configuration. FireHydrant has a number of integrations, each with different possible steps you can add
 to your runbook.
 
-## Attachment Rule
-
-To have a runbook automatically attach, set `attachment_rule` to an empty JSON chunk.
-
-```
-attachment_rule = jsonencode({})
-```
-
-Explicitly null values will assume the provider default, which is manual attachment.
-
 ## Step Configuration by Integration
 
 * [Confluence Cloud](./runbooks_steps_confluence_cloud.md)