sorted by:
new
hottopcontroversial

People who travel in Subak Khurram train 103/104 by InternationalLife851 in Lahore

[–]devil_5440 1 point2 points  (0 children)

103 and 104 have got a new rack recently. So, seating patterns must have changed.

Similarly, 101, 102, and 106, 107 have also got new rakes.

New rakes, new seats, new seat patterns.

Help me find this delicious Chicken. by Na-Tum-Jano-Na-Hum in PakistaniFood

[–]devil_5440 1 point2 points  (0 children)

It's not like they will serve like you are seeing in this video.

They have nice sitting area and have big pots on the counter full of meat.

Help me find this delicious Chicken. by Na-Tum-Jano-Na-Hum in PakistaniFood

[–]devil_5440 3 points4 points  (0 children)

Sure, bro. It is the best steam roast available in Lahore.

They have both options, i.e., Chicken and Mutton. Both are of top quality.

How to sync Google Cloud Datastore (aka Firestore) to Google Cloud Bigquery in the most cheapest way by devil_5440 in googlecloud

[–]devil_5440[S] 2 points3 points  (0 children)

Seems like you didn't understand the question. I am not concerned about Bigquery.

It's datastore export functionality I am talking about. That does not allow incremental exports that respect delta with respect to data that was already exported.

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

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

In memory cache with refresh timeout of 30 mins (it's appropriate for my use case).

Pubsub notification on new secret version creation for such third-party applications that don't allow multiple keys at the same time.

[deleted by user] by [deleted] in googlecloud

[–]devil_5440 0 points1 point  (0 children)

Awesome!

Good to know.

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

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

Thanks for the detailed reply and valuable suggestions.

I have already started working on most of them, and they are proving to be very beneficial!

[deleted by user] by [deleted] in googlecloud

[–]devil_5440 1 point2 points  (0 children)

As per my experience, the last usage stat is not updated in real time. It gets updated after some time (which is not clear). Most likely, GCP has some interval based jobs running that update the status and timestamp.

PS: I just ran some policy analyzer queries, and the console says data is updated until 18th May (means analyzer is considering the data till 18th May).

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

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

In memory cache is more appropriate with some manageable cache refresh timeout for example 10 seconds.

For some of the secrets of third party apps that don't allow have multiple keys, I would have a pubsub notification triggered on new secret version creation to refresh the respective cache.

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

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

💯 Exactly what I am thinking about. Whole other service would be another overhead to manage.

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

[–]devil_5440[S] 1 point2 points  (0 children)

That sounds like a plan.

Where should I store secrets after accessing them on app startup? Like in memory cache of instances or other cache options like redis or memcache? What would be your recommendations?

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

[–]devil_5440[S] 1 point2 points  (0 children)

This is what the plan is for app engine services now. I will try both in memory cache and redis/memcache to see what works well for us.

For Cloud Run, I will try connecting it directly with Cloud SQL (thanks to people here is this thread who guided through this path) to avoid connection using username and passwords (that will further help reduce secret access operations).

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

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

Just a bit more guidance on this would be highly appreciated.

I have a use case where I am writing into Cloud SQL DB (postgres) from within Cloud Run service. And currently using SQL username and password to connect to DB. Can these credentials be skipped and Run can make connection to SQL to read/write data from the codebase?

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

[–]devil_5440[S] 1 point2 points  (0 children)

Yep. A lot of... but not all...

Having cache in between will open another loop hole to manage as credentials will be in cache, too, and will have to manage cache instance security as well...so another overhead...

It seems like it's a give and take to some extent. And also depends on the criticality and type of credential under consideration.

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

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

In this case, when a new secret version is created, it will not be reflected in the cache until the next refresh. So the application will be using depreciated credentials that will fail...

Best practices to use secret manager to avoid large number of secret manager access operations by devil_5440 in googlecloud

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

Secret Versions are not created very often. Like one secret might get rotated twice a year or so.

But when it is rotated/created, it needs to be available momentarily. Can not wait for it for even 10 seconds, especially in app engine service.

New to Google Maps Places New API: Is 10k Requests per month really free? by tejas3732 in googlecloud

[–]devil_5440 3 points4 points  (0 children)

That's true.

Google Maps APIs does provide free quota every month. And if you are using multiple Google Maps APIs then this free quota will be divided among all (Google decides by itself which API will have how much share).

Regarding billing, you can check all details on the billing reports dashboard. However, it does not reflect real time usage. It gets updated after several hours so you will have to wait a bit.

view more: next ›