Dependency management for Terraform objects

[chanwit]

As we have introduced a new component model, the TF-controller primitive module, it's natural to have dependency management for this model because a primitive module contains a single Terraform resource.

Here's the dependency proposal based on the new component model.

---
apiVersion: infra.contrib.fluxcd.io/v1alpha1
kind: Terraform
metadata:
  name: aws-s3-bucket
  namespace: flux-system
spec:
  path: aws_s3_bucket
  values:
    bucket: my-tf-controller-test-bucket
    tags:
      Environment: Dev
      Name: My bucket
  sourceRef:
    kind: OCIRepository
    name: aws-package-v4.33.0
  approvePlan: auto
  interval: 2m
  destroyResourcesOnDeletion: true
  writeOutputsToSecret:
    name: aws-s3-bucket-outputs
    outputs:
    - arn
    - bucket
  runnerPodTemplate:
    spec:
      envFrom:
      - secretRef:
          name: aws-credentials
---
apiVersion: infra.contrib.fluxcd.io/v1alpha1
kind: Terraform
metadata:
  name: example-bucket-acl
  namespace: flux-system
spec:
  path: aws_s3_bucket_acl
  values:
    acl: private
    bucket: ${{ .aws_s3_bucket.bucket }}
  sourceRef:
    kind: OCIRepository
    name: aws-package-v4.33.0
  approvePlan: auto
  interval: 3m
  dependsOn:
  - name: aws-s3-bucket
  readInputsFromSecrets:
  - name: aws-s3-bucket-outputs
    as: aws_s3_bucket
  runnerPodTemplate:
    spec:
      envFrom:
      - secretRef:
          name: aws-credentials

We must tweak some things from the above design to provide a better OOTB experience.

• Outputs by default
• Value referencing

[chanwit]

This implementation will land into the main branch by v0.13.0-rc.8.

[artem-nefedov]

Is "{{ $.aws_s3_bucket.bucket }}" templating actually supported by the controller, or was it just a copy-paste from a helm chart?

[chanwit]

It's a feature in recent RCs.
I'll confirm its behavior right after the v0.13 stable gets released.