From ae408258de549e816b1535d028a1d7e3c8e143de Mon Sep 17 00:00:00 2001 From: Emin Alemdar <77338109+eminalemdar@users.noreply.github.com> Date: Fri, 6 Oct 2023 17:51:55 +0300 Subject: [PATCH] Update docs/vendors/terraform/module-registry.md Co-authored-by: Jean-Marc Fontaine --- docs/vendors/terraform/module-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/vendors/terraform/module-registry.md b/docs/vendors/terraform/module-registry.md index e1d02f592..418fbd4f7 100644 --- a/docs/vendors/terraform/module-registry.md +++ b/docs/vendors/terraform/module-registry.md @@ -241,7 +241,7 @@ In order to use modules, you have to source them from the Spacelift module regis ![](<../../assets/screenshots/image (1).png>) !!! info - If you want to use the modules within Spacelift Stacks, those stacks consuming the module need to be able to access the Space which the module resides. You can control the Space Inheritance configurations within [Space Access Control](../../concepts/spaces/access-control.md#inheritance). + Stacks that use private modules need access to the Space the modules reside in, which can be achieved via [Space Inheritance](../../concepts/spaces/access-control.md#inheritance). ### Sharing modules