| commit | f4d9bc487fa0386d0fb9dcf9131a5961d0f84b59 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Tue Mar 06 15:42:40 2018 -0600 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Tue Mar 27 18:06:33 2018 +0000 |
| tree | 6a40a4526a1092d8128c826001f1f52c40d20790 | |
| parent | 7a5ce461fb91a2e10eb2ef15a2a9f6a9407e1564 [diff] |
Confirm changing priority on all priority changes Before the confirm priority change modal would only appear if the user is changing the priority from priority "1" to "0" or priority "0" to "1". This doesn't work because if two images existed, a "functional" priority "1" image and an "active" priority "2" image the confirm would not appear on a priority change and it should. I believe this logic came from the belief that the "functional" image is always priority "0" and therefore only display this confirm when the "functional" image is affected by the change. The functional image is not always priority "0" and with only 2 "active" images supported (only "active" images have a priority) (the "functional" image is an "active" image) all priority changes affect the functional image so adding this confirm for all priority changes. Tested: See this confirm on every priority change. Change-Id: Icd113686f15a2e82ead72d04677335ee635cf668 Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
TODO: Write a project description
nodejs npm
npm install
npm run-script server
This will run it locally in http://localhost:8080.
https://<bmc-ip> and bypass the secure warning. You will see a JSON response with Login required message.http://localhost:8080. Enter the BMC IP, Username and Password (defaults: root/0penBmc).Now you are logged in.