Merge pull request #277030 from mumian/0603-import-export

Bicep import/export ga

Author: v-dirichards

articles/azure-resource-manager/bicep/bicep-import.md

@@ -3,14 +3,14 @@ title: Imports in Bicep
 description: Describes how to import shared functionality and namespaces in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/03/2023
+ms.date: 06/03/2024
 ---
 
 # Imports in Bicep
 
 This article describes the syntax you use to export and import shared functionality, as well as namespaces for Bicep extensibility providers.
 
-## Exporting types, variables and functions (Preview)
+## Exporting types, variables and functions
 
 The `@export()` decorator is used to indicate that a given statement can be imported by another file. This decorator is only valid on type, variable and function statements. Variable statements marked with `@export()` must be compile-time constants.
 
@@ -21,7 +21,7 @@ The syntax for exporting functionality for use in other Bicep files is:
 <statement_to_export>
 ```
 
-## Import types, variables and functions (Preview)
+## Import types, variables and functions
 
 The syntax for importing functionality from another Bicep file is:
 
@@ -43,7 +43,7 @@ import * as <alias_name> from '<bicep_file_name>'
 
 You can mix and match the preceding syntaxes. To access imported symbols using the wildcard syntax, you must use the `.` operator: `<alias_name>.<exported_symbol>`.
 
-Only statements that have been [exported](#exporting-types-variables-and-functions-preview) in the file being referenced are available to be imported.
+Only statements that have been [exported](#exporting-types-variables-and-functions) in the file being referenced are available to be imported.
 
 Functionality that has been imported from another file can be used without restrictions. For example, imported variables can be used anywhere a variable declared in-file would normally be valid.