-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature: add managed fields in jsonschema for resources, such as create_time and update_time #2433
Comments
@nic-chen can you provide some examples? |
example, add create_time and update_time for
|
@nic-chen do we need to add |
yes, i think so. if not, data will be filter by : |
agree to add the new field ^_^ |
+1, or add a field version.
[email protected]
From: YuanSheng Wang
Date: 2020-10-16 19:00
To: apache/apisix
CC: Subscribed
Subject: Re: [apache/apisix] feature: add managed fields in jsonschema for resources, such as create_time and update_time (#2433)
agree to add the new field ^_^
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
fixed alread |
Issue description
We are refactoring the dashboard
manager api
, to remove the dependency on MySQL. Previously, some managed fields were saved in mysql. After refactoring, we moved these fields to ETCD. I think APISIX's json schema should also support this part of the fields to avoid data being filtered out.Here is the detail:
create_time and update_time for
route
,upstream
,service
,consumer
,ssl
validity_start and validity_end for
ssl
this four fields are all int type for Unix timestamp.
The text was updated successfully, but these errors were encountered: