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
Schema contracts are huge, monotlithic records at the moment. For example, the AWS Nickel contract is a whopping 30M of code. This quickly becomes unmanageable and slow.
Ideally, these contracts should be built up out of modular pieces, say one generic contract for Terraform builtins and then one contract per provider resource. These should be importable on a piecemeal basis so that tf-ncl library authors can import just those resource contracts that they need.
The text was updated successfully, but these errors were encountered:
Schema contracts are huge, monotlithic records at the moment. For example, the AWS Nickel contract is a whopping 30M of code. This quickly becomes unmanageable and slow.
Ideally, these contracts should be built up out of modular pieces, say one generic contract for Terraform builtins and then one contract per provider resource. These should be importable on a piecemeal basis so that tf-ncl library authors can import just those resource contracts that they need.
The text was updated successfully, but these errors were encountered: