Cloud Job Task spec MaxRetries should be a pointer about google-api-go-client HOT 5 CLOSED

This is by design. To send fields that are default type values and omitted with omitempty please use ForceSendFields: https://pkg.go.dev/google.golang.org/api#hdr-ForceSendFields. Hope that helpes.

from google-api-go-client.

This is by design. To send fields that are default type values and omitted with omitempty please use ForceSendFields: https://pkg.go.dev/google.golang.org/api#hdr-ForceSendFields. Hope that helpes.

Thank you! My bad, I had completely missed the ForceSendFields field. Still getting used to the Google api differences when compared to AWS.

from google-api-go-client.

No problem! Just an FYI we also offer a newer style of library that has some improved ergonomics. Here is the equivalent for the API you are using: https://pkg.go.dev/cloud.google.com/go/[email protected]/apiv2

from google-api-go-client.

Thank you for trying to help! I have now tried the suggested ForceSendFields and can report that it only helps with marshaling the Yaml, but the problem still persists because Cloud Deploy uses Skaffold to unmarshal the yaml by using Golang. This means that to Skaffold the field will still be 0 and count as empty field that won't be sent to the Cloud Run Job. MaxRetries ends up defaulting back to 3. I also created a Cloud Forum support post about this problem as I consider the API implementation to be flawed when it comes to yaml based workflows. Unless of course I'm missing something.

from google-api-go-client.

I would report this to the skaffold project -- it seems like this is something they could potentially address in their layer, detecting if a variable is present in the yaml.

from google-api-go-client.