Apisix-dashboard: how to delete the historical version of the APISIX node.

[Firstsawyou]

System information

• OS: [e.g. macOS, Windows]
• Browser (if applies) [e.g. Chrome, Safari, Edge]
• Version: [e.g. 2.0-rc3]: dashboard 2.4

How to delete the extra historical version in the APISIX node? It prompts mismatch when deleting.

[nic-chen]

Plugin server-info supports the expiration time of the specified information(refer).

We could also support manual deletion of node data, what do you think? @starsz @juzhiyuan

[starsz]

Plugin server-info supports the expiration time of the specified information(refer).

We could also support manual deletion of node data, what do you think? @starsz @juzhiyuan

Agree +1.

[nic-chen]

@bisakhmondal hi, could you help to fix this issue if you have time ? thanks.

[bisakhmondal]

Yeah definitely.

[nic-chen]

@bisakhmondal
Thanks !
I think you could try to submit a proposal for this change : )

[nic-chen]

@bisakhmondal
Please deal with this issue first, it is a task in milestone 2.5, thanks.

[bisakhmondal]

Oh! I see. Then, I am going to look into it.

We could also support manual deletion of node data, what do you think?

So this is the idea, right?

[nic-chen]

Oh! I see. Then, I am going to look into it.

We could also support manual deletion of node data, what do you think?

So this is the idea, right?

sure. that's it.

[LiteSun]

cc @guoqqqi to take a look.

[juzhiyuan]

Hi, after discuss with @nic-chen @starsz @LiteSun, we have a new way to support this feature.

How about only adding one extra message that tells users: APISIX Node List will get updated in 2 hours by default., then we don't have necessary to remove nodes by hand & calling APIs.

[juzhiyuan]

If we support deleting nodes, it will take some other issues:

1. Where should we put the Delete button on this page?
2. Nodes in ETCD have the TTL option, it will expire in 2 hours by default, we don't have the necessary to delete it by hand.
3. If users delete nodes by mistake, they have to wait for APISIX to report its status, though it doesn't take a long time, users like me will get scared if we are not familiar with this logic (Only delete metrics from ETCD).

[nic-chen]

Hi, after discuss with @nic-chen @starsz @LiteSun, we have a new way to support this feature.

How about only adding one extra message that tells users: APISIX Node List will get updated in 2 hours by default., then we don't have necessary to remove nodes by hand & calling APIs.

OK

[bisakhmondal]

Hi, after discuss with @nic-chen @starsz @LiteSun, we have a new way to support this feature.

How about only adding one extra message that tells users: APISIX Node List will get updated in 2 hours by default., then we don't have necessary to remove nodes by hand & calling APIs.

Yeah, that's the default we have right now except for the displaying message part. We can definitely go for it. But looking at the current progress that has been made on this issue, I think it would be a better trade off to integrate the functionality since it'll help the pro peeps to have more customised & fine-grained control through the dashboard instead of waiting for 2 long hours.

Now coming to the implementation of the UI

Where should we put the Delete button on this page?
If users delete nodes by mistake, they have to wait for APISIX to report its status, though it doesn't take a long time, users like me will get scared if we are not familiar with this logic (Only delete metrics from ETCD).

I have prepared a mock-up for the same, which I think should address these concerns :)
The default screen:

On clicking the unlock, the user will be prompted with the necessary warnings.

upon confirming to accept button, he/she will have fine-grained access.

I have made the assets available on google slides. Feel free to tinker with it & share your thoughts.

I think this omits the risk of unexpectedly deleting apisix node data by mistake. Let me know what you think. I'd be happy to address those. Thank you

[nic-chen]

@bisakhmondal
Great!
Thanks for sharing your thoughts.
I think we can discuss further.
But in version 2.5 we could prompt the user first.

[juzhiyuan]

Good design 👏 But I'm still concerned if we have necessary to add this API? let's wait for others :)

[juzhiyuan]

How about dropping this issue from M2.5? coz I'm still not sure if it's necessary to add this feature? 🤔

[juzhiyuan]

Let's wait for more replies