init -from-module #16487
init -from-module #16487
Conversation
Add GetModule for the cli to initialize from a regisry module source. Storage.GetModule fetches a module using the same detection and discovery as used by the normal module loading. The final copy is still done by module.GetCopy to remove vcs files.
This will enable copying any module source into a target directory.
There was a problem hiding this comment.
LGTM!
It'd also be good to add a TF_ACC-blocked test to the command/e2etest suite that installs something from the real registry just as a final validation that this is all working end-to-end, since we're going to start describing this as part of the getting started guide section on modules when we introduce the module registry and so this workflow will get more prominent.
|
I'll push the the e2e test in a separate PR. |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Add GetModule for the cli to initialize from a regisry module source.
Storage.GetModule fetches a module using the same detection and
discovery as used by the normal module loading. The final copy is still
done by module.GetCopy to remove vcs files.