You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apisix.apache.org by jinwei <gx...@163.com> on 2020/05/28 07:57:36 UTC
[DISCUSS] Support configuration management with yaml for APISIX
Many users have proposed to configure APISIX through yaml
The yaml method is easier to understand and convenient for Ops
We can achieve CI through making yaml persistent, with version control through git
You can also divide the configuration of APISIX into multiple yaml files and collaborate to manage APISIX
I think it is necessary to launch a new project to support the yaml declaration configuration, and keeping the status of APISIX in sync with the declaration
It is similar to decK in kong
What do you think?
Re:Re: [DISCUSS] Support configuration management with yaml for
APISIX
Posted by jinwei <gx...@163.com>.
Yes, you are right
At 2020-05-28 16:03:07, "YuanSheng Wang" <me...@apache.org> wrote:
>On Thu, May 28, 2020 at 3:57 PM jinwei <gx...@163.com> wrote:
>
>> Many users have proposed to configure APISIX through yaml
>>
>
>ops -> yaml -> admin API -> etcd -> apisix gateway
>
>Is the configured delivery path like this?
>
>
>>
>>
>>
>>
>>
>>
>>
>> The yaml method is easier to understand and convenient for Ops
>>
>>
>>
>>
>> We can achieve CI through making yaml persistent, with version control
>> through git
>>
>>
>>
>>
>> You can also divide the configuration of APISIX into multiple yaml files
>> and collaborate to manage APISIX
>>
>>
>>
>>
>> I think it is necessary to launch a new project to support the yaml
>> declaration configuration, and keeping the status of APISIX in sync with
>> the declaration
>>
>>
>>
>>
>> It is similar to decK in kong
>>
>>
>>
>>
>> What do you think?
>--
>*MembPhis*
>My github: https://github.com/membphis
>Apache APISIX: https://github.com/apache/incubator-apisix
Re: [DISCUSS] Support configuration management with yaml for APISIX
Posted by YuanSheng Wang <me...@apache.org>.
On Thu, May 28, 2020 at 3:57 PM jinwei <gx...@163.com> wrote:
> Many users have proposed to configure APISIX through yaml
>
ops -> yaml -> admin API -> etcd -> apisix gateway
Is the configured delivery path like this?
>
>
>
>
>
>
>
> The yaml method is easier to understand and convenient for Ops
>
>
>
>
> We can achieve CI through making yaml persistent, with version control
> through git
>
>
>
>
> You can also divide the configuration of APISIX into multiple yaml files
> and collaborate to manage APISIX
>
>
>
>
> I think it is necessary to launch a new project to support the yaml
> declaration configuration, and keeping the status of APISIX in sync with
> the declaration
>
>
>
>
> It is similar to decK in kong
>
>
>
>
> What do you think?
--
*MembPhis*
My github: https://github.com/membphis
Apache APISIX: https://github.com/apache/incubator-apisix