Is st2web actively developed / maintained? I have a number of things I'd like to see in st2web, either new features or re-work of some things:
1, NodeJS 14 is considered stable on the github page, but Node 14 is EOL for a number of years now. the package was updated to node20 5 months ago, so probably the readme is wrong
1, working in st2flow doesn't refresh logout timer, so regardless of work being done in there, the user is rather unceremoniously kicked after 2 hours (timer resets are implemented in st2menu, which is not loaded in st2flow afaik). This would require either the same resets to be implemented in st2flow or add menu to it (can be hidden perhaps?)
2, I'd like to see execution filtering in st2history not based on /executions/views/filters, but rather on any field that the /executions API allows as filtering criteria. In a corporate environment (or on a very utilized ST2 instance) there can be A LOT of executions / day, so the ability to filter down to a specific execution id / timeframe would be a very welcome feature. This would require partial rework on how the st2history works, as I think (correct me if I'm wrong) currently it fetches 50 executions where parent = null and then applies filter on the resulting dataset, so the filtering criteria, when applied, should apply when calling the API. this is in fact wrong. during initial load filters are not applied, but after selecting filters an API call is made with the filters applied. so I'd still need to rework this in the UI to be able to filter by values I need
3, I'd like to have an option to adjust style settings for st2flow and store them somehow, either as a static preset (similar to theme drop down selection) or user-defined style overrides stored in datastore per user. The items in the menu are way too large, operations with longer names don't fit and the ratio of menu:canvas is not adjustable (only via developer tools > inspect). As all st2flow does to talk to ST2 is just API calls, it should be technically possible to store style overrides in a user-scoped datastore key and load the values when user clicks the "+" and st2flow opens in a new page. An alternative is to use browser localStorage.
4, there's a number of stale open feature requests / bug reports (#860, #1005, ...) that go back years and some are of interest to me.
Hello Community,
Is st2web actively developed / maintained? I have a number of things I'd like to see in st2web, either new features or re-work of some things:
1,
NodeJS 14 is considered stable on the github page, but Node 14 is EOL for a number of years now.the package was updated to node20 5 months ago, so probably the readme is wrong1, working in st2flow doesn't refresh logout timer, so regardless of work being done in there, the user is rather unceremoniously kicked after 2 hours (timer resets are implemented in st2menu, which is not loaded in st2flow afaik). This would require either the same resets to be implemented in st2flow or add menu to it (can be hidden perhaps?)
2, I'd like to see execution filtering in st2history not based on /executions/views/filters, but rather on any field that the /executions API allows as filtering criteria. In a corporate environment (or on a very utilized ST2 instance) there can be A LOT of executions / day, so the ability to filter down to a specific execution id / timeframe would be a very welcome feature. This would require partial rework on how the st2history works, as I think (correct me if I'm wrong)
currently it fetches 50 executions where parent = null and then applies filter on the resulting dataset, so the filtering criteria, when applied, should apply when calling the API.this is in fact wrong. during initial load filters are not applied, but after selecting filters an API call is made with the filters applied. so I'd still need to rework this in the UI to be able to filter by values I need3, I'd like to have an option to adjust style settings for st2flow and store them somehow, either as a static preset (similar to theme drop down selection) or user-defined style overrides stored in datastore per user. The items in the menu are way too large, operations with longer names don't fit and the ratio of menu:canvas is not adjustable (only via developer tools > inspect). As all st2flow does to talk to ST2 is just API calls, it should be technically possible to store style overrides in a user-scoped datastore key and load the values when user clicks the "+" and st2flow opens in a new page. An alternative is to use browser localStorage.
4, there's a number of stale open feature requests / bug reports (#860, #1005, ...) that go back years and some are of interest to me.
Thoughts / feedback?
BR,
Filip