Do we need terraform rulesets before building drag, drop, and link

[mayansalama]

I've got some thoughts about how we bind and group components.

1. Are links decorative or do they provide info to terraform?
2. If they provide info to terraform, how do we define the ruleset for what components can be linked together?
3. Are the rule sets something we can dynamically generate from terraform spec? Manually writing these out will suck.
4. Is the project grouping the only thing we're doing to group components? For example, are we doing namespaces in GKE etc.

[TomKlimovski]

• I think links should provide info to TF
• we can offer granularity into namespace level, but as we develop we need to be clear we're not reinventing GCP. I'm hoping this decision evolves organically
• any ideas around the rulesets?

[mayansalama]

I have a feeling that we could validate using terraform dry runs, but who knows how fast that's gonna be. Might be a fun async validation problem. I don't think we could easily extract rulesets direct from the terraform provider. A better approach would be using the API spec, but I don't think there's a direct mapping between terraform schemas and the GCP APIs.

Either way - I think we're either reverse engineering terraform or reverse engineering the GCP api

[mayansalama]

Actually just had a look at the terraform source: https://github.com/terraform-providers/terraform-provider-google/blob/master/google/resource_bigquery_data_transfer_config.go

This one is auto generated (including the rulesets I guess) so I wonder if we reverse engineer that into something useful.

[TomKlimovski]

keen to reverse-engineer! let's GO