Skip to content

Conversation

@AnatoliB
Copy link
Contributor

@AnatoliB AnatoliB commented Aug 3, 2020

Resolves #491

When a command is invoked from the function code, but this command cannot be found in any available module, logs the following warning:

The app may be missing a module containing the '{0}' command definition. If this command belongs to a module available on the PowerShell Gallery, add a reference to this module to requirements.psd1. Make sure this module is compatible with PowerShell 7. For more details, see https://aka.ms/functions-powershell-managed-dependency.

When Import-Module is invoked from the function code but this module is not available, logs the following warning:

The app may be missing the '{0}' module. If '{0}' is available on the PowerShell Gallery, add a reference to this module to requirements.psd1. Make sure this module is compatible with PowerShell 7. For more details, see https://aka.ms/functions-powershell-managed-dependency.

/cc @eamonoreilly @stefanushinardi for the warning message wording.

Copy link
Contributor

@Francisco-Gamino Francisco-Gamino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One minor comment. Otherwise, LGTM

@AnatoliB AnatoliB merged commit 91704b2 into Azure:dev Aug 5, 2020
@AnatoliB AnatoliB deleted the command-not-found-message-2 branch August 5, 2020 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Issue an actionable warning on CommandNotFoundException

2 participants