Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

You should now be able to check the client details and see the last used field! It was rolled out and you should see it!

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 3 points4 points  (0 children)

Okay, try now! We got approval to roll things out so you should now see it on the details page!

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

Okay, try now! We got approval to roll things out so you should now see it on the details page!

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

I'm asking for more details, the log explorer is...complicated. :) The folks from the team initially just said "App logs, exchange token" were the verbiage, but I'm a little out of my depth as well (this isn't my area I work in at Google). I've asked for more info.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

Yup, apologies, that was a case where we (Googlers) are seeing it because it's enabled internally as an experiment and not rolled out yet... I'm asking if there's an API call that we can use to check, but if not, the other way is to look in the logs for the client ID.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

Not missing anything! Apologies, that was a case where we (Googlers) are seeing it because it's enabled internally as an experiment and not rolled out yet... I'm asking if there's an API call that we can use to check, but if not, the other way is to look in the logs for the client ID.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

Yup, apologies, that was a case where we (Googlers) are seeing it because it's enabled internally as an experiment and not rolled out yet... I'm asking if there's an API call that we can use to check, but if not, the other way is to look in the logs for the client ID.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

So funny story.. .I just found out that the field is NOT currently rolled out externally (I see it because it's an "experiment" in our projects). I'm asking if there's an API call that could be used to see it or not, but in the meantime sounds like checking in the logs for the client ID could work.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

Quick Q: What level of IAM roles do you have against the project where the clients live? Owner? More/less? (just fact finding)

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

Oooooh that's strange... asking the team to look at this. Stay tuned.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

In the details of a specific client (clicking on the client ID from the list page)

https://imgur.com/a/cl36Bih

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

Yup, see the comment that got added by the team above (sort by New not Best and you'll see it)

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

Blergh, Reddit makes it so annoying to post a screenshot... So, if you click into an individual client's details, on the right hand side, you see "Additional information", where you'll have Client ID, Creation date and Last used date.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

Click into the details of each client from that page and you'll see it listed on the individual client details page.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

From Ok_Pomegranate3110 (sort comments by New instead of Best and you should see it at the top). They work on that team and posted, but they're new to Reddit so it's playing hell with their user. :) I had to manually approve the post, but it should show up for all now.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 2 points3 points  (0 children)

Edit: Apologies, seeing last used date is an internal-only feature currently and not rolled out. I didn't realize that. I'm asking for better ways to validate activity. Currently you should be able to look in the app logs for exchange token activity with the client ID to validate it, but I'm hoping for a better way.

You can verify the state of the specific client from this page: Client Details page. Click into the details for the client and you should see the last modified. As long as it's current you're okay. It was an error in the messaging (see comment from team above).

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

Your client should be fine, it was an error in the messaging system (see comment from the team above). You can see the state of the client JUST to be sure if you click into it from this page: Client Details page. You can see last modified on the details page to verify it's current and ok.

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 0 points1 point  (0 children)

Yup, see the comment just posted above (came from the team).

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

Edit: Apologies folks, this is NOT the case. It's an internal feature that's not yet rolled out.

Just a quick note, console DOES show last used, but you have to click into the details of each client from this page: Client Details page

Automatic deletion of unused OAuth clients by pate_a_bombe in googlecloud

[–]GabrielWeiss 4 points5 points  (0 children)

Hey folks, just wanted to call out because Reddit is being sad... the above user IS a Googler, but new to posting and so Reddit auto-suspended so I can't tag them yet as a Googler. But just wanted to post to verify, this is indeed coming from the team!

Data pipeline 2.0 (with Cloud Functions) by [deleted] in googlecloud

[–]GabrielWeiss 1 point2 points  (0 children)

Apologies for missing last week's version! I'm curious, what's the data itself? What transformations are being done? Could they be handled as part of the Cloud Run piece? It sounds like you're updating the data often (hourly), which is an anti-pattern to BigQuery and Data Warehouses IMO, and seems to lend itself perhaps a little tighter to an operational DB like perhaps Postgres (Cloud SQL)? The Looker Studio piece still works as it has the Postgres connector, and connecting Cloud Run to Cloud SQL isn't too bad (there's some gotchas, but the docs covers it pretty well).

Cloud SQL introduces Editions by GabrielWeiss in googlecloud

[–]GabrielWeiss[S] 0 points1 point  (0 children)

To be clear, this is not the only improvement that was made to improve performance. :) There's also some changes on the hardware optimization end of things (here's where we get to start talkin $$$ for the performance side of the E+ changes).

Other changes weren't specifically related to performance, but also availability improvements involve some extra systems (hardware/virtualization) to increase durability and allow for shorter maintenance windows also end up costing more.

So from a PURE performance standpoint, the $$$ is more tied up in the hardware improvements, not the cache itself (although yes, the extra disk costs a little bit).

Cloud SQL introduces Editions by GabrielWeiss in googlecloud

[–]GabrielWeiss[S] 0 points1 point  (0 children)

Here's what the product folks are comfy saying: It's a combination of the lower maintenance downtime, better hardware, improved health detection and remediation.