Knowledge base updates (#623)

* Updated with the latest changes from the knowledge base discussions.


Co-authored-by: docs-sourcer[bot] <99042413+docs-sourcer[bot]@users.noreply.github.com>

Author: docs-sourcer[bot]

docs/discussions/knowledge-base/133.mdx

@@ -14,14 +14,14 @@ import GitHub from "/src/components/GitHub"
 <CenterLayout>
 <span className="searchCategory">Knowledge Base</span>
 <h1>Gruntwork Pipelines: applying changes to common.hcl or other root files</h1>
-<GitHub discussion={{"id":"D_kwDOF8slf84AOeJq","number":133,"author":{"login":"zackproser"},"title":"Gruntwork Pipelines: applying changes to common.hcl or other root files","body":"A customer asked: \r\n> Is it currently possible to have Gruntwork Pipelines apply changes made to the `common.hcl` file in the root of the Reference Architecture's infrastructure-live folder?  For example, we made some changes to our `ip_allow_list` to grant another engineer access to our bastion host, but after Gruntwork Pipelines ran successfully to completion without errors, we did not see the new IP address reflected in our bastion host's security group. \r\n\r\n","bodyHTML":"<p dir=\"auto\">A customer asked:</p>\n<blockquote>\n<p dir=\"auto\">Is it currently possible to have Gruntwork Pipelines apply changes made to the <code class=\"notranslate\">common.hcl</code> file in the root of the Reference Architecture's infrastructure-live folder?  For example, we made some changes to our <code class=\"notranslate\">ip_allow_list</code> to grant another engineer access to our bastion host, but after Gruntwork Pipelines ran successfully to completion without errors, we did not see the new IP address reflected in our bastion host's security group.</p>\n</blockquote>","answer":{"body":"This is a current limitation of Gruntwork Pipelines. Any file changes to common date files in the root of your infrastructive-live folder must be applied manually. At the time of this writing, Pipelines only handles common files that are in the `_envcommon` directory. \r\n\r\nWe can't yet handle common data files because they are pulled in with `read_terragrunt_config`, which we don't have the ability to parse through yet. This is dependent on this feature of Terragrunt: https://github.com/gruntwork-io/terragrunt/issues/1910","bodyHTML":"<p dir=\"auto\">This is a current limitation of Gruntwork Pipelines. Any file changes to common date files in the root of your infrastructive-live folder must be applied manually. At the time of this writing, Pipelines only handles common files that are in the <code class=\"notranslate\">_envcommon</code> directory.</p>\n<p dir=\"auto\">We can't yet handle common data files because they are pulled in with <code class=\"notranslate\">read_terragrunt_config</code>, which we don't have the ability to parse through yet. This is dependent on this feature of Terragrunt: <a class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1049933137\" data-permission-text=\"Title is private\" data-url=\"https://github.com/gruntwork-io/terragrunt/issues/1910\" data-hovercard-type=\"issue\" data-hovercard-url=\"/gruntwork-io/terragrunt/issues/1910/hovercard\" href=\"https://github.com/gruntwork-io/terragrunt/issues/1910\">gruntwork-io/terragrunt#1910</a></p>"}}} />
+<GitHub discussion={{"id":"D_kwDOF8slf84AOeJq","number":133,"author":{"login":"zackproser"},"title":"Gruntwork Pipelines: applying changes to common.hcl or other root files","body":"A customer asked: \r\n> Is it currently possible to have Gruntwork Pipelines apply changes made to the `common.hcl` file in the root of the Reference Architecture's infrastructure-live folder?  For example, we made some changes to our `ip_allow_list` to grant another engineer access to our bastion host, but after Gruntwork Pipelines ran successfully to completion without errors, we did not see the new IP address reflected in our bastion host's security group. \r\n\r\n","bodyHTML":"<p dir=\"auto\">A customer asked:</p>\n<blockquote>\n<p dir=\"auto\">Is it currently possible to have Gruntwork Pipelines apply changes made to the <code class=\"notranslate\">common.hcl</code> file in the root of the Reference Architecture's infrastructure-live folder?  For example, we made some changes to our <code class=\"notranslate\">ip_allow_list</code> to grant another engineer access to our bastion host, but after Gruntwork Pipelines ran successfully to completion without errors, we did not see the new IP address reflected in our bastion host's security group.</p>\n</blockquote>","answer":{"body":"This is a current limitation of Gruntwork Pipelines. Any file changes to common date files in the root of your infrastructive-live folder must be applied manually. At the time of this writing, Pipelines only handles common files that are in the `_envcommon` directory. \r\n\r\nWe can't yet handle common data files because they are pulled in with `read_terragrunt_config`, which we don't have the ability to parse through yet. This is dependent on this feature of Terragrunt: https://github.com/gruntwork-io/terragrunt/issues/1910","bodyHTML":"<p dir=\"auto\">This is a current limitation of Gruntwork Pipelines. Any file changes to common date files in the root of your infrastructive-live folder must be applied manually. At the time of this writing, Pipelines only handles common files that are in the <code class=\"notranslate\">_envcommon</code> directory.</p>\n<p dir=\"auto\">We can't yet handle common data files because they are pulled in with <code class=\"notranslate\">read_terragrunt_config</code>, which we don't have the ability to parse through yet. This is dependent on this feature of Terragrunt: <a aria-label=\"Issue #1910\" class=\"issue-link js-issue-link\" data-error-text=\"Failed to load title\" data-id=\"1049933137\" data-permission-text=\"Title is private\" data-url=\"https://github.com/gruntwork-io/terragrunt/issues/1910\" data-hovercard-type=\"issue\" data-hovercard-url=\"/gruntwork-io/terragrunt/issues/1910/hovercard\" href=\"https://github.com/gruntwork-io/terragrunt/issues/1910\">gruntwork-io/terragrunt#1910</a></p>"}}} />
 
 </CenterLayout>
 
 
 <!-- ##DOCS-SOURCER-START
 {
   "sourcePlugin": "github-discussions",
-  "hash": "43770433301a97503fd262990e23fc18"
+  "hash": "c19a27df29a6829112dbf51bbc66352d"
 }
 ##DOCS-SOURCER-END -->