69650b0bbc
As part of moving to the next-generation HCL implementation, Terraform Core is getting its own representation of configuration schema that is tailored for configuration-processing use-cases. The capabilities of this are a subset of the helper/schema model primarily concerned with the configuration structure and value types, leaving detailed validation and defaults for helper/schema to still solve. These new methods allow mechanical creation of a schema in the new Core schema model from a schema expressed in the helper/schema model. This is not yet used as of this commit, but will be used later to implement some new ResourceProvider methods that will allow core to obtain the schema for provider, resource and data source configuration while remaining source-compatible with existing provider implementations. |
||
|---|---|---|
| .. | ||
| README.md | ||
| backend.go | ||
| backend_test.go | ||
| core_schema.go | ||
| core_schema_test.go | ||
| data_source_resource_shim.go | ||
| equal.go | ||
| field_reader.go | ||
| field_reader_config.go | ||
| field_reader_config_test.go | ||
| field_reader_diff.go | ||
| field_reader_diff_test.go | ||
| field_reader_map.go | ||
| field_reader_map_test.go | ||
| field_reader_multi.go | ||
| field_reader_multi_test.go | ||
| field_reader_test.go | ||
| field_writer.go | ||
| field_writer_map.go | ||
| field_writer_map_test.go | ||
| getsource_string.go | ||
| provider.go | ||
| provider_test.go | ||
| provisioner.go | ||
| provisioner_test.go | ||
| resource.go | ||
| resource_data.go | ||
| resource_data_get_source.go | ||
| resource_data_test.go | ||
| resource_importer.go | ||
| resource_test.go | ||
| resource_timeout.go | ||
| resource_timeout_test.go | ||
| schema.go | ||
| schema_test.go | ||
| serialize.go | ||
| serialize_test.go | ||
| set.go | ||
| set_test.go | ||
| testing.go | ||
| valuetype.go | ||
| valuetype_string.go | ||
README.md
Terraform Helper Lib: schema
The schema package provides a high-level interface for writing resource
providers for Terraform.
If you're writing a resource provider, we recommend you use this package.
The interface exposed by this package is much friendlier than trying to write to the Terraform API directly. The core Terraform API is low-level and built for maximum flexibility and control, whereas this library is built as a framework around that to more easily write common providers.