splunk/addonfactory-ucc-base-ui

The base UI for Splunk UCC based Add-on user interfaces

addonfactory-ucc-base-ui's Issues

pages > configuration > tabs > table > actions list ignored

The default list is
"actions": [
"edit",
"delete",
"clone"
]
I wanted to have only "delete" , but once I removed other, UI showed them as well. They worked also.
I did one more test - get rid of all options, but were still getting all of them in UI

globalConfig.json schema accepts invalid configuration

This issue is a follow-up issue from splunk/addonfactory-ucc-generator#210.

When creating an add-on using ucc-gen (version 5.0.0) command, it uses schema from this repository to validate globalConfig.json.

If I use globalConfig.json without "inputs" section - it should not be valid.

Example config: https://github.com/splunk/addonfactory-ucc-generator/files/6583733/globalConfig_1.txt

Create "Search internal logs" button

Create "Search internal logs" button.
The button will be available for each input.
Once used (clicked), new window will be opened with search application and applied search query
index = _* source = [input name]

`schema.json` and `schemaGenerator.py` are not synced

For example, schema.json has oauth_state_enabled field, but schemaGenerator.py does not.

Another example is that schemaGenerator.py still has

    onLoad = StringField(max_length=3000)
    onChange = StringField(max_length=3000)

which does not exist in schema.json.

Add column that reflects input type if more than one can be defined in inputs page

Input type is missing once defined

Bug - UI - notification stops working if the Add-on does not have an account section

If the Add-on does not have an account section in globalConfig.json, the update notification box that appears when you perform a save stop working.

In such a case, the operation remains successful, but there is no more notifications.

Talking about this:

The notification will however immediately re-appear and work as expected if there an account section.

There are cases where an Addon will not rely on requiring an account, which means this should remain an optional thing.

This clearly is a UI bug, tested in latest in 5.5.8 and 5.5.6.