I agree with the creation of a new independent project to manage the data structure of APISIX. Just like `apache/skywalking-goapi` is used to manage various data types of skywalking.
In fact, we have done similar things before, such as ` https://github.com/api7/types`, which has been archived, but at that time `apisix-ingress-controller` was still in rapid functional iteration, multiple projects were often modified at the same time for a feature always slow down the release progress, so merge this module into the `apisix-ingress-controller` project temporarily. I believe it is necessary to develop the most comprehensive APISIX data structure, which can facilitate the common use of surrounding projects. JinChao Shuai <[email protected]> 于2021年9月23日周四 下午12:26写道： > hi, community, > > The configuration structure currently used by the Apache APISIX Ingress > Controller can only meet the needs of the current Ingress Controller, and > other items in the Apache APISIX ecosystem cannot be reused, such as the > lack of a structure of service objects. [1] If this configuration is used > when exporting the APISIX yaml configuration, the APISIX configuration > structure will be incomplete. > > So I think we can create a new `apisix-go-sdk` public repository to solve > this problem and maintain a complete object structure to meet the needs of > Apache APISIX Ingress Controller and other Apache APISIX projects. > > [1] > > https://github.com/apache/apisix-ingress-controller/blob/3e9bdbf0cee6d49c8e0db27152d46565df704e8c/pkg/types/apisix/v1/types.go > -- > Thanks, > Janko >
