Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the intended usage of GetParams in CRDs? #991

Closed
wlynch opened this issue Jun 19, 2019 · 4 comments
Closed

What is the intended usage of GetParams in CRDs? #991

wlynch opened this issue Jun 19, 2019 · 4 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

Comments

@wlynch
Copy link
Member

wlynch commented Jun 19, 2019

Brought up in #895 (comment)

In all Tekton CRDs, there is a func that looks like:

func (s Resource) GetParams() []Param { return []Param{} }

https://github.com/tektoncd/pipeline/search?q=GetParams&type=Code

It looks like it is defined to satisfy the PipelineResourceInterface, but I can't find a place where this used meaningfully. What is the intended purpose of this func? Should we be populating this func with values for Tekton CRDs, or should we remove it?

/cc @bobcatfish @vdemeester

@bobcatfish
Copy link
Collaborator

The work to do here would be to do a bit of digging through the history of the GetParams function and see:

  • If it is actually doing something useful right now that we're not seeing
  • If we can make an informed guess about what the original purpose was and if that makes sense

@bobcatfish bobcatfish added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Jun 19, 2019
@dlorenc
Copy link
Contributor

dlorenc commented Jun 27, 2019

Yeah, looks like this is useless. Removing now.

@vincent-pli
Copy link
Member

Maybe it's useful when we decide to implement Variable substitution of PipelineResource, I guess...

@bobcatfish
Copy link
Collaborator

Since this was removed I'm going to close this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Projects
None yet
Development

No branches or pull requests

4 participants