New Feature: Parameter to specify updating Azure Modules only or All Modules #33
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…estVersion to use the parameter
…alProvisoningState
… parameter description.
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have added a new boolean parameter named UpdateAzureModulesOnly, with a default value of $true.
Some minor logic changes have been added, so when the UpdateAzureModulesOnly is set to $false; then all modules added from PowerShell Gallery to the Automation Account will be updated, in addition to the existing functionality of updating AzureRM or Az modules. The non-azure modules can also make use of the ModuleVersionOverrides.