8000 Pin Azure CLI to 2.82.0 to fix JSON parsing error by Pepo48 · Pull Request #47828 · keycloak/keycloak · GitHub
[go: up one dir, main page]
Skip to content

Pin Azure CLI to 2.82.0 to fix JSON parsing error #47828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stianst merged 1 commit into from
Apr 8, 2026
Merged

Pin Azure CLI to 2.82.0 to fix JSON parsing error #47828

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions .github/scripts/ansible/azure_vm_manager.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,9 @@ VM_SIZE="Standard_D2s_v5"
IMAGE="Ubuntu2404"

if [[ "$ACTION" == "create" ]]; then
# Pin Azure CLI to 2.82.0 (azure-core 1.38.0+ causes JSON parsing errors with az vm create)
sudo apt-get install -y -q --allow-downgrades azure-cli=2.82.0-1~noble
@michalvavrik michalvavrik Apr 7, 2026 •
edited
Loading
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

696D

Please bear in your mind I have a limited knowledge about Azure CLI and I also don't know what is a common practice in this project. Still, I'll tell you what I think 😄 :

Should you link TODO with link to an opened issue so that you don't loose track of this? Or what are upgrade plans? I'd go even further and say without linked upstream issue or documentation saying which Azure CLI can be used under certain conditions, this is fantastic workaround, but we will need to revisit it at some point in the future and define when exactly we should use Azure CLI 2.82.0-1-noble and under which conditions we can proceed to the newest version.


# 1. Resource group (created via idempotent command)
az group create --name "$CLUSTER" --location "$REGION"

Expand Down
Loading
0