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

Add --use-workspace-defaults #1441

Closed

Conversation

AeroNotix
Copy link

@AeroNotix AeroNotix commented Aug 29, 2021

  • tkn task start always asks for the configuration of the workspaces,
    even if you have:
  default-task-run-workspace-binding: |
    emptyDir: {}

In the config-defaults.

If there is another way to achieve this, please let me know.

Add a new flag `--use-workspace-default` to use the configured default workspace for the task run

@tekton-robot tekton-robot requested a review from chmouel August 29, 2021 23:35
@tekton-robot tekton-robot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Aug 29, 2021
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Aug 29, 2021

CLA Signed

The committers are authorized under a signed CLA.

@tekton-robot tekton-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 29, 2021
@tekton-robot
Copy link
Contributor

Hi @AeroNotix. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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 size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 29, 2021
@AeroNotix
Copy link
Author

/assign @danielhelfand

@chmouel
Copy link
Member

chmouel commented Aug 30, 2021

if you set UseParamDefaults as false, it should use the workspace defaults? If this doesn't happen like this it would be a bug isnt it ?

(also if we go forward on this please consider adding a test)

/ok-to-test

@tekton-robot tekton-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 30, 2021
@tekton-robot
Copy link
Contributor

The following is the coverage report on the affected files.
Say /test pull-tekton-cli-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/cmd/task/start.go 80.9% 81.0% 0.1

@AeroNotix
Copy link
Author

@chmouel no, using just --use-param-defaults=false without what I added, still prompts for the workspace configuration.

@AeroNotix
Copy link
Author

/retest

@AeroNotix
Copy link
Author

@danielhelfand can I get some help moving this along, please? What do I need to do/answer/change/discover/debug etc.

@AeroNotix
Copy link
Author

The CI failure looks to be a documentantion related thing.. what do I need to fix?

@vinamra28
Copy link
Member

vinamra28 commented Jan 28, 2022

CLA Signed

The committers are authorized under a signed CLA.

@tekton-robot tekton-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 28, 2022
@tekton-robot
Copy link
Contributor

The following is the coverage report on the affected files.
Say /test pull-tekton-cli-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/cmd/task/start.go 81.0% 81.1% 0.1

@piyush-garg
Copy link
Contributor

@pradeepitm12 @vinamra28 @chmouel I think this we can close as #1465 is merged

@vinamra28
Copy link
Member

vinamra28 commented Feb 8, 2022

@pradeepitm12 @vinamra28 @chmouel I think this we can close as #1465 is merged

@piyush-garg I think we can still consider this as this is solving a different problem. There is a field in configmap as config-defaults where we can set the value of key default-task-run-workspace-binding. If I am not wrong then this PR is to handle this scenario 😅
#1465 is just to handle the binding of optional workspaces. This PR is to handle all the workspaces. It's similar to --use-params-default flag

@piyush-garg
Copy link
Contributor

@pradeepitm12 @vinamra28 @chmouel I think this we can close as #1465 is merged

@piyush-garg I think we can still consider this as this is solving a different problem. There is a field in configmap as config-defaults where we can set the value of key default-task-run-workspace-binding. If I am not wrong then this PR is to handle this scenario sweat_smile

Aah ok, this is for skipping all and #1465 is for skipping optional

@piyush-garg
Copy link
Contributor

/retest

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 20, 2022
@tekton-robot tekton-robot removed the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 20, 2022
@AeroNotix
Copy link
Author

Added the same flags for cluster/pipeline.

@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Apr 20, 2022
@tekton-robot
Copy link
Contributor

The following is the coverage report on the affected files.
Say /test pull-tekton-cli-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/cmd/clustertask/start.go 80.2% 80.3% 0.1
pkg/cmd/pipeline/start.go 66.3% 66.4% 0.1
pkg/cmd/task/start.go 81.0% 81.1% 0.1

@vinamra28
Copy link
Member

/retest

@AeroNotix
Copy link
Author

@vinamra28 good to merge now?

@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Apr 25, 2022
@vdemeester
Copy link
Member

Added a release-note block, it should be good to merge now
/cc @tektoncd/cli-maintainers

@tekton-robot tekton-robot requested a review from a team April 25, 2022 07:53
@piyush-garg
Copy link
Contributor

Can we please add some tests for this?

@AeroNotix
Copy link
Author

Can you point me to an existing test which tests similar functionality?

@tekton-robot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
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 with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 26, 2022
@tekton-robot
Copy link
Contributor

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

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 25, 2022
@tekton-robot
Copy link
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

@tekton-robot
Copy link
Contributor

@tekton-robot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/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
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@piyush-garg
Copy link
Contributor

/remove-lifecycle rotten

@tekton-robot tekton-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 28, 2022
@piyush-garg
Copy link
Contributor

Can you point me to an existing test which tests similar functionality?

you can take look at the tests fo --use-param-defaults to get an idea

@tekton-robot
Copy link
Contributor

@AeroNotix: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-tekton-cli-integration-tests 62043f3 link true /test pull-tekton-cli-integration-tests

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@AeroNotix
Copy link
Author

I literally don't care.

@AeroNotix AeroNotix closed this Sep 28, 2022
@AeroNotix AeroNotix deleted the fix/use-workspace-defaults branch September 28, 2022 14:14
@AeroNotix
Copy link
Author

Over a year to get something so trivial in, I love the project but this is just unreal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants