[SQL] Fix null ref when not logged into Azure account for all sql cmdlets #8411
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.
Description
Current behavior of SQL cmdlets inheriting from
AzureSqlCmdletBase
results in the user getting a nullref exception when using a command prior to logging into their AzAccount. This is caused by the existing code unconditionally accessingDefaultProfile.DefaultContext.Subscription
, which only gets set upon login.This change fixes this behavior by:
AzureSqlCmdletBase.InitModelAdapter()
to no longer have a IAzureSubscription parameterIAzureContext.Subscription
Existing behavior:

New behavior:

Checklist
CONTRIBUTING.md
platyPS
module