🤔 Choose when runs should be triggered by VCS changes.

[obervinov]

Operator Version, Kind and Kubernetes Version

• Operator version: 2.1.0
• Kind: Workspace
• Kubernetes version: v1.28.2

YAML Manifest File

apiVersion: app.terraform.io/v1alpha2
kind: Workspace
metadata:
  creationTimestamp: "2023-12-29T21:43:46Z"
  finalizers:
  - workspace.app.terraform.io/finalizer
  generation: 1
  name: dns-workspace
  namespace: terraform-operator
spec:
  agentPool:
    name: kubernetes-tfc-agent-pool
  allowDestroyPlan: true
  applyMethod: manual
  description: For managing the DNS records
  executionMode: agent
  name: dns-workspace
  notifications:
  - emailUsers:
    - obervinov@example.com
    enabled: true
    name: 'Terraform Cloud: DNS'
    triggers:
    - run:applying
    - assessment:check_failure
    - run:completed
    - assessment:drifted
    - run:errored
    - assessment:failed
    - assessment:failed
    type: email
  organization: ***
  tags:
  - dns
  - terraform-operator
  - automatic-deployment
  terraformVersion: 1.6.6
  token:
    secretKeyRef:
      key: token
      name: tfc-operator
  versionControl:
    oAuthTokenID: ***
    repository: infrastructure
  workingDirectory: infra/dns

Output Log

Kubectl Outputs

Question

In the Web UI settings of Terraform Cloud, I can override the VCS Triggers setting by setting the parameter to Only trigger runs when files in specified paths change.
This allows for multi-repository setups with different workspaces to avoid triggering all workspaces at once when a commit is made to the repository. However, I don't see support for this functionality in the API specification through the CRD Workspace.
Is it possible to change the value of VCS Triggers, or will I have to abandon the Terraform operator in favor of manually creating workspaces through the web UI?

References

Community Note

• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

[razorsk8jz]

This is also a requirement for us as we trigger based on pattern changes using more of a monorepo for our terraform projects - this makes the operator unusable for us

[lee5i3]

We need this too, unfortunately it keeps putting the triggers back every time we change the triggers in the UI, we either need this functionality or ignore changes in the UI

[obervinov]

@razorsk8jz @lee5i3 If you don’t mind, please support this PR (it should solve the problem described) #496