Our company is using Schematics service to create entire environments. We have run into several issues and challenges to using schematics service to stand up customer envs
A simple answer we often received was, why don't we just use the terraform command line tool instead of using the IBM Cloud Schematics service.
And sometimes it was hard for us to understand why our own use of schematics service was.
IBM Cloud Schematics service
pulls github .tf files that are created by the user to create environments
Customers can run the opensource terraform tool to create resources just like the schematics service for their .tf files. It's terribly not too different from the IBM Cloud Schematics service product.
IBM Cloud Schematics service try to win more customers and increase its value by offering drag and drop tree-directory style for Terraform configurations from the terraform registry. It would allow for codeless bespoke env creation. This should allow users to drag and drop resources from a terraform registry that they want, then create .tf files from that config., export them, and import them as well into the service.
This allows for avoiding connecting to github to pull files, and also allows complicated headaches with writing in HCL, modules and the rest that are changing more rapidly than a common programming language. These features will enabling more customers to try IaC. Terraform 11 and 12 syntax has differences from Terraform 14, the latest supported by IBM Cloud. The latest is Terraform 15, which may have more differences.
Do not place IBM confidential, company confidential, or personal information into any field.