Update unsupported-config-as-code-scenarios.md

src/pages/docs/projects/version-control/unsupported-config-as-code-scenarios.md

@@ -92,4 +92,7 @@ Configuration as Code is an all-or-nothing feature. You'll be unable to say mana
 
 Use the [Octopus Terraform Provider](https://registry.terraform.io/providers/OctopusDeployLabs/octopusdeploy/latest/docs) to create a deployment process template. Use Terraform's [variable functionality](https://www.terraform.io/language/values/variables) to manage the different projects. For example, have a variable for target roles; one project has **OctoFX-WebApi** while another uses **RandomQuotes-WebApi**.  
 
-One advantage to this approach is the flexibility to decide what resources are managed by the Terraform Provider and what resources are managed by users in the Octopus UI. The downside to this approach is you'll be unable to use the Octopus Deploy UI to manage your deployment processes. In addition, you'll need to convert your existing deployment process into Terraform manually. The files generated by Configuration as Code has a similar syntax as the Terraform provider, but it is not a 1:1 match.
+One advantage to this approach is the flexibility to decide what resources are managed by the Terraform Provider and what resources are managed by users in the Octopus UI. The downside to this approach is you'll be unable to use the Octopus Deploy UI to manage your deployment processes. In addition, you'll need to convert your existing deployment process into Terraform manually. The files generated by Configuration as Code has a similar syntax as the Terraform provider, but it is not a 1:1 match.
+
+## Submodules
+Submodules are a convenient way to reference one repository from within a subdirectory of another repository. Octopus does currently _not_ support the use of submodules for the storing of Configuration as Code files. This means that your configuration files must all be stored directly in the connected repository.