Skip to content

Hide Users page in kubedb-ui-presets; Use billing ui 2.4.10 - #1315

Merged
ArnobKumarSaha merged 2 commits into
masterfrom
arnob-ui-users
Aug 6, 2026
Merged

Hide Users page in kubedb-ui-presets; Use billing ui 2.4.10#1315
ArnobKumarSaha merged 2 commits into
masterfrom
arnob-ui-users

Conversation

@ArnobKumarSaha

Copy link
Copy Markdown
Member

Set page-level show: false on the Users page in the 15 ResourceOutlineFilters that define one (druid, elasticsearch, hazelcast, kafka, mariadb, mongodb, mysql, oracle, perconaxtradb, pgbouncer, postgres, rabbitmq, redis, singlestore, solr), matching how Security and Manifests are already disabled. Section-level show and blocks are untouched. The other 15 databases never had a Users page, so they were already hidden by the default-hidden rule.

Also removes the Monitoring page from memcached.yaml — it was the only filter of 30 defining one, so the Monitoring tab rendered for Memcached and nowhere else. Monitoring stays reachable via the Insights/Dashboards blocks and the Monitoring action.

Page totals after this change:

Page show=true show=false
Overview 30 0
Operations 29 0
Insights 25 0
Backup 17 0
Users 0 15
Security 0 30
Manifests 0 30
Backup (Legacy) 0 9

No individual block is set to false in any filter; visibility is decided entirely at page level.

…presets

Set page-level show: false on the Users page in the 15 filters that define
one, matching how Security and Manifests are disabled. Remove the Monitoring
page from memcached.yaml, the only filter of 30 that defined it.

Signed-off-by: Arnob kumar saha <arnob@appscode.com>
Signed-off-by: Arnob kumar saha <arnob@appscode.com>
@ArnobKumarSaha ArnobKumarSaha changed the title Hide Users page and drop memcached-only Monitoring page in kubedb-ui-presets Hide Users page in kubedb-ui-presets; Use billing ui 2.4.10 Aug 6, 2026
@ArnobKumarSaha
ArnobKumarSaha merged commit 77c4462 into master Aug 6, 2026
4 checks passed
@ArnobKumarSaha
ArnobKumarSaha deleted the arnob-ui-users branch August 6, 2026 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant