6 Commits (80d4c4841900bc4e6a555ffce21e3e2eae1fbe03)

Author	SHA1	Message	Date
Liam Cervante	3d211eb42f	Fix crash when importing a resource with complex sensitive attributes (#34996)	2 years ago
Daniel Schmidt	ba043a04d5	in import-generated code represent JSON values in HCL instead of as strings ... This makes the value easier to read and is mostly an aesthetic change. Closes #34444	2 years ago
CJ Horton	98b81d3c50	add missing copyright headers	3 years ago
kmoe	4015f1aa30	genconfig: do not generate null NestingSingle blocks (#33213) ... * genconfig: fix nil nested block panic * always InternalValidate test schemas * genconfig: null NestingSingle blocks should be absent A NestingSingle block that is null in state should be completely absent from config.	3 years ago
Liam Cervante	cd06543b39	plannable import: fix config generation printing empty collections instead of null values (#33183)	3 years ago
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>	3 years ago