Fix (modulemanifest): Export functions instead of cmdlets

theohbrothers · May 28, 2021 · 40ddee0 · 40ddee0
1 parent 58588f2
commit 40ddee0
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/build/definitions/modulemanifest/definition.ps1 b/build/definitions/modulemanifest/definition.ps1
@@ -22,10 +22,10 @@
     # TypesToProcess = @()
     # FormatsToProcess = @()
     # NestedModules = @()
-    FunctionsToExport = @()
-    CmdletsToExport = @(
-        'Generate-DockerImageVariants'
+    FunctionsToExport = @(
+        Get-ChildItem $PSScriptRoot/../../../src/Generate-DockerImageVariants/public -Exclude *.Tests.ps1 | % { $_.BaseName }
     )
+    CmdletsToExport = @()
     VariablesToExport = @()
     AliasesToExport = @()
     # DscResourcesToExport = @()

diff --git a/src/Generate-DockerImageVariants/Generate-DockerImageVariants.psd1 b/src/Generate-DockerImageVariants/Generate-DockerImageVariants.psd1
@@ -69,10 +69,10 @@ PowerShellVersion = '3.0'
 # NestedModules = @()
 
 # Functions to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no functions to export.
-FunctionsToExport = @()
+FunctionsToExport = 'Generate-DockerImageVariants'
 
 # Cmdlets to export from this module, for best performance, do not use wildcards and do not delete the entry, use an empty array if there are no cmdlets to export.
-CmdletsToExport = 'Generate-DockerImageVariants'
+CmdletsToExport = @()
 
 # Variables to export from this module
 # VariablesToExport = @()