-
Notifications
You must be signed in to change notification settings - Fork 71
[DO NOT MERGE] feat: adding az CLI #263
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.
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
Open
ibuziuk
wants to merge
3
commits into
main
Choose a base branch
from
az
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+62
−0
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: devfile/developer-images
Length of output: 291
🏁 Script executed:
Repository: devfile/developer-images
Length of output: 1042
🌐 Web query:
Microsoft Azure CLI RHEL 10 install DNF microsoft.asc microsoft-2025.asc💡 Result:
To install the Azure CLI on Red Hat Enterprise Linux (RHEL) 10, you must use the Microsoft repository key specifically designated for repositories created after April 2025, which is microsoft-2025.asc [1][2]. As of July 2026, the official installation process involves the following steps [3][4]: 1. Import the correct Microsoft repository GPG key for RHEL 10 [3][4]: sudo rpm --import https://packages.microsoft.com/keys/microsoft-2025.asc 2. Install the Microsoft repository configuration package for RHEL 10 to enable the required package source [3]: sudo dnf install -y https://packages.microsoft.com/config/rhel/10/packages-microsoft-prod.rpm 3. Install the Azure CLI package using dnf [3][4]: sudo dnf install azure-cli Regarding the GPG keys: - microsoft-2025.asc: This is the required key for RHEL 10 repositories [1][2]. It corresponds to the public key fingerprint AA86 F75E 427A 19DD 3334 6403 EE4D 7792 F748 182B [1][2]. - microsoft.asc: This is the original key used for older distributions (e.g., RHEL 9 and earlier) created before May 2025 and should not be used for RHEL 10 [1][2]. Always prefer using the configuration package (packages-microsoft-prod.rpm) from https://packages.microsoft.com/config/rhel/10/ to ensure the repository is configured with the correct GPG key and base URLs automatically [1].
Citations:
🌐 Web query:
packages.microsoft.com github RHEL 10 packages-microsoft-prod RPM GPG key💡 Result:
RHEL 10 is supported by Microsoft's Linux package repositories [1][2]. Unlike earlier RHEL versions, RHEL 10 requires a newer GPG signing key due to updated security requirements [3][2]. Repository Configuration Microsoft provides a specific repository configuration package for RHEL 10. You can download and install it using the following commands: # Download the RHEL 10 repository configuration package curl -sSL -O https://packages.microsoft.com/config/rhel/10/packages-microsoft-prod.rpm # Install the repository configuration package sudo rpm -i packages-microsoft-prod.rpm GPG Keys for RHEL 10 RHEL 10 packages are signed with a newer Microsoft GPG key (RSA-4096), which is distinct from the older
microsoft.asckey used for RHEL 8 and RHEL 9 [3][2]. 1. New RHEL 10 Key: The key for RHEL 10 is typically imported automatically when using the repository configuration package above. If you need to import it manually, it is available at: https://packages.microsoft.com/rhel/10/prod/repodata/repomd.xml.key 2. Legacy Key: The legacy key (microsoft.asc) is still required for certain products (such as Microsoft Edge) that have not yet migrated to the new signing infrastructure [3]. - Legacy Key URL: https://packages.microsoft.com/keys/microsoft.asc - Command: sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc Key Details for Verification - New GPG Public Key (for repositories created after April 2025): - URL: https://packages.microsoft.com/keys/microsoft-2025.asc - Fingerprint: AA86 F75E 427A 19DD 3334 6403 EE4D 7792 F748 182B [4][5] For further details on repository structure, you can browse the official RHEL 10 repository index at https://packages.microsoft.com/rhel/10/prod/ [6].Citations:
🏁 Script executed:
Repository: devfile/developer-images
Length of output: 1447
🌐 Web query:
site:learn.microsoft.com/en-us/cli/azure/install-azure-cli-linux pivots=dnf RHEL 10 microsoft.asc microsoft-2025.asc💡 Result:
For RHEL 10, the correct GPG key to import for Microsoft repositories is microsoft-2025.asc [1]. You should import this key using the following command: sudo rpm --import https://packages.microsoft.com/keys/microsoft-2025.asc The older microsoft.asc key is used for lower versions of RHEL, not RHEL 10 [1]. To add the Microsoft repository for RHEL 10, use the official packages-microsoft-prod.rpm file rather than manual configuration files [1]: sudo dnf install -y https://packages.microsoft.com/config/rhel/10/packages-microsoft-prod.rpm There is no documented usage of a pivots=dnf configuration parameter in standard RHEL 10 dnf repository setups or Microsoft repository installation instructions.
Citations:
Use the RHEL 10 Microsoft signing key.
The Azure CLI RHEL 10
dnfinstall path importsmicrosoft.asc, which is the legacy key. Import the RHEL 10 key before installing the Microsoft repo, or omit the explicit import if thepackages-microsoft-prod.rpminstalls/importing the newer key.🤖 Prompt for AI Agents
Source: MCP tools