@Sn0rt Hi, I replied to your email yesterday, but I am not sure if you received it, so, I am pasting the email content now.

I basically agree with you idea. Now APISIX not use "validity_start" and "validity_start" fields no matter we set or read "ssl" resource. But APISIX Dashboard will set these fields when we add SSL resources, and it will display these fields on the web page, a user has raised an issue regarding this before. #10063
Maybe we should be compatible with this logic in APISIX Dashboard first, and remove these fields in APISIX.
What do you think?

@jiangfucheng

I have not recive your reponse email yet. you can click the email list for confirm.

apache/apisix is the core project. to remove this field from apisix, we can merge it into it first.

1. APISIX-dashboard is a side project of APISIX and needs to be compatible with apisix instead of APISIX compatible with APISIX-dashboard. (I will create an issue under apisix-dashboard to track this requirement after this PR has been merged.)

2. The apisix-dashbaord compatibility guarantee is only up to 3.0.x. Currently, apisix has been released to 3.6.x.

@jiangfucheng

I have not recive your reponse email yet. you can click the email list for confirm.

apache/apisix is the core project. to remove this field from apisix, we can merge it into it first.

1. APISIX-dashboard is a side project of APISIX and needs to be compatible with apisix instead of APISIX compatible with APISIX-dashboard. (I will create an issue under apisix-dashboard to track this requirement after this PR has been merged.)
2. The apisix-dashbaord compatibility guarantee is only up to 3.0.x. Currently, apisix has been released to 3.6.x.

Got it, I think it's reasonable.