You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tfexec exported error types - for example, tfexec.ErrCLIUsage and tfexec.ErrTFVersionMismatch - are implemented by parsing Terraform's human-readable error output using regular expressions.
Since this log output is subject to frequent changes and not covered by the v1.0 compatibility promises, users of these error types are at risk of having their code broken by new Terraform versions, requiring them (in the best case) to keep terraform-exec updated.
This error parsing code also seems to be a leading cause of terraform-exec nightly test failures.
Are these error types useful enough to consumers to continue maintaining them? Should we remove them prior to v1.0.0? Are there any really good use cases?
The text was updated successfully, but these errors were encountered:
To gain some insight on potential usage in the wild, I spent some time with GitHub's code search (fuzzy matching on tfexec.{TYPE} because it'd be difficult to ignore non-tfexec things and most Go code doesn't use aliasing), e.g.
The tfexec exported error types - for example,
tfexec.ErrCLIUsage
andtfexec.ErrTFVersionMismatch
- are implemented by parsing Terraform's human-readable error output using regular expressions.Since this log output is subject to frequent changes and not covered by the v1.0 compatibility promises, users of these error types are at risk of having their code broken by new Terraform versions, requiring them (in the best case) to keep terraform-exec updated.
This error parsing code also seems to be a leading cause of terraform-exec nightly test failures.
Are these error types useful enough to consumers to continue maintaining them? Should we remove them prior to v1.0.0? Are there any really good use cases?
The text was updated successfully, but these errors were encountered: