Skip to content

Conversation

@xiehan
Copy link
Member

@xiehan xiehan commented Jul 16, 2024

I'm not familiar enough with platform-specific differences to know whether our ability to produce a build is enough confidence that this will work, or whether we need to do manual testing to verify. We did unfortunately figure out that our existing E2E tests won't work for this platform, so any verification will need to be manual.

Fixes #32719

Target Release

1.15.x, or we could backport to 1.14.x, this is relatively flexible

Rollback Plan

  • If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

n/a

CHANGELOG entry

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

@apparentlymart
Copy link
Contributor

I expect there's probably context here that I'm not aware of and so what I'm about to say might be redundant, but just to make sure:

In the past when we've introduced new officially-supported platforms (darwin_arm64 being the most recent example) we've asked the developers of the official providers to lead first and produce at least one or two provider releases that support the new platform.

If Terraform CLI/Core were to go first then we'd be publishing something that's more-or-less useless, because a Terraform Core without any providers doesn't do anything of value. I would expect it to cause folks to open bug reports in this repository saying that provider installation failed for them, and that to then create indirect pressure for provider developers to rush to make new releases supporting the new platform.

I mention this only because none of the official providers I quickly checked seems to be offering a windows_arm64 build for its latest release. If there's already a plan to make that happen before the first Core release supporting that platform, or if there's some different plan to deliver this which bypasses the need for providers to go first, then of course please ignore me. 😀

@crw
Copy link
Contributor

crw commented Jul 18, 2024

This is excellent context, thank you!

mildwonkey
mildwonkey previously approved these changes Sep 26, 2025
Copy link
Contributor

@mildwonkey mildwonkey left a comment

Choose a reason for hiding this comment

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

:shipit: We have some windows-arm64 providers now, let's do it!

@xiehan xiehan force-pushed the releng/windows-arm64 branch from 2ebc7c1 to 08c95d8 Compare September 26, 2025 14:39
@xiehan xiehan requested a review from a team as a code owner September 26, 2025 14:39
@xiehan xiehan merged commit eae5ac1 into main Sep 26, 2025
45 checks passed
@xiehan xiehan deleted the releng/windows-arm64 branch September 26, 2025 18:35
@github-actions
Copy link
Contributor

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support for Windows Arm64 binaries

4 participants