Limitations of running GAM in GCP Cloud Run?

[Matt Duran]

Hi folks, 

I'm running into a fairly specific problem that I'm curious if anyone has run up against and am wondering if this is just not the use case for GAM. I'm currently working on a serverless flask frontend for GAM for folks on our support team that aren't as comfortable with CLI -- similar to this: https://groups.google.com/g/google-apps-manager/c/x88etXlMZfo/m/aA1rYDLuBwAJ. The idea with making it serverless was to cut down on the idle time of a VM -- we already have a VM set up that we can SSH into and run commands from if we needed to. 

I had made a pretty barebones "backend" that we could GET, POST, DELETE, etc. to and in GCP's Cloud Run and it worked! At least for a while -- after a few hours or so I'd run into a problem that my credentials would be invalid. If I ran the same command locally on my computer, no problem at all. If I then pushed the same oauth2.txt and client_secrets.json files to the container, it'd work again, but then same error would crop up after a bit.

After reading a bit more about the oauth flow, I'm thinking that this is related to the  expiration time? I'm sure I could figure out some method of storing these in a bucket and letting the container update them as needed, but figured before I went down that rabbit hole I'd ask if anyone has run into a similar problem? Any and all help is appreciated!

[Matt Duran]

Hey Ross,

Thanks for taking the time to hop on Zoom with me! I'll update you with the changes once I update the source and make those config changes in GCP!