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

Deprecates --max-scale/--min-scale for more consistent naming #958

Merged
merged 2 commits into from Aug 3, 2020
Merged

Deprecates --max-scale/--min-scale for more consistent naming #958

merged 2 commits into from Aug 3, 2020

Conversation

mpetason
Copy link
Contributor

@mpetason mpetason commented Jul 28, 2020

Description

This PR updates --max-scale and --min-scale to --scale-max and --scale-min

Changes

  • Updated --max-scale to --scale-max
  • Updated --min-scale to --scale-min

Reference

#822

@googlebot googlebot added the cla: yes label Jul 28, 2020
@knative-prow-robot knative-prow-robot added the size/M label Jul 28, 2020
@mpetason
Copy link
Contributor Author

@mpetason mpetason commented Jul 28, 2020

This may require additional work. I wasn't sure if I should be changing some of the function names and others to match the renaming.

@mpetason mpetason changed the title Depreciates --max-scale/--min-scale for more consistent naming Deprecates --max-scale/--min-scale for more consistent naming Jul 28, 2020
Copy link
Member

@daisy-ycguo daisy-ycguo left a comment

I'm fine with the changes. Thank you. I don't think we need to change functions or variable names to match the option name change, because the annotation keys defined in the serving side are still using minScale and maxScale.

@knative-metrics-robot
Copy link

@knative-metrics-robot knative-metrics-robot commented Jul 28, 2020

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 85.1% 85.4% 0.3

@mpetason
Copy link
Contributor Author

@mpetason mpetason commented Jul 31, 2020

I think this is ready for another review. Do I need to resolve previous conversations before that happens?

@mpetason mpetason requested a review from sixolet Aug 3, 2020
Copy link
Contributor

@maximilien maximilien left a comment

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm label Aug 3, 2020
@knative-prow-robot
Copy link
Contributor

@knative-prow-robot knative-prow-robot commented Aug 3, 2020

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: daisy-ycguo, maximilien, mpetason

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 label Aug 3, 2020
@knative-prow-robot knative-prow-robot merged commit 4a3cf24 into knative:master Aug 3, 2020
7 of 8 checks passed
rhuss pushed a commit to rhuss/knative-client that referenced this issue Sep 9, 2020
…e#958)

* Depreciates --max-scale/--min-scale for more consistent naming

* Added back old flags and marked hidden
@cardil
Copy link
Contributor

@cardil cardil commented May 11, 2022

This PR contradicts the whole movement of knative/serving#12103 to align the option names, by using names in inverted form to what is currently supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cla: yes lgtm size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants