Initialize CheckForUpgrade to false #20575
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Task names:
Description
The code inside Az PowerShell module that is responsible for checking for the latest module version in some cases fails with
StackOverflowException. This logic might be disabled by setting Az configurationCheckForUpgradevalue tofalse. This PR changes the Az module initialization so that disablingCheckForUpgradeis the very first thing after the module is imported. The fix might be enabled by settingUSE_FIXED_AZ_CONFIG_INITenvironment value totrue. There will be a follow up PR which will populate the value of that variable based on the feature flag.Documentation changes required: N
Added unit tests: N
Attached related issue:
Checklist: