You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: Missing reference to Claranet Terraform modules #245
All sorts of modules are supported, tfwrapper does not make any assumption about them.
You just use any module with the vanilla source argument of a terraform module block.
For modules that are not really reusable beyond a project, there's effectively a pattern of keeping them at the root of a project under a modules or common directory, and then referencing them locally across the stacks.
I wondered how Claranet folks structure it in a project based on the tfwrapper that also uses Claranet modules.
Including such example in docs would be a nice touch to newbies, I think.
Never heard of that behavior.
Since modules are public, they're mostly retrieved from registry or, for a very few customers, mirrored from Github and used through their git as source.
Activity
pdecat commentedon Oct 9, 2023
All sorts of modules are supported,
tfwrapperdoes not make any assumption about them.You just use any module with the vanilla
sourceargument of a terraformmoduleblock.For modules that are not really reusable beyond a project, there's effectively a pattern of keeping them at the root of a project under a
modulesorcommondirectory, and then referencing them locally across the stacks.mloskot commentedon Oct 9, 2023
I have encountered convention to use Clara modules like
then export https://github.com/claranet/terraform-azurerm-nsg.git into
terraform/modules/terraform_azurerm_nsg, or add as Git submodule.I wondered how Claranet folks structure it in a project based on the
tfwrapperthat also uses Claranet modules.Including such example in docs would be a nice touch to newbies, I think.
pdecat commentedon Oct 10, 2023
Hmm, I'm not aware of such usage internally. @Shr3ps @BzSpi does that speak to you?
BzSpi commentedon Oct 10, 2023
Hi,
Never heard of that behavior.
Since modules are public, they're mostly retrieved from registry or, for a very few customers, mirrored from Github and used through their git as source.
mloskot commentedon Oct 10, 2023
Good point on the preference of the registry as source of Claranet modules.
Thanks @pdecat @BzSpi
mloskot commentedon Oct 28, 2023
I've been looking for a repo with a good example project that shows Claranet's own best practices of
I think such repo would be a very useful complement to the whole collection here.