Describe the Feature

This feature is an enhancement for Atmos Components to be able to fetch terraform modules from private registries based on https.

Expected Behavior

Ability to fetch terraform modules from private terraform registries

Use Case

Many companies use private registries and repositories to:

• Decoupled from vendor servers.
• Fasten their pipeline builds.
• Avoid breaking routine work when problems appear with vendor servers.
• Improve security.
• etc...

E.g:

• Docker
• Apt
• Rpm
• Npm
• Maven
• Helm
• Terraform
• etc...

Describe Ideal Solution

Option 1:

After running terraform login <some terraform private registry>, credentials file being created under ~/.terraform.d/credentials.tfrc.json .
If Atmos can look for this path on component initialization, it might solve the problem for any terraform registry use case as long as it work with native terraform registry authentication.

Reference: ==> Terraform Credentials Storage

Option 2 (might be the preferred):

Atmos will fetch the following environment variable in case of private registries TF_TOKEN_cloudposse_jfrog_io=<terraform-private-registry-token> , terraform translate the uri to cloudposse.jfrog.io .

Reference: ==> Environment Variables Credentials

Alternatives Considered

No response

Additional Context

No response