feat: add NetRC support to the provider installer

[aaklilu]

An interim solution to lack of credential while downloading provider archives.

Fixes #29349

Target Release

1.10.x

Draft CHANGELOG entry

ENHANCEMENTS

• Provider installation now support NetRC and utilises the credentials configured in .netrc file. Similar to module downloads.

[crw]

Thanks for this submission!

[crw]

Hi @aaklilu, we discussed this in triage today. Generally speaking there is agreement that this is probably the correct approach. The main blocker to doing a full review is maintainer availability. My best guess is that we'll check back in on this PR mid-November to consider a review. I just wanted to set expectations up-front as to timelines. Thanks again for this submission.

[aaklilu]

Hi @aaklilu, we discussed this in triage today. Generally speaking there is agreement that this is probably the correct approach. The main blocker to doing a full review is maintainer availability. My best guess is that we'll check back in on this PR mid-November to consider a review. I just wanted to set expectations up-front as to timelines. Thanks again for this submission.

Thank you @crw for the update.

[crw]

Hi @aaklilu, I have been off for the past three weeks so apologies for this late update. As this change would not make a difference for the Hashicorp Terraform Registry (public or private via Enterprise), this change is unlikely to be prioritized in the near future. If you think this is incorrect, especially if you think the Hashicorp enterprise registry could benefit from this change, please let me know as that could change the decision-making process. Thanks very much!

[aaklilu]

Hi @aaklilu, I have been off for the past three weeks so apologies for this late update. As this change would not make a difference for the Hashicorp Terraform Registry (public or private via Enterprise), this change is unlikely to be prioritized in the near future. If you think this is incorrect, especially if you think the Hashicorp enterprise registry could benefit from this change, please let me know as that could change the decision-making process. Thanks very much!

It's fine, thanks for the update @crw

[liamcervante]

Hi @aaklilu, I'm happy to review and merge this. The change actually looks fine to me, but before I merge it could you take a look at #36022 and let me know if the documentation update there is actually understandable for someone using this externally? Thanks!

[aaklilu]

Hi @aaklilu, I'm happy to review and merge this. The change actually looks fine to me, but before I merge it could you take a look at #36022 and let me know if the documentation update there is actually understandable for someone using this externally? Thanks!

Hey @liamcervante its quite clear. Thanks!

[liamcervante]

I'm just waiting for one of our tech writers to okay my docs change in #36022, and then we can merge both together.

[github-actions]

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

[github-actions]

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.