Skip to content
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

fix(manager/terraform/lockfile): use registryURL defined in lockfile #28886

Merged
merged 2 commits into from
May 7, 2024

Conversation

secustor
Copy link
Collaborator

@secustor secustor commented May 6, 2024

Changes

Prefer the registryURL of locks defined in .terraform.lock.hcl.
This allows to use OpenTofu without explicitly defining it with registryUrls.

Context

Solves #28818

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

@secustor secustor requested review from viceice and rarkins May 6, 2024 22:38
@rarkins rarkins added this pull request to the merge queue May 7, 2024
Merged via the queue into renovatebot:main with commit cbbfcd1 May 7, 2024
37 checks passed
@secustor secustor deleted the fix/opentofu-lockfile-generation branch May 7, 2024 04:56
@@ -191,6 +187,10 @@ export async function updateArtifacts({
continue;
}
}

// use registryURL defined in the update and fall back to the one defined in the lockfile
const registryUrl = registryUrls?.[0] ?? updateLock.registryUrl;
Copy link
Member

Choose a reason for hiding this comment

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

we should read it on extract, so no user intervention is required .

the datasource is always filling registry url, so you fallback will probably never used at runtime

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I agree we should detect Terraform vs OpenTofu during extract, though this is not possible if there is no lock file. At least I'm not aware there is a reliable way.

This is picked up as expected, I have tested / debugged it against a real repo.

@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 37.347.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 7, 2024
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.

4 participants