BUG: generated nav configuration should not default to configuration view #1041
Assignees
Labels
bug
Something isn't working
Comments
|
@pmeyerson I think we definitely can provide such an option in the globalConfig file. Changing the default - I think it will be too big of a change. |
4 tasks
artemrys
added a commit
that referenced
this issue
Jun 3, 2024
**Issue number:** #1041 ## Summary ### Changes > Please provide a summary of what's being changed Configuration page require admin privileges and if a Splunk user is not an admin - configuration page will show an error which is confusing. This PR allows to set a default page to `search` so there will be no error shown when a Splunk user opens add-on for the first time. This PR enables TA developers to choose the default view, one of four: `inputs`, `configuration`, `dashboard` and `search`. ### User experience > Please describe what the user experience looks like before and after this change Nothing changes for the existing customers. For customers who decide to use `search` view as a default one - they need to update their globalConfig file, specifically set `meta.defaultView` to `search` and rebuild an add-on. ## Checklist If your change doesn't seem to apply, please leave them unchecked. * [x] I have performed a self-review of this change * [x] Changes have been tested * [ ] Changes are documented * [x] PR title follows [conventional commit semantics](https://www.conventionalcommits.org/en/v1.0.0/)
|
This will be released in the upcoming release of UCC (next week). |
soleksy-splunk
pushed a commit
that referenced
this issue
Jun 7, 2024
**Issue number:** #1041 ## Summary ### Changes > Please provide a summary of what's being changed Configuration page require admin privileges and if a Splunk user is not an admin - configuration page will show an error which is confusing. This PR allows to set a default page to `search` so there will be no error shown when a Splunk user opens add-on for the first time. This PR enables TA developers to choose the default view, one of four: `inputs`, `configuration`, `dashboard` and `search`. ### User experience > Please describe what the user experience looks like before and after this change Nothing changes for the existing customers. For customers who decide to use `search` view as a default one - they need to update their globalConfig file, specifically set `meta.defaultView` to `search` and rebuild an add-on. ## Checklist If your change doesn't seem to apply, please leave them unchecked. * [x] I have performed a self-review of this change * [x] Changes have been tested * [ ] Changes are documented * [x] PR title follows [conventional commit semantics](https://www.conventionalcommits.org/en/v1.0.0/)
srv-rr-github-token
added a commit
that referenced
this issue
Jun 13, 2024
# [5.46.0](v5.45.0...v5.46.0) (2024-06-13) ### Bug Fixes * **oauth:** set loglevel in oauth rh template to use log level set in add-on ([#1227](#1227)) ([3b7b9e1](3b7b9e1)) ### Features * allow developers to choose the default view ([#1197](#1197)) ([21610e2](21610e2)), closes [#1041](#1041) * **configuration:** display UCC version ([#1221](#1221)) ([a63d8b3](a63d8b3)) * **dashboard:** add error categories to chart and event table in the error panel ([#1225](#1225)) ([cd2907a](cd2907a)) * **dashboard:** add resource monitoring tab and information about input status ([#1209](#1209)) ([e8acfd9](e8acfd9)) * globalConfig file passed through `--config` accepts only JSON or YAML formats ([#1216](#1216)) ([f661475](f661475)) * sort table by visible text ([#1205](#1205)) ([8561e0f](8561e0f))
|
Released as part of v5.46.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
It seems that the default view in ucc-generated nav/default.xml is set to the configuration page, which is an issue if this page requires admin privileges.
Better to default to the search view.
generated /default/data/ui/nav/default.xml:
NOTE: I have latest pip 5.37.0 installed fresh, but the output log shows 5.28.4 for some reason.
What ucc-gen version are you using?
5.37.0
Additional System Info
No response
The text was updated successfully, but these errors were encountered: