Skip to content
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

webhook功能能否添加这次修改的参数 #5060

Closed
Phoebus888 opened this issue Dec 21, 2023 · 1 comment
Closed

webhook功能能否添加这次修改的参数 #5060

Phoebus888 opened this issue Dec 21, 2023 · 1 comment

Comments

@Phoebus888
Copy link

文档:https://www.apolloconfig.com/#/zh/development/portal-how-to-enable-webhook-notification
比如发布后我想获取到这次版本更改了那些key,能否有值展示出来

Copy link

dosubot bot commented Dec 21, 2023

🤖

Hello @Phoebus888! 😊 I'm Dosu, an assistant here to help you with Apollo repository. I'm capable of helping you solve bugs, answer questions, and contribute to the project while we wait for a human maintainer to join us. Looking forward to assisting you on this journey!

根据我找到的相关信息,Apollo的webhook功能确实可以添加参数以显示发布版本后更改的键。在请求体样本中,有一个名为"configuration"的字段,它是一个对象数组。这个数组中的每个对象都有两个属性:"firstEntity"和"secondEntity"。"firstEntity"代表配置的键,"secondEntity"代表配置的值。

当一个配置被发布时,webhook会发送一个包含"configuration"数组的HTTP post请求。这个数组将包含所有要发布的配置,因此,它将显示发布版本后更改的键。

以下是请求体样本的相关部分:

"configuration": [ { // all configurations to be released; also applys to gray release
    "firstEntity": "",  // key of configuration
    "secondEntity": ""  // value of configuration
} ],

在这个例子中,"firstEntity"是被更改的配置的键,"secondEntity"是该键的新值。

关于这个问题,我找到了一个类似的已解决问题:WebHook功能不包括更改的配置。这个问题的建议解决方案是:WebHook功能应该更新,以包括两个版本之间的差异,类似于电子邮件通知功能。这可以通过复用带有更改的releaseHistory对象来实现。

但是,我没有在Apollo代码库中找到webhook有效载荷的当前结构。可能需要在其他地方找到答案,或者我可能错过了。

如果你需要更多的帮助,或者有其他的问题,欢迎随时向我提问。

Sources


This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant