You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Sarah French da87dbb60f command/init: Event ordering changes to support the policy feature (#38699) ... This change makes some reversion of changes to the init command created during the PSS project, in order to support the Policy feature. Also see this change, which altered the provider download logic: https://github.com/hashicorp/terraform/pull/38648 Broadly this change's goal is to make module download happen after the backend is initialised. This was how init was structured in the past, and for a while in v1.15 of Terraform this step was moved to before backend initialisation, as the first provider download step downloaded all providers in the config (so loading the entire config was needed at that point in init). The changes make this code go back to resembling the old order of events in init prior to v1.15. See this for reference: https://github.com/hashicorp/terraform/blob/v1.14.9/internal/command/init_run.go To facilitate this change some code needed to be updated to use a config.Module as input, which is obtained by parsing the root module only. Previously once the whole configuration was parsed, after module download, that code was being passed an entire config.Config variable. There are also some small refactoring and improvements, e.g. removing the `header` boolean from the init command implementation, as it had become redundant over time.		3 weeks ago
..
foo	…
main.tf	…
output.jsonlog	command/init: Event ordering changes to support the policy feature (#38699)	3 weeks ago