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 support for command and args in service create #635

Merged
merged 2 commits into from
Feb 4, 2020

Conversation

dsimansk
Copy link
Contributor

@dsimansk dsimansk commented Feb 4, 2020

Fixes #604

Proposed Changes

  • Add new flags --cmd and --arg
  • --cmd accepts a single string input
  • --arg can be used multiple times to provide as many as neeed
  • Examples:
    • --cmd /app/start
    • --cmd /app/start --arg myArg
    • --arg myArg1 --arg --myArg2 --arg myArg3=3.

Even though podSpec.Command accepts stringArray and arguments can be passed directly to this field. Per discussion on #604 I've decided to follow more verbose and strict approach to make a clear distinction to improve usability and user-exp.

/assign @rhuss
/assign @navidshaikh

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Feb 4, 2020
Copy link
Contributor

@knative-prow-robot knative-prow-robot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dsimansk: 0 warnings.

In response to this:

Fixes #604

Proposed Changes

  • Add new flags --cmd and --arg
  • --cmd accepts a single string input
  • --arg can be used multiple times to provide as many as neeed
  • Examples:
  • --cmd /app/start
  • --cmd /app/start --arg myArg
  • --arg myArg1 --arg --myArg2 --arg myArg3=3.

Even though podSpec.Command accepts stringArray and arguments can be passed directly to this field. Per discussion on #604 I've decided to follow more verbose and strict approach to make a clear distinction to improve usability and user-exp.

/assign @rhuss
/assign @navidshaikh

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.

@knative-prow-robot
Copy link
Contributor

Welcome @dsimansk! It looks like this is your first PR to knative/client 🎉

@knative-prow-robot
Copy link
Contributor

Hi @dsimansk. Thanks for your PR.

I'm waiting for a knative 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.

@knative-prow-robot knative-prow-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 4, 2020
@navidshaikh
Copy link
Collaborator

/ok-to-test

@knative-prow-robot knative-prow-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 Feb 4, 2020
@knative-metrics-robot
Copy link

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

File Old Coverage New Coverage Delta
pkg/kn/commands/service/configuration_edit_flags.go 82.3% 82.4% 0.1
pkg/serving/config_changes.go 79.8% 79.8% 0.0

Copy link
Contributor

@rhuss rhuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks ! Looks good to me.

Maybe you could add some E2E tests in an additional PR ? (like the other e2e tests that you find in the test/ directory.

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 4, 2020
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dsimansk, rhuss

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

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 4, 2020
@knative-prow-robot knative-prow-robot merged commit ffdeafe into knative:master Feb 4, 2020
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. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for cmd and args when creating a new service
6 participants