英文:
How to deal with `app_engine_apis` warning when updating app.yaml from go114 to go115
问题
我最近将我的app.yaml
从
runtime: go114
更新为
runtime: go115
因为我在一封电子邮件中收到警告,称对于go114
的支持即将结束。
服务部署成功,但在完成后,我收到了以下消息:
> 正在更新服务 [default]...⠼警告:您的 app.yaml 中存在对 App Engine API 的间接依赖,但这些 API 在您的 app.yaml 中未启用。您可能会在尝试访问这些 API 时看到运行时错误。请设置 app_engine_apis 属性。
所以我添加了:
app_engine_apis: true
现在服务无法部署并显示以下错误:
> 错误:(gcloud.app.deploy) 解析文件时出错:[<snip>/app.yaml] 对于类型为 AppInfoExternal 的对象,出现了意外属性 'app_engine_apis'。
看起来是一个进退两难的情况。我该如何处理这个问题?
英文:
I recently updated my app.yaml
from
runtime: go114
to
runtime: go115
because I was warned in an email that support for go114
was ending.
The service deployed fine but after it finished, I got the message:
> Updating service [default]...⠼WARNING: There is an indirect dependency on App Engine APIs, but they are not enabled in your app.yaml. You may see runtime errors trying to access these APIs. Set the app_engine_apis property.
So I added:
app_engine_apis: true
And now the service won't deploy and gives this error:
> ERROR: (gcloud.app.deploy) An error occurred while parsing file: [<snip>/app.yaml]
Unexpected attribute 'app_engine_apis' for object of type AppInfoExternal.
Looks like a catch 22. How do I deal with this?
答案1
得分: 2
将此作为社区wiki发布,因为它基于@Joel的评论。
看起来是由于尚未在go115
中启用这些API,所以会触发此处,您可能会遇到运行时错误。
我建议您可能应该联系Google Cloud,要么在他们的问题跟踪系统中提出问题,要么在此GitHub页面上开启一个问题,以便他们可以解决此问题,因为似乎没有任何解决方法。
英文:
Posting this as community wiki as it's based on @Joel's comments.
It looks like this is being triggered, since those APIs aren't enabled yet in go115
, you might get a runtime error.
I would say that you should probably reach out to Google Cloud either in their Issue Tracker system or open an Issue in this Github Page so that they can fix this issue, as there doesn't seem to be any workarounds for this one.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论