-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
Marking this as blocked by #238 |
@bobcatfish what is the status ? I guess it still is blocked on the PipelineResource design work 👼 |
/area api |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
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. |
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, butdir
doesn't really convey that.Also it can have literally any value (except ""), which is confusing.
Additional Info
recursive
might be a better nameThe text was updated successfully, but these errors were encountered: