feat(blog): notifications in Terraform and IaC automation #48
Conversation
WalkthroughA new markdown file has been created to document the importance of efficient notifications in Terraform and Infrastructure as Code (IaC) automation. The document addresses critical issues related to unnoticed failures, infrastructure drift, and alert fatigue. It outlines how Spacelift's notification policies can deliver targeted, context-rich alerts and mentions an open-sourced notification policy template for community use. Changes
Sequence Diagram(s)sequenceDiagram
participant TF as Terraform
participant SL as Spacelift
participant NP as Notification Policy Engine
participant Team as Responsible Team
TF->>SL: Initiate infrastructure deployment
SL->>SL: Monitor deployment for failures
SL->>NP: Evaluate failure and trigger notification policy
NP->>Team: Dispatch targeted, context-rich notification
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for masterpoint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (11)
content/updates/importance-of-efficient-notifications-terraform-automation.md (11)
26-28: Improve Word Choice and Phrasing in the Introduction
- Line 26: Consider replacing “times where” with “times when” for clarity.
- Line 28: Use a hyphen in “follow-up” and remove the apostrophe from “re-run’s” (use “reruns” or “re-runs”) to improve grammar.
Proposed diff:
-Line 26: In the world of Terraform and OpenTofu (collectively referred to as “TF” in this post) and Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail to deploy IaC changes. +Line 26: In the world of Terraform and OpenTofu (collectively referred to as “TF” in this post) and Infrastructure as Code (IaC), there are times when the CI/CD pipeline or automation fail to deploy IaC changes. -Line 28: ...and can easily be addressed with simple follow up changes or re-run’s. +Line 28: ...and can easily be addressed with simple follow-up changes or reruns.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
[grammar] ~28-~28: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ...and can easily be addressed with simple follow up changes or re-run’s. But do you know w...(CA_FOLLOW_UP)
39-39: Subject-Verb Agreement and Punctuation
In line 39, change “the likelihood of these silent failures increase dramatically which undermines infrastructure reliability” to use correct subject-verb agreement and add a comma for clarity.Proposed diff:
-Line 39: ...the likelihood of these silent failures increase dramatically which undermines infrastructure reliability. +Line 39: ...the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
42-46: Consistent Unordered List Styling
Markdownlint recommends using dashes (-) instead of asterisks (*) for unordered list items. Consider replacing the bullets in lines 42–46 accordingly.Proposed diff (example for one item):
-* **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good. +- **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
60-60: Correct Article Usage
On line 60, change “an universal tag” to “a universal tag” for proper article usage.Proposed diff:
-Line 60: ...pings everyone in the channel with an universal tag such as `@everyone` or `@here`... +Line 60: ...pings everyone in the channel with a universal tag such as `@everyone` or `@here`...🧰 Tools
🪛 LanguageTool
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
76-83: Refine Bullet Introduction and List Styling
- Line 76: The colon after “including” is not necessary; consider removing it to avoid disrupting the flow of the sentence.
- Lines 77–83: Similar to the earlier bullet list, update the unordered list items from asterisks to dashes to meet markdownlint guidelines.
Proposed diff for line 76:
-Line 76: What makes Spacelift’s policy engine shine for notification use cases is its ability to access detailed information about the deployment (TF Applies), including: +Line 76: What makes Spacelift’s policy engine shine for notification use cases is its ability to access detailed information about the deployment (TF Applies), including🧰 Tools
🪛 LanguageTool
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
90-90: Insert Missing Comma for Clarity
On line 90, add a comma after “From those details” to improve readability.Proposed diff:
-Line 90: From those details we can, using the OPA Rego policy language, evaluate conditions and send out notifications. +Line 90: From those details, we can, using the OPA Rego policy language, evaluate conditions and send out notifications.🧰 Tools
🪛 LanguageTool
[typographical] ~90-~90: It appears that a comma is missing.
Context: ...fication-policy-input.png) From those details we can, using the OPA Rego policy langu...(DURING_THAT_TIME_COMMA)
94-94: Correct the Sentence Structure
In line 94, remove the extra conjunction “and” so that the sentence reads more smoothly.Proposed diff:
-Line 94: Our improved solution using Spacelift’s Notification Policies and does the following: +Line 94: Our improved solution using Spacelift’s Notification Policies does the following:
96-96: Ensure Consistent Bullet List Styling for Sub-Items
For the indented list item on line 96, change the asterisk to a dash to align with the markdown style guidelines.Proposed diff:
-Line 96: * It’s important to note that this is NOT blaming the author... +Line 96: - It’s important to note that this is NOT blaming the author...🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
96-96: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
106-106: Fix Verb Agreement
In line 106, “which all contributes” should be changed to “which all contribute” to match the plural subject.Proposed diff:
-Line 106: ...and decreased alert fatigue, which all contributes to less infrastructure drift... +Line 106: ...and decreased alert fatigue, which all contribute to less infrastructure drift...🧰 Tools
🪛 LanguageTool
[uncategorized] ~106-~106: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... and decreased alert fatigue, which all contributes to less infrastructure drift and more r...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
110-110: Refine Preposition Usage
On line 110, change “share our solution to the broader Spacelift community” to “share our solution with the broader Spacelift community” for improved preposition usage.Proposed diff:
-Line 110: ...we decided to share our solution to the broader Spacelift community. +Line 110: ...we decided to share our solution with the broader Spacelift community.🧰 Tools
🪛 LanguageTool
[uncategorized] ~110-~110: The preposition “with” seems more likely in this position.
Context: ...teams, we decided to share our solution to the broader Spacelift community. We’ve ...(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
122-122: Eliminate Duplicate Words
On line 122, remove the duplicate “for” in “for for managing Infrastructure as Code.”Proposed diff:
-Line 122: Interested in exploring more about Spacelift for for managing Infrastructure as Code? +Line 122: Interested in exploring more about Spacelift for managing Infrastructure as Code?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (6)
static/img/updates/efficient-notifications-terraform-automation/github-pr.jpgis excluded by!**/*.jpgstatic/img/updates/efficient-notifications-terraform-automation/sample-notification-policy-input.pngis excluded by!**/*.pngstatic/img/updates/efficient-notifications-terraform-automation/simple-targeted-notification-example.jpgis excluded by!**/*.jpgstatic/img/updates/efficient-notifications-terraform-automation/spacelift-notification-policy-template.jpgis excluded by!**/*.jpgstatic/img/updates/efficient-notifications-terraform-automation/spacelift-notifications-ping.pngis excluded by!**/*.pngstatic/img/updates/efficient-notifications-terraform-automation/terraform-automation-notifications.pngis excluded by!**/*.png
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[grammar] ~28-~28: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ...and can easily be addressed with simple follow up changes or re-run’s. But do you know w...
(CA_FOLLOW_UP)
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
[typographical] ~90-~90: It appears that a comma is missing.
Context: ...fication-policy-input.png) From those details we can, using the OPA Rego policy langu...
(DURING_THAT_TIME_COMMA)
[uncategorized] ~106-~106: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... and decreased alert fatigue, which all contributes to less infrastructure drift and more r...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~110-~110: The preposition “with” seems more likely in this position.
Context: ...teams, we decided to share our solution to the broader Spacelift community. We’ve ...
(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
[duplication] ~124-~124: Possible typo: you repeated a word.
Context: ...ested in exploring more about Spacelift for for managing Infrastructure as Code? We rec...
(ENGLISH_WORD_REPEAT_RULE)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
96-96: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - masterpoint
- GitHub Check: Header rules - masterpoint
- GitHub Check: Pages changed - masterpoint
🔇 Additional comments (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md (1)
1-11: Front Matter is Well Structured
The YAML front matter is clear and well formatted. The placeholder date is noted for testing.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (12)
content/updates/importance-of-efficient-notifications-terraform-automation.md (12)
1-11: Front Matter & Metadata Check
The YAML front matter is well-structured and provides the necessary metadata. Consider updating the placeholder date on line 7 when moving toward a final release rather than preview.
26-26: Rephrase Introductory Phrase for Clarity
The sentence beginning on line 26 ("In the world of [Terraform]…") uses "there are times where" which can be made clearer. Consider rephrasing it to "there are instances when" to improve the flow.Proposed diff:
-In the world of [Terraform](https://www.terraform.io/) and [OpenTofu](https://opentofu.org/) (collectively referred to as “TF” in this post) and Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail to deploy IaC changes. +In the world of [Terraform](https://www.terraform.io/) and [OpenTofu](https://opentofu.org/) (collectively referred to as “TF” in this post) and Infrastructure as Code (IaC), there are instances when the CI/CD pipeline or automation fails to deploy IaC changes.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
38-39: Fix Subject-Verb Agreement and Punctuation
On line 39 the phrase "the likelihood of these silent failures increase dramatically which undermines infrastructure reliability" contains a subject-verb agreement issue and lacks a needed comma.
Proposed diff:-…the likelihood of these silent failures increase dramatically which undermines infrastructure reliability. +…the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
58-60: Correct Article Usage in Notification Description
On line 60, "with an universal tag" should use the article "a" instead of "an" because "universal" begins with a consonant sound.
Proposed diff:-…pings everyone in the channel with an universal tag such as `@everyone` or `@here`. +…pings everyone in the channel with a universal tag such as `@everyone` or `@here`.🧰 Tools
🪛 LanguageTool
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
75-77: Refine List Introduction for Detail Clarity
Line 76 ends with "including:" before the bullet list. To improve readability, consider rephrasing this to introduce the list more smoothly (for example, "including the following details:").
Proposed diff:-...access detailed information about the deployment (TF Applies), including: +...access detailed information about the deployment (TF Applies), including the following details:🧰 Tools
🪛 LanguageTool
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
89-91: Clarify and Simplify Notification Explanation
The sentence starting on line 90 can be clearer. Consider rephrasing to remove the interrupting comma and improve flow.
Proposed diff:-From those details we can, using the OPA Rego policy language, evaluate conditions and send out notifications. +Based on those details, we can use the OPA Rego policy language to evaluate conditions and send out notifications.🧰 Tools
🪛 LanguageTool
[typographical] ~90-~90: It appears that a comma is missing.
Context: ...fication-policy-input.png) From those details we can, using the OPA Rego policy langu...(DURING_THAT_TIME_COMMA)
105-107: Correct Verb Agreement in Benefit Description
On line 106, the clause "which all contributes to less infrastructure drift and more reliable operational stability" uses "contributes" (singular) for a plural subject. It should be "contribute."
Proposed diff:-...and decreased alert fatigue, which all contributes to less infrastructure drift and more reliable operational stability. +...and decreased alert fatigue, which all contribute to less infrastructure drift and more reliable operational stability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~106-~106: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... and decreased alert fatigue, which all contributes to less infrastructure drift and more r...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
109-111: Improve Prepositional Choice for Community Sharing
On line 110, "share our solution to the broader Spacelift community" should use "with" instead of "to" for improved clarity.
Proposed diff:-…we decided to share our solution to the broader Spacelift community. +…we decided to share our solution with the broader Spacelift community.🧰 Tools
🪛 LanguageTool
[uncategorized] ~110-~110: The preposition “with” seems more likely in this position.
Context: ...teams, we decided to share our solution to the broader Spacelift community. We’ve ...(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
123-125: Remove Duplicate Word in Post Script
Line 124 contains a duplicated word ("for for") in the post script. Removing the extra "for" will correct this typo.
Proposed diff:-*P.S. Interested in exploring more about Spacelift for for managing Infrastructure as Code? We recently published... +*P.S. Interested in exploring more about Spacelift for managing Infrastructure as Code? We recently published...🧰 Tools
🪛 LanguageTool
[duplication] ~124-~124: Possible typo: you repeated a word.
Context: ...ested in exploring more about Spacelift for for managing Infrastructure as Code? We rec...(ENGLISH_WORD_REPEAT_RULE)
42-46: Standardize Unordered List Style (TOC Detail List)
The bullet list on lines 42–46 uses asterisks, but markdownlint guidelines recommend using dashes for unordered lists. Consider updating these list markers for consistency.
Proposed diff snippet:-* **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good. -* **Loss of source of truth** - Your VCS/Git repository no longer accurately reflects your deployed infrastructure. -* **Development roadblocks** - Subsequent changes become blocked because new deployments can’t proceed until the failure is resolved. -* **Increased troubleshooting complexity** - The longer a failure is unnoticed, the harder it becomes to troubleshoot it, since you have outdated state data and have lost context about what changed in the first place. -* **Wasted engineering time** - Developers waste time days after the failure investigating issues that could’ve been more easily diagnosed on the spot. + - **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good. + - **Loss of source of truth** - Your VCS/Git repository no longer accurately reflects your deployed infrastructure. + - **Development roadblocks** - Subsequent changes become blocked because new deployments can’t proceed until the failure is resolved. + - **Increased troubleshooting complexity** - The longer a failure is unnoticed, the harder it becomes to troubleshoot it, since you have outdated state data and have lost context about what changed in the first place. + - **Wasted engineering time** - Developers waste time days after the failure investigating issues that could’ve been more easily diagnosed on the spot.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-83: Standardize Unordered List Style for Policy Details
Similarly, the unordered list on lines 77–83 (detailing what Spacelift’s policy engine provides) should use dashes instead of asterisks to comply with markdownlint rules.
Proposed diff snippet:-* who triggered it, -* timestamps, -* the type of TF operation (add, modify, destroy), -* which TF resources are affected, -* the VCS (such as Git) context, -* state of the TF execution, -* [and more](https://docs.spacelift.io/concepts/policy/notification-policy#data-input). + - who triggered it, + - timestamps, + - the type of TF operation (add, modify, destroy), + - which TF resources are affected, + - the VCS (such as Git) context, + - state of the TF execution, + - [and more](https://docs.spacelift.io/concepts/policy/notification-policy#data-input).🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
95-97: Standardize Nested List Marker
On line 96, within the numbered list, the nested list item currently uses an asterisk. For consistency with markdownlint, change it to a dash.
Proposed diff:- * It’s important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently. + - It’s important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
96-96: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[grammar] ~28-~28: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ...and can easily be addressed with simple follow up changes or re-run’s. But do you know w...
(CA_FOLLOW_UP)
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
[typographical] ~90-~90: It appears that a comma is missing.
Context: ...fication-policy-input.png) From those details we can, using the OPA Rego policy langu...
(DURING_THAT_TIME_COMMA)
[uncategorized] ~106-~106: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... and decreased alert fatigue, which all contributes to less infrastructure drift and more r...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~110-~110: The preposition “with” seems more likely in this position.
Context: ...teams, we decided to share our solution to the broader Spacelift community. We’ve ...
(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
[duplication] ~124-~124: Possible typo: you repeated a word.
Context: ...ested in exploring more about Spacelift for for managing Infrastructure as Code? We rec...
(ENGLISH_WORD_REPEAT_RULE)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
96-96: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (11)
content/updates/importance-of-efficient-notifications-terraform-automation.md (11)
26-28: Refine Time-Reference and Compound Adjective Usage
In the introduction, consider using “when” instead of “where” for time references and hyphenate “follow up” to “follow‐up” for clarity and grammatical correctness. For example:-In the world of [Terraform](https://www.terraform.io/) and [OpenTofu](https://opentofu.org/) (collectively referred to as “TF” in this post) and Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail to deploy IaC changes. +In the world of [Terraform](https://www.terraform.io/) and [OpenTofu](https://opentofu.org/) (collectively referred to as “TF” in this post) and Infrastructure as Code (IaC), there are times when the CI/CD pipeline or automation fails to deploy IaC changes.-...can easily be addressed with simple follow up changes or re-run’s. +...can easily be addressed with simple follow‐up changes or re-run’s.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
[uncategorized] ~26-~26: “to the” seems less likely than “to”.
Context: ...y IaC changes. Failures could occur due to the code errors, cloud provider resource co...(AI_HYDRA_LEO_CP_TO_THE_TO)
[grammar] ~28-~28: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ...and can easily be addressed with simple follow up changes or re-run’s. But do you know w...(CA_FOLLOW_UP)
39-39: Adjust Verb Agreement and Punctuation for Clarity
On this line, modify the verb to agree with the singular subject “likelihood” and add a comma for clarity. For example:-As organizations’ infrastructure scales and complexity grows, the likelihood of these silent failures increase dramatically which undermines infrastructure reliability. +As organizations’ infrastructure scales and complexity grows, the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
60-60: Correct Article Usage with “Universal”
Replace “an universal tag” with “a universal tag” since “universal” begins with a “yoo” sound. For example:-...pings everyone in the channel with an universal tag such as `@everyone` or `@here` +...pings everyone in the channel with a universal tag such as `@everyone` or `@here`🧰 Tools
🪛 LanguageTool
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
[uncategorized] ~60-~60: Possible missing comma found.
Context: .... Teams become desensitized to constant alerts and critical failures (load balancer mo...(AI_HYDRA_LEO_MISSING_COMMA)
76-76: Remove Unnecessary Colon Before List
To improve readability, remove the colon after “including” so that the introduction to the list flows naturally into the bullet items. For example:-...detailed information about the deployment (TF Applies), including: +...detailed information about the deployment (TF Applies), including🧰 Tools
🪛 LanguageTool
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
90-90: Insert a Comma for Improved Readability
Adding a comma after the introductory clause enhances clarity. Consider:-From those details we can evaluate conditions and send out notifications with Rego. +From those details, we can evaluate conditions and send out notifications with Rego.🧰 Tools
🪛 LanguageTool
[typographical] ~90-~90: It appears that a comma is missing.
Context: ...fication-policy-input.png) From those details we can evaluate conditions and send out...(DURING_THAT_TIME_COMMA)
106-106: Ensure Subject-Verb Agreement in Benefit Listing
Since “benefits” is plural, change “contributes” to “contribute” for grammatical consistency. For example:-...and decreased alert fatigue, which all contributes to less infrastructure drift... +...and decreased alert fatigue, which all contribute to less infrastructure drift...🧰 Tools
🪛 LanguageTool
[uncategorized] ~106-~106: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... and decreased alert fatigue, which all contributes to less infrastructure drift and more r...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
110-110: Adjust Preposition for Natural Readability
Change “share our solution to the broader Spacelift community” to “share our solution with the broader Spacelift community” to better align with common usage. For example:-...we decided to share our solution to the broader Spacelift community. +...we decided to share our solution with the broader Spacelift community.🧰 Tools
🪛 LanguageTool
[uncategorized] ~110-~110: The preposition “with” seems more likely in this position.
Context: ...teams, we decided to share our solution to the broader Spacelift community. We’ve ...(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
124-124: Fix Duplicate Word in Conclusion Note
Remove the repeated “for” to resolve the duplication:-*P.S. Interested in exploring more about Spacelift for for managing Infrastructure as Code?* +*P.S. Interested in exploring more about Spacelift for managing Infrastructure as Code?*🧰 Tools
🪛 LanguageTool
[duplication] ~124-~124: Possible typo: you repeated a word.
Context: ...ested in exploring more about Spacelift for for managing Infrastructure as Code? We rec...(ENGLISH_WORD_REPEAT_RULE)
42-46: Standardize Unordered List Markers
For consistency with markdownlint guidelines, update the bullet list markers from asterisks to dashes. For example:-* **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good. -* **Loss of source of truth** - Your VCS/Git repository no longer accurately reflects your deployed infrastructure. -* **Development roadblocks** - Subsequent changes become blocked because new deployments can’t proceed until the failure is resolved. -* **Increased troubleshooting complexity** - The longer a failure is unnoticed, the harder it becomes to troubleshoot it, since you have outdated state data and have lost context about what changed in the first place. -* **Wasted engineering time** - Developers waste time days after the failure investigating issues that could’ve been more easily diagnosed on the spot. + - **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good. + - **Loss of source of truth** - Your VCS/Git repository no longer accurately reflects your deployed infrastructure. + - **Development roadblocks** - Subsequent changes become blocked because new deployments can’t proceed until the failure is resolved. + - **Increased troubleshooting complexity** - The longer a failure is unnoticed, the harder it becomes to troubleshoot it, since you have outdated state data and have lost context about what changed in the first place. + - **Wasted engineering time** - Developers waste time days after the failure investigating issues that could’ve been more easily diagnosed on the spot.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-83: Align Bullet List Style with Markdownlint Standards
Replace the asterisks with dashes for the unordered list in the Spacelift policy engine details section. For example:-* who triggered it, -* timestamps, -* the type of TF operation (add, modify, destroy), -* which TF resources are affected, -* the VCS (such as Git) context, -* state of the TF execution, -* [and more](https://docs.spacelift.io/concepts/policy/notification-policy#data-input). + - who triggered it, + - timestamps, + - the type of TF operation (add, modify, destroy), + - which TF resources are affected, + - the VCS (such as Git) context, + - state of the TF execution, + - [and more](https://docs.spacelift.io/concepts/policy/notification-policy#data-input).🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
96-96: Standardize Nested Bullet List Marker
Within the numbered list, update the nested bullet marker to a dash instead of an asterisk for consistency. For example:-* It's important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently. + - It's important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
96-96: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~26-~26: “to the” seems less likely than “to”.
Context: ...y IaC changes. Failures could occur due to the code errors, cloud provider resource co...
(AI_HYDRA_LEO_CP_TO_THE_TO)
[grammar] ~28-~28: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ...and can easily be addressed with simple follow up changes or re-run’s. But do you know w...
(CA_FOLLOW_UP)
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[uncategorized] ~60-~60: Possible missing comma found.
Context: .... Teams become desensitized to constant alerts and critical failures (load balancer mo...
(AI_HYDRA_LEO_MISSING_COMMA)
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
[typographical] ~90-~90: It appears that a comma is missing.
Context: ...fication-policy-input.png) From those details we can evaluate conditions and send out...
(DURING_THAT_TIME_COMMA)
[uncategorized] ~106-~106: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... and decreased alert fatigue, which all contributes to less infrastructure drift and more r...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~110-~110: The preposition “with” seems more likely in this position.
Context: ...teams, we decided to share our solution to the broader Spacelift community. We’ve ...
(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)
[duplication] ~124-~124: Possible typo: you repeated a word.
Context: ...ested in exploring more about Spacelift for for managing Infrastructure as Code? We rec...
(ENGLISH_WORD_REPEAT_RULE)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
96-96: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
🔇 Additional comments (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md (1)
1-11: YAML Front Matter is Well-Structured
The YAML front matter looks clear and correctly specified. Just ensure that the placeholder date (line 7) is updated before the final release.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (10)
content/updates/importance-of-efficient-notifications-terraform-automation.md (10)
26-26: Refine Temporal Phrase & Verb Agreement in Introduction
Consider rephrasing “there are times where the CI/CD pipeline or automation fail to deploy IaC changes” to improve clarity. For example, “there are times when the CI/CD pipeline or automation fails to deploy IaC changes.” This revision also helps ensure subject–verb agreement.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
28-28: Hyphenate “Follow-up”
In “simple follow up changes or reruns,” use a hyphen to form the compound adjective “follow-up changes.”🧰 Tools
🪛 LanguageTool
[grammar] ~28-~28: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ...and can easily be addressed with simple follow up changes or reruns. But do you know wha...(CA_FOLLOW_UP)
36-36: Subject–Verb Agreement & Punctuation in Scaling Statement
In the sentence beginning “At Masterpoint, we’ve observed this problem repeatedly…”, change “the likelihood of these silent failures increase dramatically which undermines infrastructure reliability” to “the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability” to correct verb agreement and clarify the sentence with a comma.
51-51: Correct Article Usage
Change “an universal tag” to “a universal tag” to fix the article error in “...pings everyone in the channel with an universal tag such as@everyoneor@here…”
62-62: Adjust Punctuation Before List
The phrase “including:” before the bullet list may be better served with a comma instead of a colon. Consider revising it to “including,” which can improve the flow of the sentence.
73-73: Insert Comma for Readability
In “From those details we can evaluate conditions and send out notifications with Rego…”, adding a comma after “From those details” (i.e. “From those details, we can evaluate…”) could make the sentence clearer.
86-86: Correct Verb Agreement in Benefit Description
In “which all contributes to less infrastructure drift and more reliable operational stability,” use “contribute” instead of “contributes” so that the verb agrees with the plural subject “benefits.”
38-42: Consistent Unordered List Style in “Silent Failure” Section
The bullet points in this section start with asterisks (“*”). For consistency with our style guidelines (which expect dashes “–”), consider replacing these with “–”.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
🪛 markdownlint-cli2 (0.17.2)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
63-69: Consistent Unordered List Style in Notification Data Section
The list detailing the deployment information (e.g. “* who triggered it,” “* timestamps,” etc.) currently uses asterisks. For consistency—and to satisfy markdownlint rules—please convert these to dash (“-”) list items.
77-78: Consistent Unordered List Style in Nested Bullet
Within the numbered list outlining notification benefits, the nested bullet on line 78 also uses an asterisk. Consider switching this to a dash (“-”) to maintain consistent list styling throughout the document.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[grammar] ~28-~28: ‘follow up’ seems to be a compound adjective before a noun. Use a hyphen: “follow-up”.
Context: ...and can easily be addressed with simple follow up changes or reruns. But do you know wha...
(CA_FOLLOW_UP)
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
[typographical] ~90-~90: It appears that a comma is missing.
Context: ...fication-policy-input.png) From those details we can evaluate conditions and send out...
(DURING_THAT_TIME_COMMA)
[uncategorized] ~106-~106: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... and decreased alert fatigue, which all contributes to less infrastructure drift and more r...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
96-96: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - masterpoint
- GitHub Check: Header rules - masterpoint
- GitHub Check: Pages changed - masterpoint
🔇 Additional comments (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md (1)
1-11: Great YAML Front Matter!
The metadata is clear and complete. Consider updating the placeholder date once the final publication date is confirmed.
oycyc
changed the title
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (8)
content/updates/importance-of-efficient-notifications-terraform-automation.md (8)
1-11: YAML Front Matter Needs a Valid Date.
The front matter overall is well structured, but the date on line 7 is a placeholder (2025-03-99). Please update it with a valid date before merging.
24-30: Improve Temporal Expression in the Introduction.
On line 26, consider revising “there are times where” to “there are times when” to enhance grammatical clarity.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
32-40: Correct Subject-Verb Agreement and Punctuation.
On line 39, update the sentence to:“…the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability.”
This correction will improve both verb agreement and readability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
56-63: Fix Article Usage in Alert Fatigue Section.
On line 60, change “with an universal tag” to “with a universal tag” to correct the article usage.🧰 Tools
🪛 LanguageTool
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
72-88: Refine Colon Usage in the Spacelift Section.
On line 76, the sentence ends with “including:” before listing items. Consider removing the colon or rephrasing (e.g., “including details such as”) to improve clarity.🧰 Tools
🪛 LanguageTool
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
42-46: Standardize Unordered List Markers.
Markdownlint recommends using dashes (-) over asterisks (*) for unordered lists. Please update the list markers in the “Silent Failure Problem” section (lines 42–46) to use dashes for consistency.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-83: Ensure Consistent List Styling in the Detailed Information Section.
The bullet list on lines 77–83 (detailing properties like “who triggered it,” “timestamps,” etc.) currently uses asterisks. For markdown style consistency, change these markers to dashes (-).🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
95-98: Align Nested List Marker Style.
Within the numbered list detailing the improved notification solution, the nested bullet on line 96 uses an asterisk. Please update it to use a dash (-) to adhere to the markdown guidelines.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
96-96: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
96-96: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
🔇 Additional comments (3)
content/updates/importance-of-efficient-notifications-terraform-automation.md (3)
108-117: Open Sourcing Section Looks Clear.
The “Open Sourcing our Spacelift Notification Policy Template” section is well written and informative.
118-125: Conclusion Section is Effective.
The conclusion successfully reinforces the blog’s message and summarizes the benefits of effective notifications.
1-125: Overall Review Summary.
The new markdown document is well structured and provides a detailed, informative overview of the importance of efficient notifications in Terraform and IaC automation. Before merging, please address the placeholder date in the front matter and consider the suggested grammatical and markdown style improvements.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
96-96: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (9)
content/updates/importance-of-efficient-notifications-terraform-automation.md (9)
1-11: Front Matter – Date Placeholder Needs Correction
The metadata looks good overall, but the date on line 7 (2025-03-99) is clearly a placeholder and invalid. Please update it to a valid date before finalizing the post.
26-26: Introduction – Refine Time Expression and Verb Agreement
Consider rephrasing “there are times where the CI/CD pipeline or automation fail to deploy IaC changes” to “there are times when the CI/CD pipeline or automation fails to deploy IaC changes” for improved clarity and correct subject–verb agreement.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
39-39: Silent Failure Problem – Correct Verb Agreement and Punctuation
On line 39, “the likelihood of these silent failures increase dramatically which undermines infrastructure reliability” should use a singular verb (“increases”) and include a comma before “which” to improve readability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
60-60: Alert Fatigue – Article Correction Needed
On line 60, “an universal tag” should be corrected to “a universal tag” since the word “universal” starts with a consonant sound.🧰 Tools
🪛 LanguageTool
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
67-67: Targeted Deployment Notifications – Use Appropriate Relative Pronoun
On line 67, change “the engineer that made the code change” to “the engineer who made the code change” to correctly refer to a person.🧰 Tools
🪛 LanguageTool
[style] ~67-~67: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...(THAT_WHO)
[uncategorized] ~67-~67: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... best suited for handling the issue and has the most context ![Pinging ALL vs indi...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
76-76: Spacelift Notification Details – Revisit Colon Usage
On line 76, the phrase “including:” is followed immediately by a bullet list. Consider removing the colon or rephrasing (for example, “including details such as”) to comply with best practices for introducing lists.🧰 Tools
🪛 LanguageTool
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
42-46: Unordered List Style – Update List Markers for Consistency
The consequence items on lines 42–46 use asterisks. For consistency with markdownlint recommendations (MD004), please change these to dash (-) list markers.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-83: Unordered List Style – Update Notification Detail List Markers
The bullet list detailing Spacelift’s policy engine capabilities on lines 77–83 is currently using asterisks. Consider replacing them with dashes (-) to align with the expected markdown style.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
96-96: Nested List Consistency – Standardize Bullet Marker
On line 96, within the ordered list’s nested bullet, an asterisk is used. For consistency, please change it to a dash (-) as required by markdownlint guidelines.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
96-96: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~39-~39: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~39-~39: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~60-~60: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[style] ~67-~67: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...
(THAT_WHO)
[uncategorized] ~67-~67: This verb does not appear to agree with the subject. Consider using a different form.
Context: ... best suited for handling the issue and has the most context ![Pinging ALL vs indi...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[typographical] ~76-~76: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
46-46: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
83-83: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
96-96: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - masterpoint
- GitHub Check: Header rules - masterpoint
- GitHub Check: Pages changed - masterpoint
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (9)
content/updates/importance-of-efficient-notifications-terraform-automation.md (9)
1-11: Front Matter Header: Update Placeholder DateThe front matter header is well-structured overall, but the date on line 7 (
2025-03-99) appears to be a placeholder and is not in a valid format. Please update it to a proper date before publication.
26-26: Enhance Temporal Clause WordingConsider revising the phrase on line 26 from "there are times where the CI/CD pipeline or automation fail" to "there are times when the CI/CD pipeline or automation fails" for improved clarity and correct subject-verb agreement.
🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
38-38: Correct Subject-Verb Agreement and PunctuationOn line 38, update the sentence to read: "As organizations’ infrastructure scales and complexity grows, the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability." This change ensures proper subject-verb agreement and improves readability.
🧰 Tools
🪛 LanguageTool
[uncategorized] ~38-~38: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~38-~38: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
59-59: Fix Article UsageOn line 59, change "an universal tag" to "a universal tag" to use the correct article with the consonant sound.
🧰 Tools
🪛 LanguageTool
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
66-66: Improve Pronoun ChoiceOn line 66, consider replacing "the engineer that made the code change" with "the engineer who made the code change" for clearer reference to a person.
🧰 Tools
🪛 LanguageTool
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...(THAT_WHO)
75-75: Revise List Introduction PunctuationRemove the colon following "including" on line 75. The colon is unnecessary before the list items and its removal will improve the sentence flow.
🧰 Tools
🪛 LanguageTool
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
41-45: Consistent Unordered List StyleMarkdownlint recommends using dashes ("-") for unordered lists. Consider replacing the asterisks on lines 41–45 with dashes for consistency.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
41-41: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
76-82: Standardize List MarkersFor the list on lines 76–82, update the asterisks to dashes ("-") to align with markdownlint style guidelines.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
76-76: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
95-95: Nested List Marker UpdateOn line 95, replace the asterisk with a dash ("-") for the nested list item to maintain consistent list formatting.
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
95-95: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~38-~38: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~38-~38: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...
(THAT_WHO)
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
41-41: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
76-76: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
95-95: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
🔇 Additional comments (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md (1)
1-124: Overall Content and StructureThe article provides a comprehensive and informative discussion on the importance of notifications in Terraform and IaC automation. Aside from the minor language and style improvements noted above, the content is well-organized and engaging.
🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
[uncategorized] ~38-~38: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~38-~38: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...(THAT_WHO)
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
41-41: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
76-76: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
95-95: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
|
|
||
| Below is a simple targeted notification example -- with different use cases in different organizations, the actual messaging and content will vary greatly to suit what different teams need to best address their needs. | ||
|
|
||
|  |
There was a problem hiding this comment.
|  | |
|  |
There was a problem hiding this comment.
@oycyc here is a different screenshot that isn't as redacted. As long as @westonplatter is good with this, let's use this.
content/updates/importance-of-efficient-notifications-terraform-automation.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (9)
content/updates/importance-of-efficient-notifications-terraform-automation.md (9)
1-11: Front Matter – Date Placeholder
The front matter contains a placeholder date on line 7 (date: 2025-03-99 # TODO TBD, placeholder for testing in preview). Please update this to a valid publication date before merging.- date: 2025-03-99 # TODO TBD, placeholder for testing in preview + date: 2025-03-15 # Update with the final publication date
24-29: Introduction – Time Reference Clarity
In line 26, the phrase “there are times where the CI/CD pipeline or automation fail to deploy IaC changes” can be improved for clarity and grammatical correctness. Consider revising it to “there are instances when the CI/CD pipeline or automation fails to deploy IaC changes.”- ...there are times where the CI/CD pipeline or automation fail to deploy IaC changes. + ...there are instances when the CI/CD pipeline or automation fails to deploy IaC changes.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
32-39: The Silent Failure Problem – Grammar Adjustments
Within the “The Silent Failure Problem in IaC Deployments” section:
- On line 34, instead of “if there are no alerting set up,” consider “if no alerting is set up.”
- On line 38, change “the likelihood of these silent failures increase dramatically which undermines infrastructure reliability” to “the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability.”
- if there are no alerting set up + if no alerting is set up - the likelihood of these silent failures increase dramatically which undermines infrastructure reliability. + the likelihood of these silent failures increases dramatically, which undermines infrastructure reliability.🧰 Tools
🪛 LanguageTool
[uncategorized] ~34-~34: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~38-~38: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~38-~38: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
55-62: Alert Fatigue – Correcting the Article Use
On line 59, “with an universal tag” should be replaced with “with a universal tag” to correct the article usage.- with an universal tag such as `@everyone` or `@here` + with a universal tag such as `@everyone` or `@here`🧰 Tools
🪛 LanguageTool
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
64-69: Targeted Deployment Notifications – Human Reference
In line 66, change “the engineer that made the code change” to “the engineer who made the code change” to appropriately refer to a person.- the engineer that made the code change + the engineer who made the code change🧰 Tools
🪛 LanguageTool
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...(THAT_WHO)
71-83: Spacelift Policy Engine Description – Punctuation Adjustment
On line 75, the sentence ends with a colon after “including:” before the bullet list. For smoother readability, consider removing the colon or restructuring the sentence.-... including: +... including🧰 Tools
🪛 LanguageTool
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
76-76: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
41-45: Markdown List Style – Consistency for Unordered Lists (Section on Silent Failures)
The unordered list items on lines 41–45 currently use asterisks. For consistency with Markdown lint guidelines (which expect dashes), please update these markers.-* **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC... + - **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC...(Apply similar changes to the subsequent bullet items on lines 42–45.)
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
41-41: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
76-82: Markdown List Style – Consistency in the Policy Engine Feature List
The bullet list detailing the information provided by Spacelift’s policy engine (lines 76–82) is using asterisks. Please replace them with dashes to comply with markdown style consistency.-* who triggered it, + - who triggered it,(Ensure to update all bullet markers in this list accordingly.)
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
76-76: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
94-98: Markdown List Style – Consistent Markers in Nested Lists
Within the numbered list under “Our improved solution using [Spacelift's Notification Policies]” (specifically the nested bullet on line 95), the asterisk should be replaced by a dash for consistency.- * It's important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently. + - It's important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
95-95: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~34-~34: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~38-~38: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...the likelihood of these silent failures increase dramatically which undermines infrastru...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[uncategorized] ~38-~38: A comma might be missing here.
Context: ...ihood of these silent failures increase dramatically which undermines infrastructure reliabi...
(AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...
(THAT_WHO)
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ...tion about the deployment (TF Applies), including: * who triggered it, * timestamps, * the...
(RP_COLON)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
41-41: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
76-76: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
95-95: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - masterpoint
- GitHub Check: Header rules - masterpoint
- GitHub Check: Pages changed - masterpoint
🔇 Additional comments (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md (1)
117-124: Conclusion – Overall Structure and Clarity
The conclusion is well structured and effectively reinforces the importance of targeted notifications. No changes are essential here, but a final proofread for minor stylistic refinements is recommended before publication.
Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
…m-automation.md Co-authored-by: Matt Gowie <[email protected]>
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (10)
content/updates/importance-of-efficient-notifications-terraform-automation.md (10)
1-11: Note: Update the Date Placeholder in Front Matter
Thedatefield on line 7 is currently a placeholder (2025-03-99). Please update it with the actual publish date before merging.
24-27: Suggestion: Use "when" Instead of "where"
In the introduction, consider changing “there are times where” to “there are times when” to more clearly indicate a temporal condition.- ...there are times where the CI/CD pipeline or automation fail to deploy IaC changes. + ...there are times when the CI/CD pipeline or automation fail to deploy IaC changes.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
32-34: Correction: Grammar Adjustment for Alerting
The phrase “if there are no alerting set up” can be improved for grammatical agreement. Consider rephrasing to “if alerting is not set up.”- if there are no alerting set up + if alerting is not set up🧰 Tools
🪛 LanguageTool
[uncategorized] ~34-~34: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
59-59: Typo Fix: Correcting Article Usage
Replace “an universal tag” with “a universal tag” to ensure correct article usage.- with an universal tag + with a universal tag🧰 Tools
🪛 LanguageTool
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
66-66: Style Improvement: Person-Reference Correction
Change “engineer that made the code change” to “engineer who made the code change” for better clarity when referring to a person.- engineer that made the code change + engineer who made the code change🧰 Tools
🪛 LanguageTool
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...(THAT_WHO)
75-75: Typographical Suggestion: Adjusting the "including" Clause
Avoid using a colon immediately after “including.” Consider rephrasing to “including details such as” to introduce the subsequent list more naturally.- including: + including details such as🧰 Tools
🪛 LanguageTool
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ... about the TF apply that just occurred, including: * who triggered it, * timestamps, * the...(RP_COLON)
41-45: Markdown Style: Use Dashes for Unordered List Items
Per markdownlint (MD004) guidelines, please replace the asterisks with dashes for the list items to maintain a consistent style.- * **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good. - * **Loss of source of truth** - Your VCS/Git repository no longer accurately reflects your deployed infrastructure. - * **Development roadblocks** - Subsequent changes become blocked because new deployments can’t proceed until the failure is resolved. - * **Increased troubleshooting complexity** - The longer a failure is unnoticed, the harder it becomes to troubleshoot it, since you have outdated state data and have lost context about what changed in the first place. - * **Wasted engineering time** - Developers waste time days after the failure investigating issues that could’ve been more easily diagnosed on the spot. + - **Infrastructure drift** - Your actual infrastructure diverges from your desired state in the IaC, which is never good. + - **Loss of source of truth** - Your VCS/Git repository no longer accurately reflects your deployed infrastructure. + - **Development roadblocks** - Subsequent changes become blocked because new deployments can’t proceed until the failure is resolved. + - **Increased troubleshooting complexity** - The longer a failure is unnoticed, the harder it becomes to troubleshoot it, since you have outdated state data and have lost context about what changed in the first place. + - **Wasted engineering time** - Developers waste time days after the failure investigating issues that could’ve been more easily diagnosed on the spot.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
41-41: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
76-82: Markdown Style: Consistent List Item Formatting
For the detailed points about Spacelift’s policy engine, replace the asterisks with dashes to comply with markdownlint’s style recommendations.- * who triggered it, - * timestamps, - * the type of TF operation (add, modify, destroy), - * which TF resources are affected, - * the VCS (such as Git) context, - * state of the TF execution, - * [and more](https://docs.spacelift.io/concepts/policy/notification-policy#data-input). + - who triggered it, + - timestamps, + - the type of TF operation (add, modify, destroy), + - which TF resources are affected, + - the VCS (such as Git) context, + - state of the TF execution, + - [and more](https://docs.spacelift.io/concepts/policy/notification-policy#data-input).🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
76-76: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
94-95: Markdown Style: Use Dashes in Nested List Items
Within the nested list in the “Notifications through Spacelift’s IaC Automation” section, please replace the asterisk with a dash to keep list formatting consistent.- * It's important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently. + - It's important to note that this is NOT blaming the author, especially since TF Apply errors can be common. Rather, this is proactive, ensuring that the failure notification reaches the person most capable of resolving the issue efficiently.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
95-95: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
119-119: Tone Refinement: Adjust Notification Wording
Consider rephrasing “each failure notice goes to the right person(s) who can fix the issue” to a more formal tone, such as “each failure notice is directed to the appropriate person(s) who can resolve the issue.”- each failure notice goes to the right person(s) who can fix the issue. + each failure notice is directed to the appropriate person(s) who can resolve the issue.🧰 Tools
🪛 LanguageTool
[style] ~119-~119: Consider using a different verb for a more formal wording.
Context: ...ice goes to the right person(s) who can fix the issue. By implementing this tailor...(FIX_RESOLVE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~34-~34: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...
(THAT_WHO)
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ... about the TF apply that just occurred, including: * who triggered it, * timestamps, * the...
(RP_COLON)
[style] ~119-~119: Consider using a different verb for a more formal wording.
Context: ...ice goes to the right person(s) who can fix the issue. By implementing this tailor...
(FIX_RESOLVE)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
20-20: Link fragments should be valid
null
(MD051, link-fragments)
41-41: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
76-76: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
95-95: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (10)
content/updates/importance-of-efficient-notifications-terraform-automation.md (10)
7-7: Placeholder Date Warning:
Thedatefield is currently set to"2025-03-99", which appears to be a placeholder. Please update this field to a valid date before merging.
26-26: Temporal Preposition Adjustment:
Consider replacing "where" with "when" in the sentence “In the world of Terraform and Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail to deploy IaC changes” for a more precise temporal reference.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
34-34: Subject-Verb Agreement Improvement:
The phrase “if there are no alerting set up” is grammatically awkward. Consider revising it to “if no alerting is set up” or “if there are no alert systems set up” to improve clarity.🧰 Tools
🪛 LanguageTool
[uncategorized] ~34-~34: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
59-59: Article and Punctuation Correction:
In “with an universal tag such as@everyoneor@here”, replace “an universal” with “a universal” since “universal” begins with a consonant sound. Also, review the punctuation for clarity in this sentence.🧰 Tools
🪛 LanguageTool
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
[uncategorized] ~59-~59: Possible missing comma found.
Context: .... Teams become desensitized to constant alerts and critical failures (load balancer mo...(AI_HYDRA_LEO_MISSING_COMMA)
66-66: Pronoun Refinement:
In the sentence “…the engineer that made the code change,” consider replacing “that” with “who” when referring to a person for improved readability.🧰 Tools
🪛 LanguageTool
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...(THAT_WHO)
75-75: Punctuation Adjustment in List Introduction:
Avoid using a colon immediately after “including” in “...detailed information about the TF apply that just occurred, including:” Either remove the colon or restructure the sentence to introduce the following list more smoothly.🧰 Tools
🪛 LanguageTool
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ... about the TF apply that just occurred, including: * who triggered it, * timestamps, * the...(RP_COLON)
41-45: Markdown List Style Consistency (Section 1):
The unordered list items here use asterisks (*) rather than dashes (-). For consistency with markdown style guidelines, please replace the asterisks with dashes.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
41-41: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
76-82: Markdown List Style Consistency (Section 2):
The bullet items following “including” also use asterisks (*). Consider switching these to dashes (-) to align with recommended markdown practices.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
76-76: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
95-95: Markdown List Style Consistency (Section 3):
The bullet point on this line is using an asterisk (*). Please replace it with a dash (-) to maintain consistent unordered list styling throughout the document.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
95-95: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
119-119: Verb Formality Suggestion:
In the phrase “…the right person(s) who can fix the issue,” consider replacing “fix” with “resolve” for a more formal tone.🧰 Tools
🪛 LanguageTool
[style] ~119-~119: Consider using a different verb for a more formal wording.
Context: ...ice goes to the right person(s) who can fix the issue. By implementing this tailor...(FIX_RESOLVE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~34-~34: This verb does not appear to agree with the subject. Consider using a different form.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...
(AI_EN_LECTOR_REPLACEMENT_VERB_AGREEMENT)
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[uncategorized] ~59-~59: Possible missing comma found.
Context: .... Teams become desensitized to constant alerts and critical failures (load balancer mo...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...
(THAT_WHO)
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ... about the TF apply that just occurred, including: * who triggered it, * timestamps, * the...
(RP_COLON)
[style] ~119-~119: Consider using a different verb for a more formal wording.
Context: ...ice goes to the right person(s) who can fix the issue. By implementing this tailor...
(FIX_RESOLVE)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
20-20: Link fragments should be valid
null
(MD051, link-fragments)
41-41: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
76-76: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
95-95: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
🔇 Additional comments (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md (1)
15-23: Table of Contents Link Verification:
Please verify that all link fragments in the Table of Contents correctly correspond to their respective section headings in the document.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
20-20: Link fragments should be valid
null(MD051, link-fragments)
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (11)
content/updates/importance-of-efficient-notifications-terraform-automation.md (11)
1-11: Invalid Date in Front Matter.
Thedatefield ("2025-03-99") appears to be a placeholder and is not a valid date. Please update it to a correct date format before merging.
26-26: Wording Improvement in Introduction.
Consider revising "there are times where" to "there are times when" for improved clarity and consistency, as suggested by LanguageTool.🧰 Tools
🪛 LanguageTool
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...(WHEN_WHERE)
[uncategorized] ~26-~26: “to the” seems less likely than “to”.
Context: ...y IaC changes. Failures could occur due to the code errors, cloud provider resource co...(AI_HYDRA_LEO_CP_TO_THE_TO)
34-34: Grammar Correction in Notification Setup.
The sentence "if there are no alerting set up" would be clearer if changed to "if there is no alerting set up" since “alerting” is used as a mass noun.🧰 Tools
🪛 LanguageTool
[uncategorized] ~34-~34: The verb “are” doesn’t seem to fit in this context, “is” is probably more formally correct.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...(AI_HYDRA_LEO_CPT_ARE_IS)
38-38: Subject-Verb Agreement & Punctuation Issue.
The phrase "the likelihood of these silent failures increase which undermines infrastructure reliability" should be revised to "the likelihood of these silent failures increases, which undermines infrastructure reliability" to ensure proper subject-verb agreement and clarity.🧰 Tools
🪛 LanguageTool
[uncategorized] ~38-~38: Possible missing comma found.
Context: ...the likelihood of these silent failures increase which undermines infrastructure reliabi...(AI_HYDRA_LEO_MISSING_COMMA)
41-45: Consistent Unordered List Style.
The bullet items currently use asterisks. For consistency with markdownlint guidelines (MD004), consider replacing these with dashes (-).🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
41-41: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
59-59: Article Tone: Minor Spelling Correction.
Please change "an universal tag" to "a universal tag" to correct the article usage.🧰 Tools
🪛 LanguageTool
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as@everyoneor `@...(EN_A_VS_AN)
[uncategorized] ~59-~59: Possible missing comma found.
Context: .... Teams become desensitized to constant alerts and critical failures (load balancer mo...(AI_HYDRA_LEO_MISSING_COMMA)
66-66: Pronoun Correction.
Replace "the engineer that made the code change" with "the engineer who made the code change" for grammatical accuracy when referring to a person.🧰 Tools
🪛 LanguageTool
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...(THAT_WHO)
75-75: Punctuation Suggestion: Remove Colon.
The colon after "including" in the sentence on line 75 is unnecessary. Consider removing it to improve the sentence flow.🧰 Tools
🪛 LanguageTool
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ... about the TF apply that just occurred, including: * who triggered it, * timestamps, * the...(RP_COLON)
76-82: List Styling Consistency.
The bullet points in this section also use asterisks. For consistency with markdown standards, replace these with dashes (-).🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
76-76: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
93-98: Ensure Consistent List Formatting in Enumerated Sections.
The numbered list and its nested bullet (e.g., in point 1) use different list markers. It would be ideal to standardize the nested list formatting (for example, using dashes for sub-items) throughout the document.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
95-95: Unordered list style
Expected: dash; Actual: asterisk(MD004, ul-style)
119-119: Terminology Update for Formality.
Consider replacing "fix the issue" with "resolve the issue" on line 119 for a tone that better suits a formal blog post.🧰 Tools
🪛 LanguageTool
[style] ~119-~119: Consider using a different verb for a more formal wording.
Context: ...ice goes to the right person(s) who can fix the issue. By implementing this tailor...(FIX_RESOLVE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/updates/importance-of-efficient-notifications-terraform-automation.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
content/updates/importance-of-efficient-notifications-terraform-automation.md
[style] ~26-~26: It might be better to use ‘times’ with the time-relative pronoun ‘when’. (Alternatively, use ‘in/on which’.)
Context: ...Infrastructure as Code (IaC), there are times where the CI/CD pipeline or automation fail t...
(WHEN_WHERE)
[uncategorized] ~26-~26: “to the” seems less likely than “to”.
Context: ...y IaC changes. Failures could occur due to the code errors, cloud provider resource co...
(AI_HYDRA_LEO_CP_TO_THE_TO)
[uncategorized] ~34-~34: The verb “are” doesn’t seem to fit in this context, “is” is probably more formally correct.
Context: ...quietly. They can go unnoticed if there are no alerting set up -- particularly in t...
(AI_HYDRA_LEO_CPT_ARE_IS)
[uncategorized] ~38-~38: Possible missing comma found.
Context: ...the likelihood of these silent failures increase which undermines infrastructure reliabi...
(AI_HYDRA_LEO_MISSING_COMMA)
[misspelling] ~59-~59: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...ails pings everyone in the channel with an universal tag such as @everyone or `@...
(EN_A_VS_AN)
[uncategorized] ~59-~59: Possible missing comma found.
Context: .... Teams become desensitized to constant alerts and critical failures (load balancer mo...
(AI_HYDRA_LEO_MISSING_COMMA)
[style] ~66-~66: Consider using “who” when you are referring to a person instead of an object.
Context: ...ications should be tied to the engineer that made the code change. They are most lik...
(THAT_WHO)
[typographical] ~75-~75: Do not use a colon (:) before a series that is introduced by a preposition (‘including’). Remove the colon or add a noun or a noun phrase after the preposition.
Context: ... about the TF apply that just occurred, including: * who triggered it, * timestamps, * the...
(RP_COLON)
[style] ~119-~119: Consider using a different verb for a more formal wording.
Context: ...ice goes to the right person(s) who can fix the issue. By implementing this tailor...
(FIX_RESOLVE)
🪛 markdownlint-cli2 (0.17.2)
content/updates/importance-of-efficient-notifications-terraform-automation.md
20-20: Link fragments should be valid
null
(MD051, link-fragments)
41-41: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
42-42: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
43-43: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
44-44: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
45-45: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
76-76: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
77-77: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
78-78: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
79-79: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
80-80: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
81-81: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
82-82: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
95-95: Unordered list style
Expected: dash; Actual: asterisk
(MD004, ul-style)
TODO:
Blog article highlighting notifications in Terraform and IaC automation.
Link to the article in the Netlify preview: https://deploy-preview-48--masterpoint.netlify.app/updates/importance-of-efficient-notifications-terraform-automation/
Notion Link: https://www.notion.so/masterpoint/Importance-of-Notifications-in-Terraform-CI-CD-Deployments-1ab859758a56806baf49c802362fa95f
Summary by CodeRabbit