如何为Google Release上的操作提供不同的实现URL？ [英] How can I provide different fulfillment URLs for Actions on Google Release?

问题描述

位于> https://developers.google.com/actions/deploy/ release-environments 指出：要处理实现中的发布渠道，您应提供不同的实现URL（例如，一个Beta的实现URL和另一个用于Action版本的URL）。但是，没有有关如何完成此操作的说明。

The documentation at https://developers.google.com/actions/deploy/release-environments states "To handle release channels in your fulfillment, you should provide different fulfillment URLs (for example, one fulfillment URL for the beta and another URL for the production version of your Action)." However, there are no instructions on how this should be accomplished.

当我在Google项目上创建Actions时，便创建了一个Firebase项目，我在其中上传了支持这些功能的JavaScript通过对我们的后端服务的请求来执行操作。该Firebase项目提供了我的Beta版本用于实现的URL。现在，我需要创建一个Alpha项目，该项目指向另一个Firebase项目，我将对请求的支持的新版本上载到我们后端服务的不同版本。我看不出有办法实现这一目标。我是否需要在Google项目上创建一个全新的Actions，该项目具有自己的实现网址，还是有更好的方法来完成此任务？

When I created my Actions on Google project, a Firebase project was created to which I upload JavaScript that supports those actions via requests to our backend service. That Firebase project provides the URL used by my Beta release for fulfillment. I now need to create an Alpha project that points to a different Firebase project to which I will upload new versions of support for requests to different versions of our backend service. I do not see a way to accomplish this. Do I need to create an entirely new Actions on Google project that has its own URL for fulfillment or is there some better way to accomplish this task?

我尝试手动创建一个单独的Firebase项目来托管Alpha代码，但这没有用。后来我了解到，当您在Google项目上创建一个Actions时，该项目与为其创建的Firebase项目紧密相连，并且无法指向另一个项目。

I tried creating manually creating a separate Firebase project to host the Alpha code but that did not work. I later learned that when you create a Actions on Google project that it is intimately connected to the Firebase project created for it and cannot be pointed to another.

问题出在所有在Google和Firebase上的操作的配置空间中。没有代码可显示。

The problem is all in the configuration space of Actions on Google and Firebase. There is no code to show.

我希望可以使用类似于Alexa开发人员控制台和Amazon Lambda管理控制台提供的方法。在这种方法中，我具有Alexa Skill的Alpha，Beta和Production版本，并且每个版本都指向不同版本的lambda函数，每个版本都有一个适当的值来指示执行lambda函数的环境。这样一来，我就可以将请求分配给正确的后端服务（Alpha，Beta版，正式版）。

I would expect that some approach similar to that provided by the Alexa Developer Console and the Amazon Lambda Management Console would be available. In that approach, I have Alpha, Beta, and Production versions of the Alexa Skill and each of them points to a different version of the lambda function each of which has an appropriate value to indicate the environment that the lambda function is executing upon. This allows me to allocate requests to the correct backend service (alpha, beta, production).

我在 Google上的操作/

I don't see a way to accomplish that in the Actions on Google/Firebase world.

推荐答案

如果您使用的是Dialogflow，则Google发行版上的操作具有相应的环境。因此，您应该能够为每个环境设置不同的实现URL，以指向不同的项目。

If you are using Dialogflow, the Actions on Google release levels have corresponding environments. So you should be able to set a different fulfillment URL for each environment to point at the different project.

这篇关于如何为Google Release上的操作提供不同的实现URL？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！