Skip to content

Backport of providers lock: include test files when loading configuration into v1.14#37904

Merged
radeksimko merged 1 commit intov1.14from
backport/liamcervante/37841/virtually-allowing-insect
Nov 25, 2025
Merged

Backport of providers lock: include test files when loading configuration into v1.14#37904
radeksimko merged 1 commit intov1.14from
backport/liamcervante/37841/virtually-allowing-insect

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Backport

This PR is auto-generated from #37851 to be assessed for backporting due to the inclusion of the label 1.14-backport.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@dsa0x
This person should resolve the merge-conflict(s) by either:

  • Manually completing the cherry picks into this branch
  • Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/terraform/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


This PR updates the providers lock command so that it also includes providers embedded in Terraform test modules. This makes providers lock match the behaviour of init in terms of provider discovery, and makes sense to me in terms of discovering provider requirements.

I've marked this as a backport into 1.14.1 as I do think it is fixing a bug, but it does also necessarily introduce a new flag to providers lock so maybe that's enough to mean this should be delayed to 1.15.0. I'm happy to take that feedback if people think so.

Fixes #37841

Target Release

1.14.1

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

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

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

Overview of commits

@hashicorp-cla-app
Copy link
Copy Markdown

hashicorp-cla-app bot commented Nov 17, 2025

CLA assistant check
All committers have signed the CLA.

@dsa0x dsa0x force-pushed the backport/liamcervante/37841/virtually-allowing-insect branch from d3f8c83 to 4bfb3ab Compare November 17, 2025 07:39
@dsa0x
Copy link
Copy Markdown
Member

dsa0x commented Nov 17, 2025

🚨🚨🚨 Not to be merged until next week

@dsa0x dsa0x marked this pull request as ready for review November 24, 2025 14:57
@dsa0x dsa0x requested a review from a team as a code owner November 24, 2025 14:57
Copy link
Copy Markdown
Member

@radeksimko radeksimko left a comment

Choose a reason for hiding this comment

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

Merging ahead of tomorrow's 1.14.1 release.

@radeksimko radeksimko merged commit b0ebd07 into v1.14 Nov 25, 2025
16 of 17 checks passed
@radeksimko radeksimko deleted the backport/liamcervante/37841/virtually-allowing-insect branch November 25, 2025 13:17
@github-actions
Copy link
Copy Markdown
Contributor Author

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 Dec 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants