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

Limit the number of events and deployments displayed in dc describer #9633

Merged
merged 1 commit into from
Jul 1, 2016

Conversation

mfojtik
Copy link
Contributor

@mfojtik mfojtik commented Jun 29, 2016

Fixes: #9604

This PR will limit the events displayed to last 4 and also the deployments displayed in describe to last 3.

@mfojtik
Copy link
Contributor Author

mfojtik commented Jun 29, 2016

@Kargakis PTAL

@0xmichalis 0xmichalis self-assigned this Jun 29, 2016
counter++
}
// Only show last three deployments here
if counter == 2 {
Copy link
Contributor

@0xmichalis 0xmichalis Jun 30, 2016

Choose a reason for hiding this comment

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

Add a comment that this number needs to be on par with the respective number in oc status

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Kargakis I can make it a const

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh, I didn't realize we are on the same package. Yes, please, make it a constant.

const (
// MaxDisplayDeployments is the number of deployments to show when describing
// deployment configuration.
// TODO: Use this constant when limiting the number of deployments displayed in
Copy link
Contributor

Choose a reason for hiding this comment

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

Plug this in oc status while here. Also we don't need to export any of these constants.

@openshift-bot openshift-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 30, 2016
@mfojtik
Copy link
Contributor Author

mfojtik commented Jul 1, 2016

@Kargakis fixed the count and plumbed oc status as well.

const (
// maxDisplayDeployments is the number of deployments to show when describing
// deployment configuration.
// TODO: Use this constant when limiting the number of deployments displayed in
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove the TODO

@0xmichalis
Copy link
Contributor

One last comment, LGTM otherwise

@mfojtik
Copy link
Contributor Author

mfojtik commented Jul 1, 2016

@Kargakis done. will merge on green tests

@openshift-bot openshift-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 1, 2016
@mfojtik
Copy link
Contributor Author

mfojtik commented Jul 1, 2016

[merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented Jul 1, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/5670/) (Image: devenv-rhel7_4502)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 18929ed

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 18929ed

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/5670/)

@openshift-bot openshift-bot merged commit a15fe31 into openshift:master Jul 1, 2016
@mfojtik mfojtik deleted the limit-events branch September 5, 2018 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants