You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am getting a little worried that the use of the default credentials in lieer will incur costs at some point. I've tried to disable all that, but the google cloud stuff is very complicated. Google may also possibly change this in the future.
The problem is that the API key was used more than 58 million times in the last 30 days, so it is definitely going to affect users. It is also very possible that this is other tools just using our API keys.. who knows.
Gaute
The text was updated successfully, but these errors were encountered:
Hi!
This isn't a lieer problem, but perhaps someone have had the same issue or will in the future.
lieer works fine using the default API credentials, but I have a "legacy" G Suite account and haven't been able to create a project in the Google Cloud Platform console.
I get the following error message:
Google Cloud Platform service has been disabled. Please contact your administrator to turn the service on in the Google Workspace Admin console.
Both the "Google Cloud Platform" and "Google Developers" apps are enabled in the G Suite admin console, and I haven't been able to find any other relevant settings nor found any tips on github/reddit/google.
It might be just the way it is because of the "legacy" G Suite status, but if anyone have got it to work I'm interested.
Hi,
I am getting a little worried that the use of the default credentials in lieer will incur costs at some point. I've tried to disable all that, but the google cloud stuff is very complicated. Google may also possibly change this in the future.
The problem is that the API key was used more than 58 million times in the last 30 days, so it is definitely going to affect users. It is also very possible that this is other tools just using our API keys.. who knows.
Gaute
The text was updated successfully, but these errors were encountered: