CameronHudson8
commented
10 months ago Unfortunately, while it is possible to terraform apply the TriggerTemplate after changing the capitalization, Terraform subsequently emits an error, and the resource is tainted. So there isn't a clean workaround at the moment.
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ module.tekton_pipelines.module.trigger_templates.kubernetes_manifest.trigger_template_github_image_pr,
│ provider "provider[\"registry.terraform.io/hashicorp/kubernetes\"]"
│ produced an unexpected new value: .object: wrong final value type:
│ attribute "spec": attribute "resourceTemplates" is required.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵Performing terraform plan after this shows a persistent diff in the state.
# module.tekton_pipelines.module.trigger_templates.kubernetes_manifest.trigger_template_github_image_pr is tainted, so must be replaced
-/+ resource "kubernetes_manifest" "trigger_template_github_image_pr" {
~ object = {
~ spec = {
+ resourceTemplates = [
+ {
+ apiVersion = "tekton.dev/v1"
+ kind = "PipelineRun"
+ metadata = {
+ generateName = "github-image-pr-"
}
+ spec = {
+ params = [
+ {
+ name = "github-status-url"
+ value = "$(tt.params.github-status-url)"
},
+ {
+ name = "pr-number"
+ value = "$(tt.params.pr-number)"
},
+ {
+ name = "repo-name"
+ value = "$(tt.params.repo-name)"
},
+ {
+ name = "repo-url"
+ value = "$(tt.params.repo-url)"
},
]
+ pipelineRef = {
+ name = "github-image-pr"
}
+ taskRunTemplate = {
+ serviceAccountName = "cicd-bot"
}
+ workspaces = [
+ {
+ name = "default"
+ volumeClaimTemplate = {
+ spec = {
+ accessModes = [
+ "ReadWriteOnce",
]
+ resources = {
+ requests = {
+ storage = "512Mi"
}
}
}
}
},
]
}
},
]
- resourcetemplates = [
- {
- apiVersion = "tekton.dev/v1"
- kind = "PipelineRun"
- metadata = {
- generateName = "github-image-pr-"
}
- spec = {
- params = [
- {
- name = "github-status-url"
- value = "$(tt.params.github-status-url)"
},
- {
- name = "pr-number"
- value = "$(tt.params.pr-number)"
},
- {
- name = "repo-name"
- value = "$(tt.params.repo-name)"
},
- {
- name = "repo-url"
- value = "$(tt.params.repo-url)"
},
]
- pipelineRef = {
- name = "github-image-pr"
}
- taskRunTemplate = {
- serviceAccountName = "cicd-bot"
}
- workspaces = [
- {
- name = "default"
- volumeClaimTemplate = {
- spec = {
- accessModes = [
- "ReadWriteOnce",
]
- resources = {
- requests = {
- storage = "512Mi"
}
}
}
}
},
]
}
},
]
# (1 unchanged attribute hidden)
}
# (3 unchanged attributes hidden)
}
# (1 unchanged attribute hidden)
}
savitaashture
Expected Behavior
It should be possible to create a TriggerTemplate using the Terraform
kubernetes_manifestresource, based on the examples from the Tekton documentation.Actual Behavior
Creation fails due to a capitalization conflict in the field
.spec.resourcetemplates.Steps to Reproduce the Problem
hashicorp/kubernetesprovider version2.23.0.kubernetes_manifestfor the TriggerTemplate, and specify the field.spec.resourcetemplates(example below).terraform planorterraform applyand encounter an error (example below)..spec.resourcetemplatesto.spec.resourceTemplates.terraform planandterraform applysuccessfully.Additional Info
Kubernetes version:
Output of
kubectl version:Tekton Pipeline version:
Output of
tkn versionorkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'Terraform code
Logs:
PS: Thank you for creating and maintaining Tekton. It rocks! 🙂