Open gergoabraham opened 1 year ago
Pinging @elastic/fleet (Team:Fleet)
Hi @jen-huang - can you please assign this to me ? this will be my first contribution into Kibana
:)
Thank you!
Hii, I would like to start my open source contribution by solving this issue. Can anyone assign me to it?
@pra2107tham Assigned you. Thanks and let us know if you have any questions.
@jen-huang from what I can understand from this issue, i can think of 2 ways to solve (correct me if I'm wrong) : The extra cloud policy token which is getting added into the number of tokens if making that new empty page right? I have to just make sure the total number of tokens doesnt include that extra one token? I dont know what and how to do this. If you can guide me personally it would be great help
The extra cloud policy token which is getting added into the number of tokens if making that new empty page right? I have to just make sure the total number of tokens doesnt include that extra one token?
Yes, I think this is accurate. You can see the total calculation and the filtering on agent policies on these lines:
Probably total
should be replaced to use the length of rowItems
.
I accidentally made 6 tokens and they r not going back, i uninstalled them but it still stays in the list? how can i reset the tokens in my local server
The previous work will be reverted in https://github.com/elastic/kibana/pull/194343 so I'm reopening this. That approach broke pagination in general so this will need to be fixed in a different way.
Ohh, if it broke pagination? so should I try with new method or it has been closed?
Kibana version: v8.11 (main) cloud deployment
Describe the bug: managed policies are hidden from the Enrollment token table, but this filtering is done on frontend side, this makes the received
total
value invalid. Because of this, if there ispageSize * n
number of other enrollment tokens, thetotal
will bepageSize * n + 1
including the Cloud agent policy token, therefore the table will show an additional, empty page.Steps to reproduce:
Expected behavior: there is only one page, not two
Screenshots (if relevant):