bluerobotics
Allow for dynamic Cockpit Actions and add support for customizable HTTP request actions
https://github.com/user-attachments/assets/7e64a286-4a72-4755-93a6-6e43636e273d
Fix #568
- [x] File import/export would be very useful
- [x] Include a "test now" button in the Actions editor
- [x] File import/export would be very useful
- [x] Include a "test now" button in the Actions editor
Added both:
Can be tested with the following files:
http-request-action (Arm with HTTP).json http-request-action (Disarm with HTTP).json
We indeed were using 'Title Case' on the titles for the windows, modals and expansible panels, but after some feedback we decided to keep everything on regular capitalization:
Check the Alerts config page:
Missing some tooltips for the action buttons and some margin on the table header:
Margins:
I was able to load some random .json files into the Actions module and they broke cockpit (obviously.. haha) What are your thoughts on adding a header to the files exported from the "Cockpit actions configuration" table? Would it be necessary or just overkill for the current needs?
I was able to load some random .json files into the Actions module and they broke cockpit (obviously.. haha) What are your thoughts on adding a header to the files exported from the "Cockpit actions configuration" table? Would it be necessary or just overkill for the current needs?
I think we can add a simple validator to check at least if the json structure is the same.
Export icons can be centered inside its container using:
<v-btn
variant="outlined"
class="rounded-full mx-1 pl-[3px] pt-[1px]"
icon="mdi-export"
size="x-small"
@click="exportAction(item.id)"
/>
@ArturoManzoli all UI changes were performed. I've also added file validation for the "Import action" button and changed the data-lake structures to "CockpitActionVariable" (former "CockpitActionParameter").