Follow naming conventions for resourceTemplates

[savitaashture]

As per the standards the JSON or YAML keys should follow capitalization but resourcetemplates keys doesn't follow that. Changing resourcetemplates to resourceTemplates

Signed-off-by: Savita Ashture sashture@redhat.com"

Changes

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• [ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• [ ] Has Tests included if any functionality added or changed
• [ ] Follows the commit message standard
• [ ] Meets the Tekton contributor standards (including functionality, content, code)
• [ ] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• [ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• [ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[savitaashture]

What would happen if some resource already exists with that version? Don't we need a conversion function?

Its not needed because it works for both resourceTemplates and resourcetemplates i have verified

[khrm]

What would happen if some resource already exists with that version? Don't we need a conversion function?

Its not needed because it works for both resourceTemplates and resourcetemplates i have verified

It's working because go default JSON decoder/encoder doesn't care about case or characters like _. So etcd would have two different field names after this pr - older with resourcetemplates and newly created with resourceTemplates.

[savitaashture]

What would happen if some resource already exists with that version? Don't we need a conversion function?

Its not needed because it works for both resourceTemplates and resourcetemplates i have verified

It's working because go default JSON decoder/encoder doesn't care about case or characters like _. So etcd would have two different field names after this pr - older with resourcetemplates and newly created with resourceTemplates.

Yes but I think that should be fine right

[dibyom]

This seems like the right thing to do - as long as this is not a breaking change i.e. the old style works too

[savitaashture]

Hi @dibyom @khrm if PR looks good can you guys review and merge it Thank you

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: khrm

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/tektoncd/triggers/blob/main/OWNERS)~~ [khrm] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment