本文介绍了完全API访问不适用于Taskqueue的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
我有一个新的Debian GCE VM，可以完全访问Google Cloud服务.我可以从该实例访问大多数服务.但是我无法访问任务队列.
I have a new Debian GCE VM which has full access to Google Cloud services. I'm able to access most of the services from this instance. However I'm unable to access task queues.
host:~/home$ curl
"https://www.googleapis.com/taskqueue/v1beta2/projects/project/taskqueues/
my-queue/tasks" -H "Authorization":"Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxx"
{
"error": {
"errors": [
{
"domain": "global",
"reason": "insufficientPermissions",
"message": "Insufficient Permission"
}
],
"code": 403,
"message": "Insufficient Permission"
}
}
从我的另一个对单个服务有细粒度访问的VM，我可以访问任务队列.这是一个已知问题吗?
From my other VM which has fine grained access to individual services, I'm able to access task queue. Is this a known issue?
推荐答案
不可能，我从Google获得了有关TaskQueue REST API的答案:
It's not possible, I got the answer from Google about TaskQueue REST API:
一种解决方法是设置导出GOOGLE_APPLICATION_CREDENTIALS=/path/to/servicekey.json.
A workaround is to set export GOOGLE_APPLICATION_CREDENTIALS=/path/to/servicekey.json.
这篇关于完全API访问不适用于Taskqueue的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！