tree 8d7baffd1a579cbedd777495340e47de606c5a32
parent cd7b46b136bbdd801828d3664064bc9a68a04cfb
author Alisdair McDiarmid <alisdair@users.noreply.github.com> 1694443011 -0400
committer GitHub <noreply@github.com> 1694443011 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJk/yYDCRBK7hj4Ov3rIwAA3w0IAEVQnhEzJhn+rSHrGVjBDv0T
 Z3WOC2dSYxauIPnxM1QK2V3p8RnP10AeQgm1gTmqRx1ntcExxq/Lt+x17gmlzF6g
 0Ur9jhDFXFCn2XvxXSc+xcM4s2VsCcYtLD1B4lkNNT2LOF/BEcPMDV5puGswdsSM
 JT0Y/zi/Ja3Ctq8iENigiflIE1Qui7hHTomnibkD7i+87Tn4mnDW6V5VyNRylvXm
 PsR3SlfQrhWZIQnFiRnnfLr9PVZ7JMIio+GvLSP5YcmQOr1tjBhVUKuvzGQV6FqG
 BVtCBOsspeWxhfg+yCbUUKazEuGYvlQUpR2oDAmdsZJffuuUmcPhCVmNcCrrMgY=
 =U6yb
 -----END PGP SIGNATURE-----
 

Update README to explain when not to use this library

By design, the `terraform-json` library is not always suitable for every application. Its name and prominence may cause those integrating with Terraform to assume otherwise.

This commit expands the README to attempt to clarify situations where the `terraform-json` library is not appropriate, explaining why and what to do instead.