ConfigMap as module source

[reegnz]

What problem are you facing?

My kubernetes cluster does not have network access to my git server.
Concatenating all of the tf files into a single string and using it with Inline is my only option today that doesn't try to pull the module source from a system outside kubernetes (unless I host tar.gz-d modules in-cluster).

How could Official Terraform Provider help solve your problem?

A more kubernetes-native way would be to support terraform modules stored in configmaps.

If one could define module source to come from a configmap, then it would be very easy to package up an existing terraform module into kubernetes manifests and deploy them like any other kubernetes resource.
This would be a welcome improvement over Inline module sources.

Example:

kustomization.yaml:

configMapGenerator:
- name: my-terrfaorm-module
  files:
  - main.tf
  - variables.tf
  - outputs.tf
  - versions.tf

kustomize build | kubectl apply -n crossplane-system -

workspace.yaml:

apiVersion: tf.upbound.io/v1beta1
kind: Workspace
metadata:
  name: my-terraform-module
spec:
  forProvider:
    source: ConfigMap
    module:
      name: my-terraform-module
      namespace: crossplane-system

[ytsarev]

The feature makes sense! Thanks for documenting it.

[alkuzad]

I just use Helm. File.Get loop to include all files inside the inline. Therefore we just copied our current TF structure into folder "terraform" inside a chart. This enables normal TF work if you want to (assuming you extend provider.tf with configuration for the real cloud, provider.tf to be include has to be ONLY for aliases, not for the provider configured in crossplane ProviderConfig).

{{/*
Helper to setup Terraform Files

Include like this to ensure proper formatting:

{{ include "compositionTerraform.include" . | trim | indent 14 }}

*/}}
{{- define "compositionTerraform.include" -}}
{{- $currentScope := .}}
{{- with $currentScope}}
{{- range (tuple "provider" "variables" "locals" "data" "main" "outputs") }}
{{- $file := $currentScope.Files.Glob (printf "terraform/%s.tf" .) }}
{{- if $file }}
{{ $currentScope.Files.Get (printf "terraform/%s.tf" .) | trim }}
{{ end -}}
{{- end }}
{{- end }}
{{- end }}

[reegnz]

Thanks @alkuzad, that sounds like a reasonable alternative.

[vrabbi]

this would be extremely beneficial for us as well

[senare]

Yes, I would like this to ...

or atleast the possibility to have a way of including the TF into the configuration once I build/bundle crossplane into a OCI image (sry I am not sure of the correct terminology here )

[joneshf]

Since this request started with a kustomize example, another workaround is to use replacements to substitute a field from a ConfigMap into the module field.

If you have a single main.tf file, you'd do something like:

# kustomization.yaml

configMapGenerator:
  - name: my-terraform-module
    files:
      - main.tf

replacements:
  - source:
      fieldPath: data.[main.tf]
      kind: ConfigMap
      name: my-terraform-module
      version: v1
    targets:
      - fieldPaths:
          - spec.forProvider.module
        select:
          group: tf.upbound.io
          kind: Workspace
          name: my-terraform-module
          version: v1beta1

resources:
  - workspace.yaml

# workspace.yaml

apiVersion: tf.upbound.io/v1beta1
kind: Workspace
metadata:
  name: my-terraform-module
spec:
  forProvider:
    source: ConfigMap
    module: <Kustomize will replace this with the contents of `main.tf`>

I'm not entirely sure how you'd do this with multiple files, but maybe there's some way to concatenate those files into a single string with some other generator/transformer? The vars field seems like it would make that possible, but it's deprecated.

If there's not a way to combine multiple files, you can have multiple Workspaces, one for each Terraform file. They seem to get combined into a single module? on the Terraform side of things.