Skip to content

feat(images): add explicit per-image architectures - #18778

Draft
binujp wants to merge 1 commit into
4.0from
bphilip/image-arch-support
Draft

feat(images): add explicit per-image architectures#18778
binujp wants to merge 1 commit into
4.0from
bphilip/image-arch-support

Conversation

@binujp

@binujp binujp commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Summary

  • declare each Azure Linux image's supported architectures explicitly
  • synchronize the vendored azldev schema with the updated image configuration model

Compatibility

The field remains optional so azldev can roll out while the Azure Linux repository change percolates everywhere.

Rationale

Explicit per-image declarations avoid implicit inheritance and make each migrated image definition self-contained.

Copilot AI balanced review requested due to automatic review settings September 9, 2026 19:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟡 Changes recommended

The pinned azldev version rejects the newly added architectures keys as unknown fields.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Makes supported architectures explicit for every image and updates the vendored schema accordingly.

Changes:

  • Declares architectures for all images.
  • Restricts Gen1 images to x86_64.
  • Requires architectures in the schema.
File summaries
File Description
base/images/images.toml Adds per-image architecture lists.
external/schemas/azldev.schema.json Requires the new image field.
Review details
  • Files reviewed: 2/2 changed files
  • Comments generated: 1
  • Review effort level: Balanced

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread base/images/images.toml
Remove the top-level default-image-architectures setting; every image
now declares its own supported architectures list. Sync the vendored
azldev schema to match the updated azldev implementation.

Keep the field optional so azldev can roll out while the Azure Linux repository change percolates everywhere.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: f91d50d8-beef-4a67-a321-beba16e98506
@binujp
binujp force-pushed the bphilip/image-arch-support branch from 8457453 to 6e504c9 Compare September 10, 2026 18:32
Copilot AI review requested due to automatic review settings September 10, 2026 18:32
@binujp binujp changed the title feat(images): require explicit per-image architectures feat(images): add explicit per-image architectures Sep 10, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔵 Needs a closer look

The pinned azldev version rejects the newly added configuration field.

Review details

Suppressed comments (1)

base/images/images.toml:19

  • The repository is still pinned by .azldev-version to azldev commit faaa0f4…, whose ImageConfig has no architectures field and whose normal config loader rejects unknown TOML fields. Consequently, loading base/project.toml with the pinned CLI will fail on this first declaration (and every azldev command that loads the project config is affected). Please update .azldev-version to a compatible azldev revision in this PR before adding these keys.
architectures = ["x86_64", "aarch64"]
  • Files reviewed: 2/2 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants