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

GCS resource "dir" field is confusing #1234

Closed
bobcatfish opened this issue Aug 22, 2019 · 7 comments
Closed

GCS resource "dir" field is confusing #1234

bobcatfish opened this issue Aug 22, 2019 · 7 comments
Labels
area/api Indicates an issue or PR that deals with the API. kind/question Issues or PRs that are questions around the project or a particular feature lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@bobcatfish
Copy link
Collaborator

Expected Behavior

As much as possible it should be clear from the names of PipelineResource params what they do and what values they expect.

Actual Behavior

The GCS Resource dir param basically tells the command that grabs the source whether it should grab the source recursively or not, but dir doesn't really convey that.

Also it can have literally any value (except ""), which is confusing.

Additional Info

  • recursive might be a better name
  • Or can we find a way to drop this field entirely?
  • Note also Design PipelineResource extensibility #238 is completely changing the PipelineResource spec, we should probably hold off on this until then, when we could make this a boolean field.
@bobcatfish
Copy link
Collaborator Author

Marking this as blocked by #238

@vdemeester
Copy link
Member

@bobcatfish what is the status ? I guess it still is blocked on the PipelineResource design work 👼

@vdemeester
Copy link
Member

/area api
/kind question

@tekton-robot tekton-robot added area/api Indicates an issue or PR that deals with the API. kind/question Issues or PRs that are questions around the project or a particular feature labels Dec 9, 2019
@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Collaborator

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 13, 2020
@tekton-robot
Copy link
Collaborator

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot tekton-robot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Aug 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Indicates an issue or PR that deals with the API. kind/question Issues or PRs that are questions around the project or a particular feature lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants