-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Implements frontend for deployment rollback #6003
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shu-mutou 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 |
Codecov Report
@@ Coverage Diff @@
## master #6003 +/- ##
==========================================
+ Coverage 41.89% 41.95% +0.06%
==========================================
Files 44 44
Lines 1234 1237 +3
Branches 163 163
==========================================
+ Hits 517 519 +2
- Misses 717 718 +1 |
/hold |
/hold cancel |
} | ||
|
||
// History is a presentation layer view of Kubernetes Replica Set resource for history. | ||
type History struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This kind of breaks our pattern of resource being a Kubernetes resource. It is then used in the frontend as a resource also. I'd have to rethink how to incorporate that into our patterns.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, these are defined in frontend also.
To create dialog contents and submission endpoint URL, the action on history row needed to pass deployment name and namespace to dialog. So I defined new type History that have ReplicaSet and parent resource information. Could you let me know if you have better idea about this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll think about how we could add this without breaking our patterns. Resource should be mappable to a real Kubernetes resource. History/HistoryList is a very abstract thing.
I was on vacation last week. I'll try to take a look at it this week. |
Hello, why You don't using Redux, it's very important in a project like kubernetes UI. |
It's not important. It's a matter of personal preference. Also, PR is not a good place to discuss such things. |
History list is added into deployment detail view, and `Rollback` action is added in each row except for current revision.
@maciaszczykm @floreks PTAL again. Thanks!! |
@shu-mutou: PR needs rebase. 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. |
Since #7047 has been merged and it introduces major architecture changes we should close this PR. If you are willing to work on it, you can open a new PR against the current master. /close |
@floreks: Closed this PR. 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. |
History list is added into deployment detail view, and
Rollback
action is added in each row except for current revision.Fixes: #2889