Merge ~caleb-ellis/maas:deploy-in-table into maas:master
Proposed by
Caleb Ellis
Status: | Merged |
---|---|
Approved by: | Caleb Ellis |
Approved revision: | 2d2239f136ea777b86dcbb1c7fc31f4a27c97be7 |
Merge reported by: | MAAS Lander |
Merged at revision: | not available |
Proposed branch: | ~caleb-ellis/maas:deploy-in-table |
Merge into: | maas:master |
Diff against target: |
241 lines (+81/-23) 4 files modified
src/maasserver/static/js/angular/directives/machines_table.js (+25/-3) src/maasserver/static/js/angular/directives/tests/test_machines_table.js (+45/-9) src/maasserver/static/partials/machines-table.html (+10/-10) src/maasserver/static/partials/pod-details.html (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Lee Trager (community) | Approve | ||
Andres Rodriguez (community) | Needs Information | ||
Anthony Dillon | Approve | ||
Blake Rouse | Pending | ||
Review via email: mp+365793@code.launchpad.net |
Commit message
LP: #1825143 - Display default OS/release deployment in in-table action menu
Description of the change
## Done
- Display default OS/release deployment in in-table action menu
- Removed in-table actions from pod details page (was causing errors if refreshing the browser at this page, because not all the machine data is passed through in this view alone)
## QA
- Check that deploying a machine has the correct default OS and release selected
## Screenshot
https:/
To post a comment you must log in.
This is not a review, but just a quick question, shouldn't the backend be doing a failsafe in which if the UI doesn't send this info, its already set? Or is the issue because the UI is setting blank fields and sending blank fields causes this?