Open ViniciusSossela opened 2 years ago
I wish I knew every Google API, but know enough to say that they may all have their own subtle requirements which can lead to surprising behaviour. There was a version of the accompanying CLIs which could display all HTTP communication, but that feature unfortunately fell victim to getting the crates through the years.
All there is to do is to study the official documentation or use a JS-in-browser binding to see what actually happens under the hood. Maybe such insight would help to make the 'right' calls through this API binding, too.
I hope that helps.
@Byron Thanks for replying.
Gonna find out what is really happening under the hood.
If I find out some solution, Can we improve the documentation for a better understanding of Google Cloud Task use?
It's possible to customize per API data that is the input of the code generation stage, even though the particular capability of customizing documentation isn't implemented yet. Doing so won't be hard, either, but certainly needs some contribution effort to get there.
I am getting stuck trying to create a new Queue and also trying to add a Task to an existing Queue with the following code. Am I missing something?
The service account below has all the Cloud Tasks API permissions setup.
Result:
Adding task code:
Result: