Abdulla Abdurakhmanov

Most likely this is related to the authentication so you have something off in your generated token.

Your Cargo.toml is fine. > I'm using service account saved as JSON. This service account should have the necessary permissions, but I'll double check. I'm quite sure this is related...

Try to check using: ``` gcloud auth application-default login ``` and compare those JSON files - one generated by gcloud tool, and another yours. PS. `gcloud cli` generates usually a...

I checked even when you don't permissions you are supposed to get something like this: ``` ResponseError(ResponseContent { status: 403, content: "{\n \"error\": {\n \"code\": 403,\n \"message\": \"Required 'compute.instances.list' permission...

This is interesting, so you're saying the same setup for the same project ID and instance names you have actually other methods working and only `compute_instances_start` fails? Then I was...

> let compute_config = google_rest_client.create_google_compute_v1_config().await Can you elaborate how are using those configs? Are you storing them for long time and reusing? If so, please create them for each requests...

I tested this example with my service account and test project: ``` let google_project_id = gcloud_sdk::GoogleEnvironment::detect_google_project_id().await .expect("No Google Project ID detected. Please specify it explicitly using env variable: PROJECT_ID"); let...

I think service accounts are irrelevant now - if at least one method is working. Something with either network/proxy or your parameters (structure fields for params).

It is hard me to help here since this is not reproducible on my infrastructure. As one possible option to debug you can try to check HTTP request printing it...

Hey, hm, interesting. Maybe this is related that I had different reqwest version when I tested it. Right now I have "0.11.20" in my lock file. Which one do you...