admin管理员组文章数量:1400674
When I try to call a rewrited route to a Run Container I got a not found
page.
If I call this Run Container from it's URL it's working fine so I think it's something I'm missing or maybe a bug with rewrites.
Here's my firebase.json
config:
"hosting": [
{
"public": "wiki/api",
"target": "api",
"ignore": [
"firebase.json",
"**/.*",
"**/node_modules/**"
],
"rewrites": [
{
"source": "/",
"destination": "/index.html"
},
{
"source": "/admin{,/**}",
"function": {
"functionId": "admin",
"region": "southamerica-east1"
}
},
{
"source": "/gotenberg{,/**}", // this is the rewrite that's not working
"run": {
"serviceId": "gotenberg",
"region": "southamerica-east1"
}
},
{
"source": "/**",
"function": {
"functionId": "api",
"region": "southamerica-east1"
}
}
]
}
All my other rewrites are working fine. I think it's because I'm rewriting to Functions (even if all functions are in v2 and they are showing inside Cloud Run section on console).
What am I missing?
本文标签: google cloud runFirebase rewrite to run service leading to quotnot foundquot pageStack Overflow
版权声明:本文标题:google cloud run - Firebase rewrite to run service leading to "not found" page - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1744250636a2597233.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论