Skip to content

Commit

Permalink
Capitalization consistency for resorucetemplates
Browse files Browse the repository at this point in the history
Some of the documentation has the wrong capitalization for this spec. We should ensure
the fields are always accurate given the issues mentioned in #526
  • Loading branch information
jmcshane authored and tekton-robot committed Apr 14, 2021
1 parent 6ea31d9 commit 4b9aa31
Show file tree
Hide file tree
Showing 5 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/eventlisteners.md
Original file line number Diff line number Diff line change
Expand Up @@ -135,7 +135,7 @@ triggers:
spec:
params:
- name: "my-param-name"
resourceTemplates:
resourcetemplates:
- apiVersion: "tekton.dev/v1beta1"
kind: TaskRun
metadata:
Expand Down
2 changes: 1 addition & 1 deletion docs/triggers.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ triggers:
spec:
params:
- name: "my-param-name"
resourceTemplates:
resourcetemplates:
- apiVersion: "tekton.dev/v1beta1"
kind: TaskRun
metadata:
Expand Down
2 changes: 1 addition & 1 deletion docs/triggertemplates.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ A `TriggerTemplate` allows you to declare parameters supplied by the associated
* Tekton applies the value of the `default` field for each entry in the `params` array of your `TriggerTemplate` if it can't find a corresponding
value in the associated `TriggerBinding` or cannot successfully extract the value from an HTTP header or body payload.

* You can reference `tt.params` in the `resourceTemplates` section of your `TriggerTemplate` to make your `TriggerTemplate` reusable.
* You can reference `tt.params` in the `resourcetemplates` section of your `TriggerTemplate` to make your `TriggerTemplate` reusable.

* When you specify parameters in your resource template definitions, Tekton replaces the specified string with the parameter name, for example `$(tt.params.name)`.
Therefore, simple string and number value replacements work fine directly in your YAML file. However, if a string has a numerical prefix, such as `123abcd`,
Expand Down
2 changes: 1 addition & 1 deletion examples/eventlisteners/cel-eventlistener-interceptor.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ spec:
spec:
params:
- name: sha
resourceTemplates:
resourcetemplates:
- apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ spec:
params:
- name: sha
- name: branch
resourceTemplates:
resourcetemplates:
- apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
Expand Down

0 comments on commit 4b9aa31

Please sign in to comment.