3 ms·
1. Because Google (it's not just the Google Cloud console). 2. Good point. I'll see why that isn't the case (I agree strongly, it'd be nice to know if this has
by boulos 11y ago
1. Because Google (it's not just the Google Cloud console).
2. Good point. I'll see why that isn't the case (I agree strongly, it'd be nice to know if this hasn't been used so you can revoke it).
3. A lot of systems require a user/email to identify the "person" taking the action. So this one is a crazy auto generated one for you. You didn't say it, but I'd love to be able to name them (like "Default GCE Service Account" or "Service Account for that Binary I built for deploying stuff").
4. This is something Google Cloud is behind on and we're working on it. For Storage (and PubSub) there actually are much finer grained ACLs (and you could add them as just a VIEWER role, etc.). I don't recall if we yet support the "Bob can use GCE but not BigQuery". Expect updates here soon.
Edit: more blank lines
- boundlessdreamz 11y ago1. Didn't get that. IMO Enabling/disabling APIs should be a separate menu item from Credentials. 2. Ok. 3. Yeah. Naming is a start. I also want to know what does it have access to. 4. Yeah. It's quite messy. Also there are Service Accounts in "Credentials" and also in "Permissions". There are multiple "Google APIs service account" in Permissions. I have no idea what they are for and what does it have access to