Hi everyone, I am running Eramba Community on a Google Cloud virtual machine with a CloudSQL mySQL database instance. Eramba does not seem to like this very much, because in the health console, it complains about permissions.
Connected datasource must have required permissions granted for the database to work properly.
Required privileges: SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, INDEX, PROCESS, TRIGGER. Schema granted:
-
Global granted:
USAGE
Missing Privileges:
SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, INDEX, PROCESS, TRIGGER
The user given to me on CloudSQL is an admin, as it can do all database operations, yet for some reason, Eramba still says the permissions are not set.
I would appreciate any advice on what I need to change on the CloudSQL side to resolve this error.
Unfortunately we do not have experience with google cloud, but I suppose you will have to set some specific parameters the same way as we are doing on AWS for example.
I’m sharing here an old installation guide where you can see how to setup these directly in MySql, check with your team how they can mirror this directly in parameters group.
The document you shared described installing mySQL on an EC2 instance. I am using mySQL in the PaaS mode (think of Aurora or RDS on AWS). The whole point is to not having to support mySQL, and using the cloud service. Google’s CloudSQL is the same. I would love to see some examples how a proper hosted SQL instance is utilised instead of manually installing it, or utilising the built-in Docker instance.
Yes, that’s exactly what I was trying to explain. I understand that you’re not managing MySQL directly via the console but rather through a parameter group (as it’s called in AWS RDS). That’s why I shared the old installation guide, so you can see the parameters we need to set. You’ll need to configure these variables through the parameter group (or whatever it’s called on Google Cloud Platform).
The use of GRANT is prevented from being run on the Google Cloud database instances. There needs to be another way to achieve this, considering the account used by Eramba does have admin rights on the instance.