Liam Cervante 79f7f59155 Plannable import: Generate config for imported resources during the plan. (#33153) ... * command: keep our promises * remove some nil config checks Remove some of the safety checks that ensure plan nodes have config attached at the appropriate time. * add GeneratedConfig to plan changes objects Add a new GeneratedConfig field alongside Importing in plan changes. * add config generation package The genconfig package implements HCL config generation from provider state values. Thanks to @mildwonkey whose implementation of terraform add is the basis for this package. * generate config during plan If a resource is being imported and does not already have config, attempt to generate that config during planning. The config is generated from the state as an HCL string, and then parsed back into an hcl.Body to attach to the plan graph node. The generated config string is attached to the change emitted by the plan. * complete config generation prototype, and add tests --------- Co-authored-by: Katy Moe <katy@katy.moe>		2023-05-11 08:38:37 +02:00
..
doc.go	Plannable import: Generate config for imported resources during the plan. (#33153)	2023-05-11 08:38:37 +02:00
generate_config_test.go	Plannable import: Generate config for imported resources during the plan. (#33153)	2023-05-11 08:38:37 +02:00
generate_config.go	Plannable import: Generate config for imported resources during the plan. (#33153)	2023-05-11 08:38:37 +02:00