BCPFR1 - Cross-Referencing Modules

Updated on Jan 18, 2025 One minute to read Category-Naming/Composition Class-Pattern Class-Resource Language-Bicep Lifecycle-BAU Persona-Contributor Persona-Owner Severity-MAY Type-Functional Validation-TBD

ID: BCPFR1 - Category: Composition - Cross-Referencing Modules

Module owners MAY cross-references other modules to build either Resource or Pattern modules.

However, they MUST be referenced only by a public registry reference to a pinned version e.g. br/public:avm/[res|ptn|utl]/<publishedModuleName>:>version<. They MUST NOT use local parent path references to a module e.g. ../../xxx/yyy.bicep.

The only exception to this rule are child modules as documented in BCPFR6 .

Modules MUST NOT contain references to non-AVM modules.