Azure / Azure/Azure-Landing-Zones
ESLZ Pipeline plan throwing Graph error
- Dominant language
- PowerShell
- Stars
- 96
- Forks
- 70
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 7
Description
Hi Laurent and Team,
We are facing the eslz pipeline issue. Could you please check below log and help us to fix the issue
Error:
26-Jun-2024 10:53:00 | @calling verify_parameters
-- | --
26-Jun-2024 10:53:00 | landingzone : '/tf/caf/landingzones/caf_solution/add-ons/caf_eslz'
26-Jun-2024 10:53:00 | @deploy for gitops_terraform_backend_type set to 'azurerm'
26-Jun-2024 10:53:00 | @tfstate_configure
26-Jun-2024 10:53:00 | @calling tfstate_configure -- azurerm
26-Jun-2024 10:53:00 | @calling deploy_azurerm
26-Jun-2024 10:53:00 | @calling get_storage_id
26-Jun-2024 10:53:02 | @calling_get_logged_user_object_id
26-Jun-2024 10:53:02 | - AZURE_ENVIRONMENT: AzureCloud
26-Jun-2024 10:53:02 | - ARM_ENVIRONMENT: public
26-Jun-2024 10:53:02 | Initalizing az cloud variables
26-Jun-2024 10:53:03 | ERROR: 'graph' is misspelled or not recognized by the system.
26-Jun-2024 10:53:03 |
26-Jun-2024 10:53:03 | Examples from AI knowledge base:
26-Jun-2024 10:53:03 | az extension add --name anextension
26-Jun-2024 10:53:03 | Add extension by name
26-Jun-2024 10:53:03 |
26-Jun-2024 10:53:03 | https://docs.microsoft.com/en-US/cli/azure/extension#az_extension_add
26-Jun-2024 10:53:03 | Read more about the command in reference docs
26-Jun-2024 10:53:03 | Error on or near line 344; exiting with status 1
26-Jun-2024 10:53:03 | Error on or near line 344; exiting with status 1
Contributor guide
Research direction
Start with the caf_eslz landing zone and the pipeline steps named in the log: verify_parameters, tfstate_configure, deploy_azurerm, and get_storage_id. Inspect the command at or near line 344 and the Azure CLI environment used there; done means the ESLZ pipeline completes without the unrecognized 'graph' command error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, terraform
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100