From b413061fd80e23b880b592f1c114bb13ed8df033 Mon Sep 17 00:00:00 2001 From: Christoph Tavan Date: Mon, 7 Aug 2017 10:52:30 +0200 Subject: [PATCH] Document how to provide provider plugin overrides The docs did not mention that it is possible to provide overrides for specific plugins by placing them into a `terraform.d/plugins/os_arch/` directory inside the working dir. Closes #15727. --- website/docs/commands/init.html.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/website/docs/commands/init.html.markdown b/website/docs/commands/init.html.markdown index 851aa8e3dc..d88ff6a261 100644 --- a/website/docs/commands/init.html.markdown +++ b/website/docs/commands/init.html.markdown @@ -135,6 +135,13 @@ the desired providers into a local directory and using the additonal option is consulted, which prevents Terraform from making requests to the plugin repository or looking for plugins in other local directories. +In case you only want to override specific providers and have Terraform +download all other providers from the plugin repository, you can place those +specific provider plugins in a `terraform.d/plugins/os_arch/` directory inside +the working directory (e.g. `terraform.d/plugins/darwin_amd64/` on Mac OS X). +Upon `init` Terraform will then use all providers found in this directory and +download all missing providers from the plugin repository. + When plugins are automatically downloaded and installed, by default the contents are verified against an official HashiCorp release signature to ensure that they were not corrupted or tampered with during download. It is