+1 (binding)
I have checked:
1. All download links are OK;
2. Signature and checksum are valid;
3. LICENSE and NOTICE files exist and are correct;
4. Build on Debian 11.5 was successful.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
+1 (binding)
I have checked:
1. All download links are OK;
2. Signature and checksum are valid;
3. LICENSE and NOTICE files exist and are correct;
4. Build on Debian 11.5 was successful.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
+1 (binding)
I have checked:
1. All download links are OK;
2. Signature and checksum are valid;
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
在 2022年9月27日 14:47:23 上，Jintao Zhang 写道：
> Hello, Community,
> This is a call f
+1 (binding)
I have checked:
1. All download links are OK;
2. Signature and checksum are valid;
3. LICENSE and NOTICE files exist and are correct;
4. It can be built successfully on my Centos 7.9.2009.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com
...@apache.org or
tzssanggl...@apache.org.
Kindly let me know if you need Google Meet or Zoom as communication tools.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
+1 (binding)
I have checked:
1. All download links are OK;
2. Signature and checksum are valid;
3. LICENSE and NOTICE files exist and are correct;
4. It can be built successfully on my Centos 7.9.2009.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com
> Question: what about the new Admin API backward compatibility?
The new API design does not keep backward compatibility, so changes will be
made to both the APISIX Dashboard and APISIX Ingress Controller.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: ht
There are no plans for this now, but I thought we could try it once after
APISIX Submit and before APISIX 3.0.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
在 2022年5月10日 12:10:27 上，Zhiyuan Ju 写道：
> Hi, Zhengsong,
>
> Do
topic.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
在 2022年4月19日 09:16:02 上，zhixiongdu027 写道：
> Hi all:
>
> compared to kafka, mongo,
> elasticsearch is a bit more used for storing logs.
> I think apisix ne
just because I didn't
think of MySQL as a log storage service in the usage scenario.
My concern is that storing log content in json format or request/response
body in a mysql property, for example (I've seen people use MySQL this
way), is not an easy way to retrieve and analyze logs.
*Z
/pzl534tgr5jg32wh5vkrvjh8261g44od
I will continue the release process.
Thank you all for making this happen!
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Congratulations!
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
在 2022年4月14日 10:53:49 上，Zeping Bai 写道：
> Hi Community,
>
> Our contributor Qi Guo [1] helps our community do a lot of things. He has
> been an active co
APISIX is supported and the details have been replied to in the issue.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
在 2022年4月2日 14:08:53 上，吴治国 写道：
> Hi community
> I met a problem when setting a timer in plugin, and I ma
It is difficult to list all safe functions in the whitelist.
It's not even possible to tell which functions are safe and which ones are
not.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
在 2022年3月31日 11:18:35 上，Kwanhur Huan
+1 non-binding
I have checked:
1. All links are OK
2. Signature and checksum are correct
3. NOTICE and LICENSE files exist
4. Building in macOS 12.3 successfully
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
在 2022年3月23日 09:26:04 上
nice idea, I will join the APISIX feature development.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Jintao Zhang 于2022年3月12日周六 00:38写道：
>
> I found that my `Architecture design` above was formatted correctly in the
> mailbox
ok, I have created an issue to tracing this:
https://github.com/apache/apisix/issues/6405
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Alexandre SOLOVIEFF 于2022年2月21日周一 21:22写道：
>
> I mean that when I configure the plugin proxy-r
and what do you mean by not working?
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Alexandre SOLOVIEFF 于2022年2月21日周一 18:03写道：
>
> And when I use the same config :
>
> \"proxy-rewrite\": {
> \"head
hi, can you show details about this configuration not working? This
configuration should work. This way we can check it more quickly.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Alexandre SOLOVIEFF 于2022年2月15日周二 16:39写道：
>
&
thanks Bobur
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Bobur Umurzokov 于2022年2月17日周四 17:57写道：
>
> Hi,
>
> Just follow up on previous emails,I created a public document where we can
> collect all project proposals f
Cool. If you change checklist to table type, add descriptions, links,
etc. to different targets, it looks more standardized, checklist looks
a bit random.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Bozhong Yu 于2022年2月21日周一 09:25写道
Congratulations!
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zhiyuan Ju 于2022年2月15日周二 10:27写道：
>
> Hi,
>
> Except for congratulations to Yilin, I would encourage everyone to read and
> know more about what Y
Default pass.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
mijo michael 于2022年2月9日周三 22:44写道：
>
> How to pass parameters (url or query parameters) in the API call to the
> route and upstream?
Congratulations !
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
YuanSheng Wang 于2022年1月19日周三 16:20写道：
>
> Congratulations ^_^
>
>
> On Wed, Jan 19, 2022 at 4:04 PM Bozhong Yu wrote:
>
> > Congratulations !
>
+1 (no binding)
I checked：
1. Download links are OK.
2. Checksum and signature are OK.
3. LICENSE and NOTICE files are exist.
4. Building on CentOS 7.9 was successful.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Bisakh Mondal 于2022年
will do it soon
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Tsangleslie 于2022年1月2日周日 23:24写道：
>
> Cool, Looking forward to this proposal.
> Shall we open a discussion in GitHub for more opinions ?
>
> Leslie Ts
Good idea, it's important.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
JunXu Chen 于2021年12月31日周五 21:07写道：
>
> Thanks for your awesome proposal.
>
> I think the doc could start from how to deploy the development envi
+1 (non-binding)
I checked:
- All links are valid
- LICENSE and NOTICE files exist
- The Signature is good, the checksum is correct
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
wei jin 于2021年12月31日周五 18:17写道：
>
> +1 binding
agreed, I've found very little feedback on Tengine in the communit, it
seems that people don't really need it.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zeping Bai 于2021年12月20日周一 21:25写道：
>
> Hi, Zexuan.
>
Congrats!
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Tsangleslie 于2021年12月19日周日 14:44写道：
>
> Congratulation !
>
> Leslie Tsang
> leslie.ts...@icloud.com
>
> > On 19 Dec 2021, at 1:30 PM, Chao Zhang
OK, I like this way.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Li Yang 于2021年11月24日周三 下午2:43写道：
>
> Exactly!
>
> On Wed, Nov 24, 2021 at 2:41 PM ZhengSong Tu wrote:
>
> > I got. you mean that when the reque
1. Did you mean to put the consumer_name to the ctx in open-connect plugin?
2. Then we can limit by consumer_name in limit-* plugins.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Joga, singh 于2021年11月26日周五 上午12:26写道：
>
> Hi Guy
iews, but it would be great if we could push for a
consensus within the community.
Note: The issues discussed above are only a small part of the issues
discussed in this email list.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zhiyuan Ju
I see you have already mentioned the issue[1], great!
[1]:https://github.com/yuz10/lua-resty-rocketmq/issues/4
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
YuanSheng Wang 于2021年11月25日周四 上午11:47写道：
>
> On Thu, Nov 25, 2021 at 9
I can't find lua-resty-rocketmq on luarocks, maybe we need to work
with this author? Or fork a copy of it?I
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
YuanSheng Wang 于2021年11月25日周四 上午9:03写道：
>
> On Wed, Nov 24, 2021
just like https://github.com/doujiang24/lua-resty-kafka
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
ZhengSong Tu 于2021年11月24日周三 下午7:46写道：
>
> we need lua-resty-rocketmq lib first?
>
> *ZhengSong Tu*
> My GitHub: htt
we need lua-resty-rocketmq lib first?
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Bisakh Mondal 于2021年11月24日周三 下午5:54写道：
>
> Nice proposal! I am willing to help developing the plugin on the first week
> of December.
>
&
.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zhiyuan Ju 于2021年11月24日周三 下午4:26写道：
>
> Hi, community members,
>
> Yesterday, one of Apache APISIX's community users asked me how to involve
> in our community, so I hold
+1 (non-binding)
I checked：
1. Download links are OK.
2. Checksum and signature are OK.
3. LICENSE and NOTICE have existed.
4. Building on macOS 11.6 was successful.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo 于2021年11月24
I got. you mean that when the request matched route1 and route2,
APISIX use route1 to match the request first.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
ZhengSong Tu 于2021年11月23日周二 下午7:02写道：
>
> AFAIK, in this case, the l
AFAIK, in this case, the logical operator of the elements in route1's
vars is and, the request must reach these three conditions before it
will be captured by route1. so it has nothing to do with route2's
vars.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache API
hi, yang.
> Route X should be matched first if and only if route X's matching
> rule set is a proper superset of route Y's matching rule set.*
I have doubts about this, can you show some example?
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://g
I found https://apisix.apache.org/cont ribute/ is broken on my side,
and seems not cause by cache of chrome.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zhiyuan Ju 于2021年11月22日周一 下午12:32写道：
>
> Thanks to Sarendipity96's c
Welcome to join us!
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
YuanSheng Wang 于2021年11月22日周一 下午9:10写道：
>
> Congratulations ^_^
>
>
> On Mon, Nov 22, 2021 at 6:29 PM Shivam Singh wrote:
>
> > Thank you
guage.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX：https <https://github.com/apache/apisix>:
//github.com/apache/apisix <https://github.com/apache/apisix>
Zhongming Hua 于2021年11月19日周五 上午10:09写道：
> We can provide a spring-cloud-starter-apisix to provide ga
yes, but need to wait
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
寒香 <1014631...@qq.com.invalid> 于2021年11月16日周二 下午7:04写道：
> Is there an updated plan to resolve this problem?
>
>
>
>
> -- 原始邮件
hi, apisix-java-plugin-runner not support to fetch request body yet.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
寒香 <1014631...@qq.com.invalid> 于2021年11月16日周二 下午4:34写道：
> Hi, everyone:
> I want to fetch request bo
+1 (non-binding)
I have checked:
1. Download links are OK.
2. Checksum and signature are OK.
3. LICENSE and NOTICE are exist.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zeping Bai 于2021年10月15日周五 下午8:05写道：
> +1 (non-binding)
&g
Hi, I see you have already submitted the issue, we can continue in the
issue.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
寒香 <1014631...@qq.com.invalid> 于2021年10月15日周五 下午4:12写道：
> Yes,I reproduced all steps
Sounds good, I like it.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Tsangleslie 于2021年10月8日周五 下午6:39写道：
> Yes, I create a repo `apish-workbench` for POC, it work fine in macOS,
> have a quick look of https://github.com/
Are you saying that we can build a development environment on windows using
Vagrant?
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX：https <https://github.com/apache/apisix>:
//github.com/apache/apisix <https://github.com/apache/apisix>
Tsangleslie 于2021年10月
I don't know what the generated code looks like, I'll do some verification
when I have time.
Maybe we can use the generated code as basic, and write more functional
code manually.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Good for me, +1
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
wei jin 于2021年9月26日周日 下午6:56写道：
> Hi, community,
>
> The current APISIX image depends on the official version of openresty, but
> APISIX needs to support mo
if the SDK is generated by `openapi generator`, what is its form? code or
jar?
I think even if it was code, then as an SDK there would still be things
like reading admin-keys, hosts etc from the config file that would still
need to be written.
*ZhengSong Tu*
My GitHub: https://github.com
admin-api in a language they are familiar with.
If an SDK is available, it is much easier to integrate APISIX with other
systems.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
孙昊 于2021年9月25日周六 下午6:27写道：
> Hello, everyone:
>
ZhengSong Tu
8月24日周二 下午8:21
发送至 dev
+1
I check:
1. All download links are fine;
2. Checksums and PGP signatures are fine;
3. LICENSE and NOTICE exist;
4. Build and test success on macOS 11.2.3
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache
Agreed, we need an LTS version.
Do we need to do something different for the LTS version than we did for
the previous release?
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo 于2021年9月16日周四 下午2:23写道：
> We are going
so cool!
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Shivam Singh 于2021年9月15日周三 下午8:43写道：
> Hi community,
>
> I am psyched to announce to you all that the new redesigned and better
> version of our website is in the f
+1
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
wei jin 于2021年9月10日周五 上午8:53写道：
> Currently, when `apisix-dashboard` is building docker images, it cannot be
> automatically pushed to docker hub.
>
> I hope to be able to a
+1 non-binding
I check:
1. All download links are fine;
2. Checksums and PGP signatures are fine;
3. LICENSE and NOTICE exist;
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo 于2021年8月31日周二 上午11:08写道：
> Hello, Commun
+1 non-binding
I check:
1. All download links are fine;
2. Checksums and PGP signatures are fine;
3. LICENSE and NOTICE exist;
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
JinChao Shuai 于2021年8月26日周四 下午8:54写道：
> Hello, Commun
+1
I check:
1. All download links are fine;
2. Checksums and PGP signatures are fine;
3. LICENSE and NOTICE exist;
4. Build and test success on Fedora release 33 (aarch64)
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo 于
+1 (non-binding)
checklist:
1. All download links are fine;
2. Checksums and PGP signatures are fine;
3. LICENSE and NOTICE exist;
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
Jintao Zhang 于2021年8月14日周六 下午2:02写道：
> Hello, Commun
+1 (non-binding)
checklist:
1. All download links are fine;
2. Checksums and PGP signatures are fine;
3. LICENSE and NOTICE exist;
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass
Apache APISIX: https://github.com/apache/apisix
JunXu Chen 于2021年8月11日周三 下午2:26写道：
> Hello, Commun
agree +1
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo 于2021年8月5日周四 上午9:43写道：
> Yes.
> The ExtraInfoReq already contains type and name (if needed).
>
> ZhengSong Tu 于20
One more question: How does APISIX know which ExtraInfo the Runner
wants? Declare it in ExtraInfoReq？
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo 于2021年8月5日周四 上午9:01写道：
> >
This is an upgrade to the protocol between Runner and APISIX? Sounds good
to me. This allows Runner to use some common TCP unpacking functions.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo
ussions:
without generating any decisions affecting the project.
Even if we find something interesting in the Discussions, it needs to be
discussed in the mail list. The opinions in the Discussions are only to be
used as supporting evidence.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <
or modify?
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
Zexuan Luo 于2021年8月3日周二 上午9:00写道：
> > If we see questions in the issue, IM, that is suitable for discussion in
> GitHub Discussions,
cle writers can
interact on an ongoing basis on a particular article, and the article does
not need to be published as a result.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
Zhiyuan Ju 于2021年8月3日
e content that
users are interested in, like issue deposits, links to various learning
resources related to the project, and those mentioned in the Proposal.
More discussion is needed on this problem.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphi
Of course, GitHub discussions do not cover topics with code-related
discussions and project management activities.
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
Ming Wen 于2021年8月2日周一 下午1:23写道：
&
> > > >> > is adopted, divided into 3 phases.
> > > > >> > > > >> >
> > > > >> > > > >> > **Phase 1**
> > > > >> > > > >> >
> > > > >> > > > >> > The first phase requires a quick solution to the
> problem
> > in
> > > > the
> > > > >> > > > >> following
> > > > >> > > > >> > way.
> > > > >> > > > >> > 1. Now, the latest version of Dashboard is 2.7, and the
> > > > latest
> > > > >> > > version
> > > > >> > > > >> of
> > > > >> > > > >> > APISIX is 2.7.
> > > > >> > > > >> > 2. Disregard the historical version matching problem
> and
> > > > >> deprecate
> > > > >> > > the
> > > > >> > > > >> > version matching logic (manually maintaining a Mapper).
> > > > >> > > > >> > 3. Compare Dashboard 2.7 with APISIX 2.7 and sort out
> > where
> > > > >> > > Dashboard's
> > > > >> > > > >> > existing features are inconsistent with APISIX (API
> > fields,
> > > > >> plugin
> > > > >> > > > >> schema).
> > > > >> > > > >> > 4. Update Dashboard to match the existing features with
> > > > APISIX
> > > > >> 2.7
> > > > >> > > and
> > > > >> > > > >> > release version 2.7.1.
> > > > >> > > > >> >
> > > > >> > > > >> > **Phase 2**
> > > > >> > > > >> >
> > > > >> > > > >> > The second phase requires enriching Dashboard
> > functionality
> > > > to
> > > > >> > match
> > > > >> > > > >> APISIX
> > > > >> > > > >> > functionality.
> > > > >> > > > >> >
> > > > >> > > > >> > 1. Sort out which APISIX 2.7 features are not
> implemented
> > > in
> > > > >> > > Dashboard
> > > > >> > > > >> > 2.7.1, such as Stream Proxy, Service Discovery, etc.
> > > > >> > > > >> > 2. Update the Dashboard to include the existing
> features
> > of
> > > > >> APISIX
> > > > >> > > 2.7
> > > > >> > > > >> and
> > > > >> > > > >> > release version 2.7.2.
> > > > >> > > > >> >
> > > > >> > > > >> > **Phase 3**
> > > > >> > > > >> >
> > > > >> > > > >> > Phase 3 requires the Dashboard to synchronize the
> APISIX
> > > > >> release
> > > > >> > > > >> schedule
> > > > >> > > > >> > and release APISIX with the same version number, e.g.,
> > 2.8,
> > > > >> > within a
> > > > >> > > > >> > manageable time frame after the release of APISIX.
> > > > >> > > > >> >
> > > > >> > > > >> > 1. APISIX milestones are visible in GitHub.
> > > > >> > > > >> > 2. After APISIX is released, sort out what is different
> > > > between
> > > > >> > > APISIX
> > > > >> > > > >> and
> > > > >> > > > >> > the previous version, and then adapt it in Dashboard.
> > > > >> > > > >> >
> > > > >> > > > >> > **Another Phase (Long-term solution)**
> > > > >> > > > >> >
> > > > >> > > > >> > In addition, I have a long-term plan, the current
> > > > architecture
> > > > >> is
> > > > >> > to
> > > > >> > > > >> > separate DP and CP, and the ManagerAPI in CP does a lot
> > of
> > > > >> > functions
> > > > >> > > > >> that
> > > > >> > > > >> > AdminAPI duplicates, so we might as well deprecate
> > > ManagerAPI
> > > > >> and
> > > > >> > > turn
> > > > >> > > > >> > Dashboard into **a pure Web project**, directly
> accessing
> > > > >> > AdminAPI,
> > > > >> > > so
> > > > >> > > > >> that
> > > > >> > > > >> > when the data in the Request Body is illegal, AdminAPI
> > will
> > > > >> return
> > > > >> > > an
> > > > >> > > > >> error
> > > > >> > > > >> > directly. Of course, this requires a more detailed
> > solution
> > > > >> design
> > > > >> > > and
> > > > >> > > > >> is a
> > > > >> > > > >> > big change.
> > > > >> > > > >> >
> > > > >> > > > >> > What do you think?
> > > > >> > > > >> >
> > > > >> > > > >> > Best Regards!
> > > > >> > > > >> > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > >> > > > >> >
> > > > >> > > > >> >
> > > > >> > > > >> > Zhiyuan Ju 于2021年7月14日周三
> > 下午1:46写道：
> > > > >> > > > >> >
> > > > >> > > > >> > > Hi,
> > > > >> > > > >> > >
> > > > >> > > > >> > > Currently, Apache APISIX Dashboard and Apache APISIX
> > are
> > > > two
> > > > >> > > separate
> > > > >> > > > >> > > projects (hereinafter referred to as Dashboard and
> > > APISIX).
> > > > >> > > Whenever
> > > > >> > > > >> > APISIX
> > > > >> > > > >> > > changes the content (e.g., APIs, API fields, Entity
> > > > >> definitions,
> > > > >> > > > >> etc.),
> > > > >> > > > >> > > Dashboard needs to match the changes and publish a
> new
> > > > >> version.
> > > > >> > > > >> > >
> > > > >> > > > >> > > Because the Apache APISIX Dashboard's version number
> is
> > > not
> > > > >> the
> > > > >> > > same
> > > > >> > > > >> as
> > > > >> > > > >> > > Apache APISIX, then users get confused when using the
> > > > >> Dashboard,
> > > > >> > > so I
> > > > >> > > > >> > draft
> > > > >> > > > >> > > a proposal to support showing incompatible
> information
> > > more
> > > > >> > > clearer on
> > > > >> > > > >> > the
> > > > >> > > > >> > > Dashboard.[1]
> > > > >> > > > >> > >
> > > > >> > > > >> > > Due to there have some prototypes I made, so I put
> them
> > > in
> > > > >> the
> > > > >> > > GitHub
> > > > >> > > > >> > > issue[1], looking forward to your feedback!
> > > > >> > > > >> > >
> > > > >> > > > >> > > [1]
> > > > >> > > > >> > >
> > > > >> > > > >> >
> > > > >> > > > >>
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://github.com/apache/apisix-dashboard/issues/1944#issuecomment-879607016
> > > > >> > > > >> > >
> > > > >> > > > >> > > Best Regards!
> > > > >> > > > >> > > @ Zhiyuan Ju <https://github.com/juzhiyuan>
> > > > >> > > > >> > >
> > > > >> > > > >> >
> > > > >> > > > >>
> > > > >> > > > >
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
>
--
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
Agree, especially with the Long-term solution. I feel that the Manager API
and AdminAPI conflict in capability, leading to some ambiguity in the
positioning of the Manager API.
Zhiyuan Ju 于2021年7月25日周日 下午5:38写道：
> Hi, community,
>
> After this discussion is closed, I will create 2 milestones to
+1 non-binding
checklist:
1. All download links are fine;
2. Checksum and signature are fine;
3. LICENSE and NOTICE exist;
4. build and test success on Fedora release 33 (Thirty Three)
Zexuan Luo 于2021年7月23日周五 下午7:45写道：
> Hello, Community,
> This is a call for the vote to release Apache APISIX
+1， gerat!
JinChao Shuai 于2021年7月20日周二 下午2:05写道：
> Hi Dev Team:
>
> We would like to start a new proposal about creating APISIX Python plugin
> runner project.
>
> APISIX Python plugin runner is a sub-project of APISIX as part of APISIX
> multilingual Support and supports APISIX running Python p
+1 non-binding
I checked:
* all download links are fine;
* the signature and checksum are valid;
* LICENSE and NOTICE files exist;
Zexuan Luo 于2021年7月12日周一 上午10:15写道：
> Hello, Community,
> This is a call for the vote to release Apache APISIX Go Plugin
> Runner version 0.1.0.
>
> Release notes:
agree, +1
JunXu Chen 于2021年7月8日周四 下午7:48写道：
> hi,
>
> I prefer to name the next version of the Dashboard as `2.8-rc1`, which can
> be used with Apache APISIX 2.7.
>
> And then 2.8 is used with Apache APISIX 2.8.
>
>
> On Thu, 8 Jul 2021 at 17:25, ZhengSon
they intuitively believe that
apisix 2.7 and apisix dashboard 2.7 are a match.
I think we should follow this intuition, and the next version of the
dashboard could be named 2.7-alpha, and then apisix and apisix dashboard
could match on 2.8.
Would like to know the community's opinion.
--
This component will automatically adapt to different service discovery
frameworks, such as nacos, consul, zookeeper, etc？
Zexuan Luo 于2021年7月6日周二 下午6:07写道：
> Currently, we do service discovery on the DP side. Each APISIX
> instance talks with the service discovery service directly, asks for
> ne
I get, +1.
Zexuan Luo 于2021年7月7日周三 上午8:55写道：
> If we have N route configuration data for the same route, the
> limit-req rank will be N * rate as each configuration has its own
> counter.
>
> ZhengSong Tu 于2021年7月6日周二 下午9:19写道：
> >
> > I think I see what you mean
I think I see what you mean. When apisix has some data stored in a lua
shared dict,
the data structure of the current communication between
apisix and runner cannot be expressed, is that what you mean？
> we need a way to store route
> level data, which is useful for limit-req or other similar feat
-plugin-runner/blob/main/docs/en/latest/development.md
>
> The vote will be open for at least 72 hours or until necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
--
*ZhengSong Tu*
My GitHub: https://github.com/tzssangglass <https://github.com/membphis>
Apache APISIX: https://github.com/apache/apisix
+1
look forward it
Joey Ma 于2021年5月26日周三 上午10:56写道：
> +1
>
> On Wed, May 26, 2021 at 10:46 AM Zeping Bai wrote:
>
> > +1
> >
> >
> >
> > *发件人: *JunXu Chen
> > *发送时间: *2021年5月26日 10:24
> > *收件人: *dev@apisix.apache.org
> > *主题: *Re: [VOTE][New Subproject] Establish APISIX Go plugin runner
> >
> >
yes, this looks more accurate
Zexuan Luo 于2021年5月24日周一 下午9:09写道：
> `admin_api_object_bind ` is confusing. We always bind the objects.
> What about configuration_allow_missing_reference?
>
> ZhengSong Tu 于2021年5月24日周一 下午8:44写道：
> >
> > Hi folks,
> >
> > Ba
Hi folks,
Background
Now that the apisix admin api has a binding relationship. For example,
there is an upstream id in a route, and if you want to delete the upstream
pointed to by this upstream id, you have to delete the route first,
otherwise you will get an error like this "can not delete this
-openresty
Log Push API: https://www.moesif.com/docs/api#api-calls
--
ZhengSong Tu
tzssanggl...@gmail.com
good idea.
+1 from me.
Chao Zhang 于2021年5月19日周三 下午4:42写道：
> That’s a good idea. +1 From me.
>
> Chao Zhang
> https://github.com/tokers
>
> On May 19, 2021 at 16:00:38, Zexuan Luo (spacewan...@apache.org) wrote:
>
> The "Semantic Pull Requests" is an App that checks the PR's title
> automatically
+1，a suitable name
Daming 于2021年5月6日周四 下午12:55写道：
>
> +1 （non-binding)
>
> How about apisix-java-plugin-runner as the new repo name?
>
> ——
> Haochao Zhuang(@dmsolr)
> Apache SkyWalking
>
>
> > 2021年5月6日 下午12:06，ZhengSong Tu 写道：
> >
> > H
to this
project.
New project repo, APISIX java plugin runner Issue, APISIX main repo issue
system Maillist/Slack, keep the same.
The initial committers are
Haochao Zhuang(ApacheID: daming),
ZhengSong Tu
Note:
Mailing list for [Proposal] support using other languages to write plugin
for APISIX
; Ming Wen, Apache APISIX PMC Chair
> Twitter: _WenMing
>
>
> Ming Wen 于2021年5月3日周一 下午8:05写道：
>
> > +1
> >
> > look forward to this project
> >
> > Daming 于2021年5月3日 周一下午8:04写道：
> >
> >> Hi
> >> +1, This is a wonderful sub-projec
; >
> > > And about debugging, once your APISIX process could access the JVM
> > through
> > > a socket with manual localhost:port, it is fine for the Java developer
> to
> > > start this sidecar in the IDEA.
> > >
> > > Sheng Wu 吴晟
> > > Tw
Mailing list for [Proposal] support using other languages to write plugin
for APISIX:
https://lists.apache.org/thread.html/r7524b2622fbdf152a83b48e8c9d680075fbe64cb0f3591e0bf3212e9%40%3Cdev.apisix.apache.org%3E
ZhengSong Tu 于2021年4月29日周四 下午4:27写道：
> Hi, Community
>
> We are imple
Hi, Community
We are implementing a feature that supports writing apisix plugins in
multiple languages.
In the first phase, we intend to support java first, so we will have a new
project named apisix-java-plugin-runner, whose role is to run the java
plugin code written by the user, and communica
/github.com/juzhiyuan>
>
>
> ZhengSong Tu 于2021年4月26日周一 上午11:47写道：
>
> > I have sketched the flow of the java side of the plugin runner
> > [image: APISIX 运行 Java 插件.png]
> >
> > And I have some questions to clarify.
> >
> > 1. How does the plugin ru
I have sketched the flow of the java side of the plugin runner
[image: APISIX 运行 Java 插件.png]
And I have some questions to clarify.
1. How does the plugin runner load the client's code?
It's up to each runner to figure it out according to its own language's
ecology. Take java as an example,
t
96 matches
Mail list logo
