[Bug] CLI assumes the AZURE_LOGIN_CONFIG file has subscriptions in it

[rhuanbarreto]

I'm using the latest version 2.0.1

Describe the bug
CLI is failing to deploy when reading the contents of my AZURE_LOGIN_CONFIG file. Logs below:

✖ Cannot read properties of undefined (reading 'find')
✔ Successfully logged into Azure!
Found an existing Azure config file, getting Tenant and Subscription Id from /home/vsts/.azure/azureProfile.json

This is the content of my azureProfile.json:

{"installationId": "redacteduuid"}

I could track down the error to be on this statement:

static-web-apps-cli/src/cli/commands/login/login.ts

Line 165 in 5f440e3

const defaultAzureInfo = allSubscriptions.find((subscription) => subscription.isDefault == true);

And the line before coerces the configuration to an interface:

static-web-apps-cli/src/cli/commands/login/login.ts

Line 164 in 5f440e3

const allSubscriptions = (azureProfile as AzureProfile).subscriptions;

Which resolves to this interface:

static-web-apps-cli/src/swa.d.ts

Lines 443 to 446 in 5f440e3

	declare interface AzureProfile {
	installationId: string;
	subscriptions: AzureLoginInfo[];
	}

Which is not true. My azureProfile.json doesn't have the subscriptions key. Therefore the failure.

To Reproduce
Steps to reproduce the behavior:

1. Make a pipeline in Azure Dev Ops
2. Use a service principal logging in with client ID and client secret in an AzureCLI@2 task
3. Inside of an AzureCLI@2 task, run the SWA CLI commands via an inline script
4. See error. The command will not fail despite the failure which makes debugging very hard once CI will never fail.

Expected behavior

Expected to have the command working fine.

[rhuanbarreto]

I managed to solve the problem by setting the "Use global Azure CLI configuration" option in the pipeline step. But this still doesn't solve the bug. The CLI must check for the existence of the subscriptions key.